Hi everyone. I’m working on a project where I need to generate a large batch of images (around 100) using DALL-E 3, but they all need to feel like part of the same brand. Think similar color palette, character style, and overall mood.
I’ve been using descriptive prompts, but I’m worried about drift over many requests. Is there a best practice for this, like creating a base prompt or using the API in a specific way? I’m new to this scale of generation and any tips would be really helpful.
Still learning.
Creating a "base prompt" is definitely the way to go, and you're smart to be thinking about drift. I've found you need to be really explicit and treat your style guide as non-negotiable.
Try building a master prompt template that locks down the constants first. List your core color hex codes, the precise style (e.g., "flat illustration with soft shadows, line weight of 2px"), and the exact mood keywords. Then you slot in the variable part for each image. Using the API helps because you can programmatically ensure that style block is appended to every single request without a typo.
One caveat: you'll still get some variation. For a batch that large, plan for a manual review and culling phase - maybe 20% more generations than you need. It's a bit of a grind, but locking the prompt down tight gets you 80% of the way there. Good luck with the project
I feel you on the drift anxiety. It's exactly like migrating data between CRMs - you think you've mapped all the fields perfectly, but then you get 100k records in and suddenly the "state/province" field is full of emojis.
Building a rigid template is the way to go, like user1528 said, but I'd go even further. Write your style guide like an angry RevOps manager would write a data governance policy. Put your HEX codes, your lighting phrase (e.g., "even, diffused studio light"), and your composition rule (e.g., "centered subject, medium shot") in a text file. That's your source of truth. Never type it fresh for a prompt. Copy-paste it in, every single time. The API is your friend here to enforce that consistency.
One thing I've learned the hard way: generate your first 10, pick the ONE that nails the style, and use its description as your new anchor. Sometimes you discover the perfect wording by seeing the output, not just from your initial spec. It's an iterative process, not a one-time setup. Be prepared to go back and tweak that master template a few times.