ByteDance Seed: Seedream 4.5
Seedream 4.5 refines ByteDance Seed’s image generation and editing with stronger reference-detail preservation, small-text typography and multi-image composition. It suits product visuals, posters and coordinated creative sets where identity and layout matter.
About the model
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Seedream 4.5 is a refinement of ByteDance Seed’s combined image-generation and editing system. The producer scales both the model and its training data, with particular attention to reference consistency, fine visual details, dense text and identifying the intended subject across multiple images. Its useful distinction from Seedream 4.0 is more precise execution of a visual brief, especially when the result must remain recognisably tied to the supplied person, product or design.
Consistency with the reference image The manufacturer emphasises preserving facial features, lighting, colour tone and other source details while making the requested change. Demonstrations include retaining one marked person while removing others, translating text into Chinese with the rest of the design retained, changing a highlighted word’s appearance, and replacing a garment’s material while keeping its pose and flowing shape. These are different kinds of editing: subject selection, typography, material appearance and illumination.
For an edit, separate what changes from what must remain. “Change the jacket material to translucent glass; retain the pose, silhouette and folds” gives a more useful target than a broad restyling request. A material transformation can also require a lighting change: the producer’s example distinguishes metallic reflection from transparent refraction. Compare the output with the source in the regions you intended to preserve, including the face, pose, small accessories and surrounding colour treatment.
Poster layout, logos and dense text Seedream 4.5’s model page places graphic design next, focusing on composition and readable small text. Examples combine a dominant title, artwork and secondary information in an exhibition poster; others explore invitations, fragrance-detail visuals and advertising compositions. The model is useful for testing an entire visual hierarchy rather than treating text as an afterthought. Describe where the main image belongs, give the exact heading and supporting copy, and distinguish font style, alignment, emphasis and spacing.
For a typographic revision, identify the text region and the new wording or treatment. A request to make one heading blue and italic is more specific than asking for a new poster style. Review all rendered text at its intended display size, including small labels and secondary lines. A generated poster or logo concept is visual artwork; the documented image workflows do not establish an editable vector or layered-design output.
Accurate editing across multiple images The producer highlights selecting target elements from different inputs and combining them coherently. The manufacturer’s 4.5 release describes multi-image compositions using up to 10 reference images. Official examples use one image for a person, another for a setting or clothing material, and another for a product or accessory. This supports lifestyle product visuals, coordinated advertisements, interior-style concepts and character or product variations. The model can also generate related outputs: demonstrated tasks include a small advertisement set and separate illustrations for steps in a recipe, with a shared visual style.
Prepare references with explicit roles. For example, assign one image to the subject, one to the bag and one to the location, then specify the composition and which features to retain. If two references disagree about colour or style, name the one that should control that feature. Inspect the resulting scale, placement, lighting and identity across the whole set rather than accepting a convincing single image as evidence that all outputs match.
What the 4.5 refinement adds The technical report singles out stronger editing consistency, preservation of identity-related features and fine details, target-subject handling in multi-image compositions, and typography in dense poster layouts. The producer’s release also describes clearer small faces, improved spatial proportions, realistic lighting and 4K image output. These strengths make 4.5 particularly useful for product catalogues, campaign variations, packaging concepts, pre-production art and graphic design with substantial text.
Text briefs guide new visuals; source images and edit instructions guide reference-based changes. Use the model for creative image production, then review the result against the actual brief: exact copy, recognisable product or person, preserved details, coherent scale and consistent treatment across variants. The edition’s improved preservation is not a guarantee that every source detail survives every complex edit. Reference-count and output-count limits also depend on the documented interface; the 4.0 reference budget should not be assumed for every 4.5 workflow.
Ailoot Ultra · Images POST /v1/images/generations bytedance-seed/seedream-4.5
bytedance-seed/seedream-4.5Overview
Seedream 4.5 refines ByteDance Seed’s image generation and editing with stronger reference-detail preservation, small-text typography and multi-image composition. It suits product visuals, posters and coordinated creative sets where identity and layout matter.
- Accepted inputs
- Text · Images
- Results
- Images
Available in Ailoot · inputs & methods
Ailoot Ultra · Images POST /v1/images/generations
- Input types
text,image- Output types
image
| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits bytedance-seed/seedream-4.5 | Default— |
Fieldprompt | Typestring | RequirementRequired | Values & limits Minimum length: 1 | Default— |
Fieldresolution | Typestring | RequirementOptional | Values & limits 1K, 2K, 4K | Default— |
Fieldaspect_ratio | Typestring | RequirementOptional | Values & limits 1:1, 1:2, 2:1, 2:3, 3:2, 3:4, 4:3, 4:5, 5:4, 9:16, 16:9, 9:19.5, 19.5:9, 9:20, 20:9, 9:21, 21:9, auto | Default— |
Fieldn | Typeinteger | RequirementOptional | Values & limits Minimum: 1 Maximum: 10 | Default— |
Fieldinput_references | Typearray | RequirementOptional | Values & limits Minimum items: 0 Maximum items: 14 | Default— |
Fieldprovider | Typeobject | RequirementOptional | Values & limits | Default— |
Method parameters and lifecycle
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, prompt |
Parametermaterial_types | Contracttext, image |
Lifecycle: synchronous_result_then_owned_library
GET /v1/media/tasks/{task_id} · actual returned task_id or media library record
GET /v1/media/assets/{asset_id}/content
GET /v1/media/assets
GET /v1/media/assets/{asset_id}
Pricing
How the final charge is calculated
The displayed rates estimate the cost before generation. The final charge is calculated from the cost recorded for the original generation. Measured output duration and forecast quantities are not the final billable quantity.
Tariff references do not add request options. Supported parameters are listed for the selected method.
- Fast mode
- Not specified When fast mode is selected
- Flex mode
- Not specified When flex mode is selected
- Maximum reasoning effort
- Not specified When maximum reasoning effort uses the default adjustment
Estimated rates for comparison
Prices by configuration
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Rate schedule | Forecast quantity | Billing unit | Charge |
|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Forecast quantity— | Billing unit— | Charge Input · Input tokens · Estimate for comparison only — / 1K tokens Output · Output tokens · Estimate for comparison only — / 1K tokens Input · Cache read · Estimate for comparison only — / 1K tokens Input · Cache write · Estimate for comparison only — / 1K tokens Input · Cache write, 1 hour · Estimate for comparison only — / 1K tokens |
| Configurationinput image | Rate schedule— | Forecast quantity— | Billing unitper input image | Charge Input · input image · Estimate for comparison only $0 per input image |
| Configurationoutput image | Rate schedule— | Forecast quantity— | Billing unitper output image | Charge Output · output image · Estimate for comparison only $0.08 per output image |
| ConfigurationEstimated generation cost | Rate schedule— | Forecast quantityone generation estimate | Billing unit— | Charge Output · Estimated generation cost · Estimate for comparison only $0.08 estimate before generation This estimate is not an additional charge or a fixed rate for the completed generation. |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
Example requests
Ailoot Ultra · Images
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
export AILOOT_API_KEY
python3 - <<'PY_REQUEST'
import json,os
from pathlib import Path
p={'model': 'bytedance-seed/seedream-4.5', 'prompt': 'a red panda astronaut floating in space, studio lighting'}
Path("request.json").write_text(json.dumps(p,ensure_ascii=False))
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/images/generations \
-H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \
--data-binary @request.json -D response-headers.txt -o result.json
python3 - <<'PY_RESULT'
import base64, json, os, subprocess
from pathlib import Path
from urllib.parse import urlsplit, urljoin
def save_images(items):
if not items: raise SystemExit("No completed images; retain the full response")
for index, item in enumerate(items):
encoded=item.get("b64_json")
uri=item.get("url", "")
if not encoded and uri.startswith("data:image/"):
header, separator, encoded=uri.partition(",")
if not separator or ";base64" not in header: raise SystemExit("Unsupported image data URI")
if encoded:
raw=base64.b64decode(encoded,validate=True)
elif uri:
uri=urljoin("https://api.ailoot.ai",uri)
parsed=urlsplit(uri)
if parsed.scheme!="https" or not parsed.netloc or parsed.username or parsed.password:
raise SystemExit("Invalid returned image URL")
owned=parsed.netloc=="api.ailoot.ai" and parsed.path.startswith("/v1/media/assets/") and parsed.path.endswith("/content")
args=["curl","--fail-with-body","--silent","--show-error",uri]
if owned: args += ["-H","Authorization: Bearer "+os.environ["AILOOT_API_KEY"]]
temporary=Path(f"image-{index}.bin")
subprocess.run(args+["-o",str(temporary)],check=True)
raw=temporary.read_bytes()
temporary.unlink()
else: raise SystemExit("Image has neither bytes nor URL")
if not raw: raise SystemExit("Empty image result")
ext="png" if raw.startswith(b"\x89PNG") else "jpg" if raw.startswith(b"\xff\xd8") else "webp" if raw[:4]==b"RIFF" and raw[8:12]==b"WEBP" else "svg" if raw.lstrip().startswith((b"<svg",b"<?xml")) else "bin"
Path(f"image-{index}.{ext}").write_bytes(raw)
print("Every returned image saved; complete response metadata retained")
save_images(json.loads(Path("result.json").read_text())["data"])
PY_RESULT
Receive and save results
Ailoot Ultra · Images
Download each returned image or save its Base64 contents
GET /v1/media/tasks/{task_id}GET /v1/media/assets/{asset_id}/contentGET /v1/media/assetsGET /v1/media/assets/{asset_id}
Other content reads
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/media/assets \
-H "Authorization: Bearer $AILOOT_API_KEY" -o owned-assets.json
# Preserve every returned asset and follow its exact signed content URL. Do not construct a signed token.
Keep all completed results
Save every completed image; retrieve each returned URL or decode its Base64 contents.
Retain the complete response and headers, every actual output, original returned identifiers and all usage fields. Recover the original operation without submitting creation again.
If the original response needs checking
Keep the returned X-Client-Request-ID for reconciliation. Read only actual returned task_id/asset_id values or the owned media library; never build a task URL from the operation ID and never resubmit creation.
Response fields
| Field | Type |
|---|---|
Fieldcreated | Type |
Fielddata[].url | Type |
Fielddata[].b64_json | Type |
Fieldusage | Type |
Aliases
Model aliases
Ailoot Ultra bytedance-seed/seedream-4.5
Method path aliases
/v1/images
Related caller IDs
FAQ · ByteDance Seed: Seedream 4.5
- What inputs and results are available?
POST /v1/images/generations·bytedance-seed/seedream-4.5:text,image→image- Which fields does the request use?
POST /v1/images/generations·bytedance-seed/seedream-4.5:model,prompt,resolution,aspect_ratio,n,input_references,provider- What limits apply?
POST /v1/images/generations·bytedance-seed/seedream-4.5:n.minimum:1;n.maximum:10