2026-07-28 — 4 min read
Keeping AI imagery brand-safe

"Brand-safe" gets treated like a vague quality label. In AI production it's specific, and most of what it actually requires happens before an image ever gets delivered, not after.
It starts with source assets, not prompts.
Brand-safe AI work is built from real product assets — actual geometry, actual labels, actual packaging — not a text description of what the product roughly looks like. A prompt alone can't guarantee a logo renders correctly, a label stays legible, or proportions stay accurate. Real source material is what keeps a generated image from drifting into something that technically resembles the product but wouldn't survive a brand review.
Every asset needs a record of how it was made.
Shot, generated, or hybrid — down to the individual asset, not the project as a whole. That record is what makes it possible to answer, quickly and confidently, exactly what went into an image if a client, a platform, or a regulator ever asks. Without it, that question turns into a reconstruction project under time pressure. With it, it's a lookup.
Likeness and IP get checked before delivery, not discovered after.
Generated imagery can drift into recognizable territory in ways a prompt never intended — a face that reads as a specific person, a style that leans too close to another brand's identity, a setting that resembles a real, identifiable location. Brand-safe work means catching that before it ships, not relying on the client's legal team to catch it after the campaign is live.
Governance isn't a one-time setup, it's a review on every project.
Guidelines, usage rights, and disclosure requirements aren't things a studio sets once and forgets. They get checked against the specific brief every time — the country the campaign runs in, the platform it's published on, whether real people's likenesses are involved, whether the content needs disclosure under current AI labelling requirements. Brand-safe isn't a fixed checklist. It's a review that happens per project.
Disclosure gets handled as part of delivery, not bolted on afterward.
Where a project requires transparency about AI involvement — under EU AI labelling rules or a platform's own policy — that gets built into what's delivered, not left for the client to figure out after the fact. Knowing which assets are AI-built, which are classically shot, and which are hybrid should be as available as the final files themselves.
What this actually protects against.
Not a hypothetical. A generated image with an unclear origin, an unverified likeness, or no usage-rights trail is a liability the moment it's published somewhere with legal exposure — a paid campaign, a platform with strict IP enforcement, a market with active AI regulation. The record and the review are what turn "we think this is fine" into "we can prove this is fine."