Seed Discipline: Reproducing a Z-Image You Already Liked

You generated something good on z-image-turbo-t2i, noted the seed, and now you're moving to z-image-spicy-pro-t2i for the higher resolution. You paste the same seed number in, expect the same look back — and get something else entirely. The seed range is identical on both endpoints. That's exactly why the failure is confusing: nothing in the request looks wrong.

Key Takeaways

• z-image-turbo-t2i and z-image-spicy-pro-t2i both accept seed from -1 to 9999999999 — the same range, verified against both endpoints' specs.
• A locked seed only guarantees a repeatable output on the same endpoint with the same prompt. It says nothing about what happens if you change the model.
• z-image-spicy-pro-t2i has a prompt_expansion_enable field that defaults to true and silently rewrites your prompt. z-image-turbo-t2i has no such field at all.
• Migrating a look between endpoints means re-anchoring a new seed on the destination model, not porting the old number and expecting it to work.
• Size doesn't carry over either: turbo is fixed at 1024x1024; spicy-pro's size enum means re-anchoring a seed must happen at the size you intend to ship.

What Locking a Seed Actually Guarantees

A seed pins the random component of generation so the same request produces the same output twice. That guarantee holds for exactly one thing: the same endpoint, called with the same prompt and the same seed value. It doesn't extend to a different prompt, a different size setting, or — the part people miss — a different endpoint. Nothing about seed being a shared field name implies it behaves identically once the underlying model changes.

Why the Same Number Won't Reproduce the Look on a Different Endpoint

z-image-turbo-t2i and z-image-spicy-pro-t2i are separate models with separate weights, not two configurations of one model. Feeding both the identical seed doesn't align their internal randomness in any useful way — it's a coincidence of shared field naming, not a portability guarantee. On top of that, z-image-spicy-pro-t2i carries prompt_expansion_enable, defaulting to true, which rewrites your submitted prompt before generation runs. z-image-turbo-t2i has no equivalent field — it always generates from exactly what you typed. So even if you kept the prompt text byte-for-byte identical, spicy-pro may not be running the prompt you think it's running.

The One Thing You Can Control When Migrating

You can't make the two models share pixels, but you can remove one variable: set prompt_expansion_enable: false explicitly when you call z-image-spicy-pro-t2i. That stops the silent prompt rewrite, so the prompt spicy-pro actually generates from matches what you sent — the same guarantee turbo gives you by default, just not automatic here. It won't make spicy-pro's output match turbo's. It just means one fewer thing is different between your intent and what got generated.

Treat a Migration as a New Anchor, Not a Port

The practical habit: when you move from z-image-turbo-t2i to z-image-spicy-pro-t2i, don't try to carry a seed number over and expect continuity. Generate a fresh batch on the destination endpoint, pick the seed from that batch that gives you the look you want, and lock it there. From that point forward, the same-endpoint guarantee applies again — same seed, same prompt, same result, as many times as you need it. Seed discipline for character or style consistency within a single endpoint is a real, working technique; see how it's applied to holding a face steady across a shoot in Z-Image NSFW Character Consistency. It just doesn't travel across the endpoint boundary.

Size Presets Are Not Portable Either

Seed and prompt aren't the only things that reset at the endpoint boundary. z-image-turbo-t2i generates at a single fixed size, 1024x1024. z-image-spicy-pro-t2i exposes an eight-value size enum plus custom. A "look" includes framing and aspect ratio, not just color and subject, and neither survives a jump from a fixed square canvas to a wider or taller one.

Re-anchor the seed at the same size value you intend to ship with. Switching size after locking a new seed on z-image-spicy-pro-t2i reintroduces the exact problem this guide is solving — a different setting resets the guarantee again, and size is no exception.

What This Guide Doesn't Cover

This isn't a cost comparison. z-image-turbo-t2i and z-image-spicy-pro-t2i differ well beyond seed — resolution ceiling, size options, price per image — and if the question is whether the upgrade is worth paying for, Z-Image Turbo to Spicy Pro: What 5x the Price Buys covers that decision directly. This piece is narrower on purpose: it's about what a locked seed does and doesn't promise you once an endpoint changes underneath it.

Create your free Siray account and treat each endpoint's seed as its own anchor — not a number you carry from one model to the next.