Seedream 4.5 Spicy vs 5.0 Pro Spicy: What Breaks on Upgrade

Key Takeaways

• Five of the eight size values accepted by Seedream 4.5 Spicy are not in 5.0 Pro Spicy's enum. Swapping the model string alone will fail validation on most of your presets.
• There is no seedream-5.0-pro-ref2i-spicy. Multi-reference folded into i2i, which now takes an images array instead of a single image.
• Both generations bill a flat per-image rate regardless of resolution: $0.040 on 4.5 Spicy, $0.045 on 5.0 Pro Spicy. The new low-resolution sizes are not cheaper.

The Model String Is the Smallest Change

Upgrading an image endpoint usually looks like a one-line diff. Here it is not. Read on August 11, 2026 from the request schemas at docs.siray.ai/api-reference/openapi-spec/, the two generations differ in the enum, in the endpoint set, and in the shape of the reference field — three places a working pipeline can break without the prompt changing at all.

Five of Eight size Values Stop Working

Three values survive. The other five are gone, and none of the replacements is an exact aspect match, so a set generated across both generations will not crop identically. If you keep a library of presets, this is the migration, not the model string.

There Is No 5.0 Pro ref2i

Two endpoints became one. Which migration you face depends on where you started. Coming from ref2i-spicy, you change the endpoint name and keep your images array as is. Coming from i2i-spicy, the endpoint name changes and the single image string becomes an array — a silent shape change that a naive find-and-replace will miss.

The upside is that one endpoint now covers both single-image edits and reference sets of up to ten, which simplifies any batch photo-set workflow that previously branched on reference count.

What You Actually Gain

5.0 Pro Spicy's enum holds 16 values against 4.5's 8. It raises the ceiling slightly, from 3024x1296 to 3136x1344, and adds an entire low tier that 4.5 never had: 1024x1024, 1152x864, 864x1152, 1424x800, 800x1424, 1248x832, 832x1248 and 1568x672. It also adds output_format, jpg or png, which 4.5 does not expose.

Do not read that low tier as a cheap draft mode. Both generations bill flat per image with no resolution term: $0.040 on 4.5 Spicy and $0.045 on 5.0 Pro Spicy. A 1024x1024 render on 5.0 Pro costs exactly what 3136x1344 costs. If you want cheaper drafts, they live on 4.5, which is 12.5% less per image and has no small sizes at all.

FAQ

What is the difference between Seedream 4.5 Spicy and 5.0 Pro Spicy?

5.0 Pro Spicy accepts 16 size values against 4.5's 8, adds an output_format field for jpg or png, drops the separate ref2i endpoint, and costs $0.045 per image versus $0.040. Only three of 4.5's eight size values remain valid.

Is there a seedream-5.0-pro-ref2i-spicy endpoint?

No. Multi-reference moved into bytedance/seedream-5.0-pro-i2i-spicy, which accepts an images array of 1 to 10 rather than the single image string that 4.5's i2i endpoint takes.

Does generating at a lower resolution cost less on Seedream 5.0 Pro Spicy?

No. Billing is flat per image with no resolution term, so 1024x1024 and 3136x1344 both cost $0.045. Cheaper drafts mean dropping to 4.5 Spicy at $0.040, which offers no small sizes.

Summary

The model string is the one part of this upgrade that is trivial. Budget for a size-preset rewrite, a merged reference endpoint, and a field that changes from a string to an array. The prompt itself carries over unchanged — the family prompt guide still applies, and the 2026 image model roundup covers whether to stay in this family at all.

Get Started

Create your free Siray account and call both generations with one key — one API for multiple AI models covers the setup.

Compliance: Siray refuses all illegal content and enforces zero tolerance for CSAM. Every endpoint above is intended for lawful adult content involving consenting adults only, and never for a real person's likeness without documented consent. "Uncensored" and "Spicy" mean no excess filtering within the law — not the absence of it.