July 19, 2026
What a seed is, and why consistency sells more food than any single photo
There's a small number printed under every photo you generate. Most people never notice it. It's the difference between a menu that looks like one restaurant and a menu that looks like fifteen.
I spent years as a food photographer before building this, and the single most common thing I fixed on client menus wasn't a bad photo. It was thirty decent photos that didn't belong together. One shot warm and golden, the next one cold and grey, a third one from a completely different angle on a different tablecloth. Individually fine. Together, amateur.
Consistency is the part customers can't name but always feel. And in an AI studio, the tool that gives you consistency on demand is the seed.
So what actually is a seed?
Every AI render starts from a bank of randomness — the model needs a random starting point before it begins shaping an image. The seed is just the number that determines that starting point.
Think of it as a shuffle number for a deck of cards. Shuffle with the number 481920 and you get one specific order. Shuffle with 481920 again, with the same deck, and you get that same order back. Change the number and you get a different shuffle. That's the whole idea — nothing more mystical than that.
In practice this means: same photo + same settings + same seed = the same result. Change the seed and you get a different interpretation of the same instructions. Both are valid; they're just different rolls of the dice.
Where to find yours
Every finished shot in your gallery carries its seed underneath it, written as a small number like #481920. Click it and it's copied to your clipboard. On the upload page there's a Seed field: paste the number in, and your next render starts from exactly that point instead of a fresh random one.
Leave the field empty and you get a new random seed every time — which is what you want while you're still exploring.
The honest version of what a seed can and can't do
This is where most guides oversell it, so let me be precise about it.
Reusing a seed on the exact same photo with the exact same settings reproduces that render. That's reliable, and it's genuinely useful — it means a result you liked is never lost.
Reusing a seed on a *different* dish does not clone the look. A seed is not a filter and it isn't a style preset. What it does is remove one source of random variation between two renders, so two dishes shot with the same settings and the same seed land noticeably closer to each other than two random ones would. It's a nudge in the right direction, not a lock.
The real lock — the thing that makes an entire menu read as one restaurant — is the reference photo. When you shoot your actual plate and your actual tabletop into a brand kit, every render is told to match those exact props. That's what holds a set together. The seed is the fine-tuning on top of it.
- Same photo, same settings, same seed → the same image back. Reliable.
- Different photo, same settings, same seed → closer in feel, not identical. A nudge.
- Different settings, same seed → the settings win. A seed can't override your choices.
- Your plate and tabletop references → the actual consistency anchor. Use them first.
Why consistency is worth the trouble
A delivery app listing is a grid. Customers don't study one photo — they scan twelve at once. When those twelve share a lighting direction, a colour temperature and a camera height, the grid reads as one confident brand and the eye moves smoothly across it. When they don't, the grid reads as noise, and the noise reads as carelessness. Nobody consciously thinks 'the white balance is inconsistent'. They think 'this place looks a bit sloppy' and they order elsewhere.
The same effect runs through everything else you publish. A menu where every dish is lit the same way looks designed. An Instagram feed with one recognisable look builds a visual signature people start recognising in the feed before they read the name. The one-off perfect photo does none of that work. The set does.
A practical workflow
Here's the routine I'd actually use, in order:
- Explore first. Run two or three dishes with the seed field empty and different settings until one result makes you stop scrolling.
- Lock the props. Put the plate and tabletop you actually serve on into a brand kit — this does more for consistency than everything else combined.
- Reuse the whole look, not just the seed. Hit 'Use these settings' on the shot you liked and the upload form reopens with its plate, tabletop, lighting, framing and seed already filled in. This is the button most people actually want — a seed on its own will not bring the plate back.
- Or name it. 'Lock current style' saves the same bundle as a named look you can re-apply to any future dish in one tap.
- Use the seed field itself for the narrow job it's good at: pasting a number back to reproduce a specific render, or changing it to reroll one that's nearly right.
- Re-shoot changes with the same look. When one dish changes in three months, apply the saved look and the new photo drops into the existing set instead of standing out.
When to deliberately change the seed
A seed isn't only for repeating things — it's also the cheapest way to get a second opinion. If a render is close but something's slightly off, don't rewrite all your settings. Change the seed and run it again. You'll get a different interpretation of the same instructions, and often the second or third roll is the one you keep.
That's the mental model worth holding onto: same seed to repeat, new seed to reroll. Everything else — the lighting engine, the plate, the tabletop, the angle — is what you're actually directing. The seed just decides which of the many valid versions of that direction you get.
