MOSS-Image Turbo vs Seedream 5.0 Flash

MOSS-Image Turbo and Seedream 5.0 Flash side by side: specs, capabilities, parameters, and live pricing from the EmpirioLabs catalog.

OpenMOSS ByteDance Image Generation

MOSS-Image Turbo vs Seedream 5.0 Flash at a glance

MOSS-Image Turbo from OpenMOSS and Seedream 5.0 Flash from ByteDance are both in the Image Generation category, available through the EmpirioLabs API.

Key differences

  • MOSS-Image Turbo is the newer release (Oct 16, 2026); Seedream 5.0 Flash was released on Sep 28, 2026.
  • Input types only Seedream 5.0 Flash accepts: Image.
  • Capabilities listed only for MOSS-Image Turbo: seed control.
  • Capabilities listed only for Seedream 5.0 Flash: image editing, layer decomposition, interactive editing, multi reference, transparent background.
  • MOSS-Image Turbo lists the lower rate for Image generation (per image).

MOSS-Image Turbo vs Seedream 5.0 Flash: specs

SpecMOSS-Image TurboSeedream 5.0 Flash
Model IDmoss-image-turboseedream-5-0-flash
AuthorOpenMOSSByteDance
ReleasedOct 16, 2026Sep 28, 2026
Input
Text
Text Image
Output
Image
Image
Region-Malaysia
Endpoints
POST /v1/images/generations
POST /v1/images/generations
Capabilities
image generation text rendering multilingual text seed control
image generation image editing layer decomposition interactive editing multi reference text rendering multilingual text transparent background

MOSS-Image Turbo vs Seedream 5.0 Flash: API pricing

Live rates from the EmpirioLabs catalog for both models. Each rate card always matches what the API charges.

MOSS-Image Turbo vs Seedream 5.0 Flash: API parameters

Request parameters each model lists on EmpirioLabs, with the allowed values or range where one applies. A dash marks a parameter the model does not list.

ParameterMOSS-Image TurboSeedream 5.0 Flash
promptstringstring
aspect_ratio1:1, 16:9, 9:16, 4:3, 3:4, 3:2, 2:3 Default: 1:1auto, 1:1, 16:9, 9:16, 4:3, 3:4, 3:2, 2:3, 21:9 Default: auto
sizestringstring
width512 to 2048-
height512 to 2048-
seed0 to 2147483647-
num_images1 to 4 Default: 1-
formatwebp, png, jpg, jpeg Default: webp-
response_formaturl, b64_json Default: urlurl, b64_json Default: url
return_base64boolean Default: false-
image-array
images-array
layer_decomposition-boolean Default: false
quality-1K, 1.5K, 2K Default: 2K
use_custom_size-boolean Default: false
custom_width-15 to 8600

MOSS-Image Turbo vs Seedream 5.0 Flash: limits and notes

MOSS-Image Turbo

Generates images from text, with accurate English and Chinese text in signs, posters, labels, and layouts.

Input

  • A text prompt of up to 4,000 characters. Image inputs, negative prompts, and LoRA adapters are not supported.
  • Size from aspect_ratio (1:1, 16:9, 9:16, 4:3, 3:4, 3:2, or 2:3), from size as WIDTHxHEIGHT, or from width and height. Each side is a multiple of 16 from 512 to 2,048 pixels, and width x height is at most 1,048,576 pixels. The default is 1024x1024.
  • Up to 4 images per request with num_images.

Output

  • WebP by default, or PNG or JPEG with format.
  • A signed URL by default, or base64 with response_format set to b64_json.
  • Each image carries the seed it used.

Content safety

Generated images pass an automated content-safety check. An image flagged as explicit is not returned. Because the image is generated before the check runs, a flagged generation is still billed.

Weights

  • INT8.

Seedream 5.0 Flash

Modes

  • Text to image
  • Single or multi-image to image
  • Interactive editing with coordinate or sketch markers
  • Layer decomposition into a base image plus up to 16 layers

