# Seeds and Remix — how to iterate on AI renders on purpose > What a seed does, which engines honor one, how Remix reloads a recipe, and a worked A and B example that changes exactly one variable at a time. Published 2026-09-09 · eroq.ai — canonical: https://eroq.ai/blog/seeds-and-remix-workflow There are two ways to improve an AI render. One is to rewrite the prompt, change the engine, nudge the settings and press generate again, hoping the next one is better. The other is to change exactly one thing and look at what moved. The first feels faster and takes all day. The second is boring and works. Two features make the second one possible — the seed, which controls randomness, and Remix, which controls everything else. ## What a seed actually does Every generation starts from random noise. The [seed](/glossary/seed) is the number that produces that noise. Same seed, same starting point; different seed, different starting point. That has one practical consequence worth internalizing: with the seed fixed and every other input identical, you get the same render back. Change one input — a word in the prompt, a palette, a lighting preset — and you get a render that differs *because of that change* rather than because the dice landed differently. The seed does not make renders better. It makes comparisons honest. Leave the seed empty and you get a new number every time. That is the right default when you are exploring and want variety. Lock it the moment you have something worth improving. ## Which engines honor a seed Not every engine exposes one. The Seedance engines honor a reproducibility seed — [Seedance 2.5](/models/seedance-2-5) and the 1.0 Pro and Lite models — and the studio shows a seed field only when the selected engine supports it. That is the general rule across the video studio: a control you cannot see is a control the engine does not take, not a control that is being quietly ignored. If you switch to an engine without a seed field, your seed discipline does not transfer, and comparisons on that engine need the other half of the method instead — change one variable, run two or three renders per variant, and judge the tendency rather than a single frame. The [video docs](/docs/video) list what each engine accepts. Image models take a different reproducibility lever: the [CFG scale](/glossary/cfg-scale) plus a [negative prompt](/glossary/negative-prompt) will move a still more predictably than re-rolling it will. ## Remix reloads the recipe Every render in your library is saved automatically, free, with its full recipe attached — prompt, engine, length, format, camera move, director's rack settings, negative prompt, seed, all of it. **Remix** is the button that loads that recipe back into the composer. Not the clip, the *decisions*. You land in the studio with every setting exactly as it was when the render happened, one field away from an experiment. This matters more than it sounds. The alternative is reconstructing a good render from memory three days later, which is how people end up with a library full of results they like and no idea how they got them. Remix means the good ones are reproducible by definition. Images have the same loop, and images plus [the image studio](/studio/image) are where it is cheapest to practice — 10 credits a render instead of 100 or more. ## Change one variable at a time The method is unglamorous: 1. Generate until something is 70% right. Seed off, prompt loose, explore. 2. Remix the best one. Note the seed if the engine gave you one — lock it. 3. Change **one** thing. Render. 4. Keep the winner. Go back to step 3. The variables worth isolating, roughly in order of how much they move a render: - The subject sentence of the prompt - The camera move - The lighting preset - The palette - The lens and aperture - The negative prompt - The engine Do not change the engine and the palette together. You will learn nothing and spend twice. ## A worked A and B Here is a base prompt, written the way the composer likes it — one paragraph naming subject, motion, camera, light and mood: > A courier in a black jacket carries a sealed case across an empty rooftop parking lot at night, steady tracking shot from behind at hip height, sodium lights pooling on wet concrete, the city skyline flat and distant, wind pushing litter across the frame, tense and businesslike mood. **Render A.** Engine with seed support, seed `184502`, 5 seconds, 16:9, Tracking. Director's rack set to Film noir · 2010s · Tense · 35mm film · Anamorphic · f/1.4 · Neon noir · Practicals. Watch it. Say what is wrong in one sentence. Suppose it is: *the neon palette makes it look like a music video, not a thriller.* **Render B.** Remix A. Change the palette from Neon noir to Industrial fog. Touch nothing else — same seed, same prompt, same camera, same everything. Now the two clips differ by one decision, and you can actually answer the question. If B is better, keep it and move to the next variable — maybe Practicals to Overhead fall, still one change. If B is worse, you have learned that the palette was not the problem, which is worth a render. Four Remixes in, you usually have a version you would defend, plus a recipe you can apply to the next eleven shots of the same film. That second part is the real payoff: a tuned recipe is a house style, and a house style is what makes a set of clips look like one project instead of seven. ## When not to lock the seed Locked seeds are for converging. They are wrong for two situations: - **Exploring.** If you do not yet know what you want, a fixed seed just shows you the same idea repeatedly. - **Takes.** When you render multiple takes of a scene to pick the best one, you want the dice to actually roll. A fixed seed with an identical prompt will hand you takes that look alike, which defeats the purpose of asking for four. The rule of thumb: seed off while you are searching, seed on while you are polishing, seed off again when you want options. Iterate in [the video studio](/studio/video) and let the library keep the receipts. ## FAQ ### What is a seed in AI video generation? The number that determines the initial random noise a render starts from. The same seed with identical settings reproduces the same render, which makes it possible to compare two versions and know the difference came from your change. ### Do all eroq engines support seeds? No. The Seedance engines honor a reproducibility seed, and the studio only shows a seed field when the selected engine supports one. On engines without it, isolate one variable and judge across a few renders instead. ### What exactly does Remix reload? The full recipe stored with the creation — prompt, engine, format, length, camera move, rack settings, negative prompt and seed — back into the composer, ready to edit. It does not re-render anything on its own, so opening a Remix costs nothing. Lock one thing, change one thing, look. [Open the video studio](/studio/video) — new accounts start with 50 free credits.