ImageVideo

Model developer guide

ByteDance

13 website model guides

Separate Seedream image work from Seedance video work before choosing a model. This page connects composition and motion briefs with exact hosting contracts, while keeping sequential-image delivery, route spelling and unverified app controls visible.

Image generationVideo generationCreative output

Practical guidance

Where should I start?

Editorial starting points, not a performance ranking. Check current app access before choosing a model.

Build a still-image campaign concept

WaveSpeed positions Seedream 4.5 for composition and in-image typography. Start with one layout, a concise subject description and space for verified copy, then inspect lettering and object relationships rather than assuming the first draft is publishable.

Tradeoff: The public endpoint uses decimal punctuation while the audited app route uses hyphens. Equivalence has not been generation-tested, and provider high-resolution support is not the app’s default output.

Seedream 4.5 guide

Plan a short motion sequence

Higgsfield documents a text-to-video route for Seedance 2.5. Describe a subject, one main action and a restrained camera move; use the returned clip as a reviewed shot in a larger edit.

Tradeoff: This text route does not accept source media. Its documented maximum is not a verified EZ Ai Assist maximum, and a card or estimator range does not establish forwarded parameters.

Seedance 2.5 guide

Technical details

What does the provider document?

Official documentation describes the named model or gateway—not every feature available in this app.

Image versions and endpoint punctuation matter

WaveSpeed documents bytedance/seedream-v4.5 for the image route. Its examples include 2048-square and larger compositions, subject to the live input schema. The app audit records bytedance/seedream-v4-5. This guide preserves that disagreement instead of assuming aliases are interchangeable or modifying the application mapping.

Sequential generation is a separate contract

The Seedream 4.5 sequential endpoint describes consistent multi-image generation. That host capability is distinct from rendering several panels inside one image, and from returning several downloadable images to a customer. The app audit reports no image-count parameter and first-image-only return behavior, so the latter is not established here.

Seedance 2.5 text-to-video limits

Higgsfield’s bytedance/seedance-2.5/text-to-video schema accepts a nonblank prompt, a requested 4–30 seconds, 480p/720p/1080p and six aspect ratios. It also documents generated audio, bitrate and MP4/MOV options. These are hosting API fields; image-guided and video-edit workflows use different endpoints.

Complete website coverage

Explore all 13 model guides

Every existing catalog entry for this provider is linked below. Status labels come from the individual website guides; catalog coverage is not a guarantee of current app access. Historical and snapshot pages remain references, not extra active models.

Practical guidance

From a brief to a useful result

Original prompt examples, not generated-output demonstrations. They have not been generation-tested.

Workflow 1

Create a coherent retail concept board

Plan one downloadable board containing several panels. This works as a visual brief without assuming that the app returns all images from a host-side sequence.

Create one square concept board with three equal panels showing the same unbranded amber soap bottle on a bathroom shelf, beside a folded towel and beside a small dish. Preserve its rectangular shape and black pump in each panel. Use warm ivory walls and consistent soft daylight. Leave the label blank and add no captions or claims.

Check the result: Check that the file is a usable board, compare bottle geometry across panels and verify that no generated copy or extra pumps appear.

Read the sequential image guide

Workflow 2

Brief one clear reveal shot

Use a text-only shot brief for this route. Describe the starting composition and the final view, keeping timing flexible until you have verified the app’s actual output.

A small orange sailboat rests on a quiet pond behind foreground reeds. Move the camera slowly sideways so the reeds reveal the entire boat. Keep the boat stationary, its mast straight and the water reflections consistent. Use cool early-morning light and one uninterrupted shot; add no people, lettering or dramatic weather changes.

Check the result: Watch the full clip for disappearing objects, bent geometry and unintended cuts. Check actual duration, dimensions and sound before putting it on a timeline.

Read the Seedance 2.5 guide

Technical details

What changes inside EZ Ai Assist?

The cited hosting contracts were independently reviewed. Image controls come from the October 8 owner audit and video mappings from owner audits labeled October 9; application handlers and paid generation were not independently tested. Provider limits and app-card labels are different evidence.

Owner audit · October 8

Image controls and returned files

The WaveSpeed image wrapper sends a prompt, default 1024 × 1024 size and safety checking. It does not send editing references or image count, and returns only the first image URL, including for sequential choices.

Audit vs. current host docs

Known image compatibility questions

The 4.5 and 5.0 Lite app mappings use different version punctuation from public hosting paths. Seedream 5.0 Lite documentation also gives a 1440-pixel minimum that conflicts with the wrapper’s 1024-square default. Successful compatibility remains unverified.

Owner video audit · October 9

Video controls are host-specific

Older WaveSpeed Seedance routes use a wrapper forwarding prompt, duration and aspect_ratio, with a 3–10-second clamp; resolution, audio, seed and references are not forwarded. The Higgsfield Seedance 2.5 card says 12 seconds, but its effective controls and 4–30-second estimator passthrough are not fully verified.

Before you rely on a result

Limits, costs and tradeoffs

  • The full catalog includes distinct versions and sequential routes. Do not merge their names or transfer a resolution, price or media-input feature from one endpoint to another.
  • A multi-shot prompt, coherent character sequence or exact caption remains a creative target. Review continuity and factual details, and use a conventional editor for exact typography and timing.
  • Host reference prices, estimator formulas and the customer’s actual charge are not equivalent. No generation, price calculation or routing change was performed for this provider guide.

Provider references and picker estimates are not EZ Ai Assist customer charges. Read the website pricing explanation.

Compare by task

Other paths to explore

FLUX

Compare an image-only family when still composition and material detail are the main task.

Runway

Review separate image-animation and source-video editing workflows when existing media should anchor the result.

Common questions

ByteDance, without the assumptions

Will a Sequential option give me several files?

Not according to the audited app wrapper, which returns only the first image URL and sends no image-count setting. A single contact sheet is an alternative prompt idea, not proof of multi-file delivery.

Can Seedance 2.5 make a 30-second video in the app?

Thirty seconds is the cited Higgsfield endpoint’s maximum, not a verified app limit. The owner audit records a 12-second card and a wider estimator range. The final forwarded request and successful maximum were not tested.

Can I fix the Seedream route conflict by changing my prompt?

No. Route punctuation and accepted image sizes are integration details, not prompt instructions. They remain explicitly unresolved in these guides; this website update does not change application routing.

New to the terminology?

Official documentation

Sources & review notes

Highlighted provider contracts reviewed . Individual model guides carry their own review dates. Sources can change; these pages do not perform live health checks.

The cited hosting contracts were independently reviewed. Image controls come from the October 8 owner audit and video mappings from owner audits labeled October 9; application handlers and paid generation were not independently tested. Provider limits and app-card labels are different evidence.