Interactive editing

Mark the region to change directly on the input image with a sketch, circle, or arrow, then describe it in the prompt. For exact placement, use coordinate tags on a 0 to 1000 normalized grid:

Place the subject from image 1 <bbox>179 283 796 986</bbox> at the position in image 2 <bbox>118 331 933 871</bbox>.

Layer decomposition

Set layer_decomposition to true with exactly one input image to split it into a base image plus up to 16 transparent PNG layers. Every returned image carries its stacking order as z_index, and each layer also carries its position in the base image as bounding_box.absolute and bounding_box.normalized, plus a name and a description. Leave the prompt empty to let the model choose the elements, or name the elements or coordinate regions to separate. Resolution accepts 1K, 1.5K, or 2K, and matches the input image when unset.

Limits

  • One output image per request, except layer decomposition, which returns the base image plus its layers
  • Up to 10 reference images, and exactly one for layer decomposition or a transparent background
  • 1K, 1.5K, and 2K resolution tiers
  • PNG or JPEG output, and layers are always PNG
  • A transparent background needs one input image that already has an alpha channel, and PNG output
  • No grouped output, streaming, or web search

Billing

Every resolution tier bills at the same per-image rate, and reference images are free. Layer decomposition bills every returned image, the base image and each layer, at that same rate.

Content safety

Generated images pass an automated content-safety check. An image flagged as explicit is not returned. Because the image is generated before the check runs, a flagged generation is still billed.

How to call MOSS-Image Turbo and Seedream 5.0 Flash

MOSS-Image Turbo runs through POST /v1/images/generations. The request returns a job_id right away; poll GET /v1/jobs/{job_id} until the job completes and read the output URLs from the result. Or add "sync": true to skip polling: the request stays open and returns the finished OpenAI-style image response directly, so OpenAI SDKs work as-is. Both models are called through the same endpoint. Set model to moss-image-turbo or seedream-5-0-flash. Get an API key from the EmpirioLabs dashboard.

cURL: submit the job
curl https://api.empiriolabs.ai/v1/images/generations \
  -H "Authorization: Bearer $EMPIRIOLABS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "moss-image-turbo",
    "prompt": "Describe what you want MOSS-Image Turbo to generate."
  }'

MOSS-Image Turbo vs Seedream 5.0 Flash: tests and guides

Prompt tests and comparison runs that cover both models.

MOSS-Image Turbo vs Seedream 5.0 Flash: common questions

What is the difference between MOSS-Image Turbo and Seedream 5.0 Flash?

MOSS-Image Turbo is the newer release (Oct 16, 2026); Seedream 5.0 Flash was released on Sep 28, 2026. Input types only Seedream 5.0 Flash accepts: Image. Capabilities listed only for MOSS-Image Turbo: seed control. The specs, rate cards, and parameters on this page come from the live EmpirioLabs catalog.

Which is newer, MOSS-Image Turbo or Seedream 5.0 Flash?

MOSS-Image Turbo is the newer release (Oct 16, 2026); Seedream 5.0 Flash was released on Sep 28, 2026.

Which has the lower rate, MOSS-Image Turbo or Seedream 5.0 Flash?

MOSS-Image Turbo lists the lower rate for Image generation (per image). Both live rate cards are on this page and always match what the API charges.

Can I switch between MOSS-Image Turbo and Seedream 5.0 Flash without rebuilding my integration?

Yes. Both models use POST /v1/images/generations with the same EmpirioLabs API key, so most integrations switch by changing the model value. Check the parameters table on this page first if you rely on a model-specific parameter.

Can I try MOSS-Image Turbo and Seedream 5.0 Flash in the browser before integrating?

Yes. Open each model in the EmpirioLabs playground and run the same prompt on both, with the parameters the API exposes.

Ready to use better endpoints?

Check out our pricing or reach out if you want your own model deployed on our stack.