Most brand projects end with one logo file. Maybe two. A designer hands over the Figma link, the client says thanks, and six months later the marketing team is using a stretched version because “the original didn’t fit the banner.”
The problem is not that logos get misused. The problem is that a brand with only one logo variant is a brand without options — and options are exactly what a team reaches for under deadline pressure.
The case for fewer variants than you think
There is a real temptation to deliver everything upfront: horizontal, stacked, reversed, icon-only, monochrome, gradient, badge version, wordmark-only, symbol-only. Ten variants to cover every edge case.
The result is usually chaos. When a team has ten logo files and no clear hierarchy, they pick the one that “looks right.” Which is the same thing as having no system at all.
The baseline that actually works in practice: four variants.
- Primary — the full logo, the canonical version, the one that defines the brand
- Horizontal — for headers, email signatures, document letterheads
- Icon/Mark — for favicons, app icons, small contexts where the wordmark disappears
- Reversed/Monochrome — for dark backgrounds and single-color print
That covers roughly 95% of real-world use cases. Everything beyond this should be justified by a specific, documented use case — not anticipated in advance.
Where it goes wrong at agencies
The variant problem compounds for agencies managing multiple client brands. A studio with 12 active clients, each with 8 logo variants, is sitting on 96 logo files. Distributed across Dropbox folders, Figma projects, and “final_final_v3” exports.
Two failure modes:
Too few variants: The client has only the primary EPS. Every social post, presentation, and merch order becomes a negotiation with the original file. The logo gets distorted. It gets used on white backgrounds when it needs contrast. It loses legibility at 32px.
Too many variants: The client has a folder of 15 files with no documentation about when to use which. The wrong version gets used anyway, just more confidently.
The solution is neither the minimal handoff nor the exhaustive export. It is a documented variant map: here are the four (or five) variants, here is when to use each, here is the context where each one breaks.
The icon variant deserves more attention than it gets
Of all the variants, the icon or symbol version is the one most frequently under-designed. It gets extracted from the full logo, scaled down, and declared done.
But the icon variant operates in a completely different context than the primary. It lives at 16px in browser tabs, at 60px in app stores, at 24px in Slack workspaces. Optical adjustments that seem unnecessary at full size become critical at small sizes — stroke weights, spacing, simplified shapes.
Brands like Airbnb and Nike have icon variants that are genuinely separate design decisions, not cropped versions of the primary. The “Bélo” and the swoosh work at any size because they were designed to. Most client logos were not.
If you are delivering a brand system and the icon variant is just the symbol cropped from the primary at original proportions, you are leaving a gap that will show up the moment the client builds a mobile app or a Slack integration.
TL;DR
Four variants is the practical baseline. Primary, horizontal, icon, reversed. Document when to use each. Anything beyond four needs a specific use case — not just “in case we need it.” The icon variant deserves a separate design pass, not just a resize.
A brand system that specifies this — with each variant labeled, contextualized, and accessible in one place — eliminates the “which version do I use?” question before it gets asked.