A brand kit is the working file set a team pulls from every day: logo variants with minimum sizes, colour values in every space you publish in, the type family with a scale, three photo examples that define the look, the fixed rules, and the templates. It is not a guidelines PDF. A PDF explains the brand. A brand kit is what people actually paste from.
Three people make assets. There are four versions of the logo, the orange is two oranges, and nobody can say which file is current.
This covers what goes in a brand kit, why guideline documents get ignored, and the difference between a kit people read and one they use.
Key Takeaways
- A brand kit is files, a brand guideline is a document. The guideline explains the reasoning. The kit is the set someone drags into a layout at 4pm. Most teams have the second problem and buy the first solution.
- Six things belong in it: logo variants with minimum sizes, colour values in hex, RGB, CMYK and Pantone, the type family with a scale, three photo examples, the fixed rules, and the templates. That is the whole list.
- Three photo examples beat three pages of photo direction. Written direction gets interpreted. Examples get matched.
- Give every file one canonical location and one name. Drift is almost never a taste problem. It is people using the file they can find rather than the file that is current.
- The rules that matter are the ones that are absolute. Two or three “never do this” rules get followed. Twenty preferences get ignored, and the twenty dilute the two.
- A kit that only exists as a PDF cannot be read by the tools that make the work. Whatever produces your assets needs to receive the constraints, not be told about them in a separate document.
- Version the kit and date it. An undated brand kit becomes four brand kits within a year.
What is the difference between a brand kit and brand guidelines?
Guidelines are a document that explains the brand. A brand kit is the set of files people use to make things.
A guideline says the primary orange expresses warmth and confidence, shows it at three sizes, and explains the clearance rule around the logo. That document is genuinely useful, once, to the person learning the brand. It is the wrong artefact for the person building an email at 4pm on a Thursday.
They need the hex value they can paste, the logo file that is already the right variant, and the answer to one question: which file is current. If getting those takes more than about thirty seconds, they will use the file already on their desktop, and that file is from March.
Most brands have written the guideline and skipped the kit. The symptom is the same every time: four logo versions in circulation and two slightly different oranges, with everyone agreeing the guideline is excellent.
What goes in a brand kit?
| Component | What it contains | Why teams get it wrong |
|---|---|---|
| Logo variants | Primary, stacked, icon-only, single colour, reversed. SVG and PNG. Minimum size and clear space for each | Shipping one lockup, so people improvise the rest |
| Colour | Hex, RGB, CMYK and Pantone for every brand colour, plus which are primary and which are accents | Hex only, so print and merchandise drift |
| Type | Family, the weights licensed, and a size scale with line heights | Naming a font nobody has a licence for |
| Photography | Three examples that are right, one that is wrong, plus a line on treatment | Writing adjectives instead of showing images |
| The rules | Two or three absolutes, stated as never statements | Twenty preferences that dilute the two that matter |
| Templates | The layouts used weekly, in the tool the team actually uses | Templates in software only the designer has |
Six components. If yours has fourteen sections, the extra eight are the reason nobody opens it.
Why do three photo examples beat three pages of photo direction?
Because written direction is interpreted and examples are matched.
“Warm, natural, editorial, uncluttered” describes several thousand distinct photographs. Four people read that sentence and picture four different images, all defensible. The words did their job and still produced drift, because adjectives are a compression of a visual decision and the decompression is lossy.
Three actual photographs collapse it. This lighting. This crop. This much background. A fourth image marked “not this” draws the boundary, and the boundary is where most disagreements live.
This is also the field that transfers cleanest to generated imagery. A model handed a reference image reproduces a look far more reliably than a model handed adjectives, which is the same reason it works on people.
How do you stop four versions of the logo?
One canonical location, one name per file, and a dated version on the kit itself.
Drift is a findability problem wearing a discipline costume. Nobody decides to use the old logo. They search Slack, find a PNG from March, and it looks right. The old file was easier to reach than the current one, and that is the entire mechanism.
Three fixes, in order of effect:
- One location that everyone knows. Not a folder per campaign with a copy of the logo in each. One place, linked from wherever the team starts their day.
- Names that carry the variant and the version. A file called “logo-primary-full-colour-v3.svg” cannot be confused with “logo-icon-reversed-v3.svg”. A file called “logo_final_2.png” can be confused with everything. The naming convention is worth writing down once.
- Delete or archive superseded files. A retired logo left in the shared folder will be used. The most reliable way to stop a file being used is for it not to be there.
The same three fixes apply to every asset you produce afterwards, which is why the kit and where finished assets live are really one problem.
Why do most brand rules get ignored?
Because there are too many, and the format invites skimming.
A rules section with twenty entries reads as preferences. People follow preferences when convenient and skip them when the deadline is close, which is exactly when they are making the asset. Worse, twenty rules hide the two that genuinely matter, so the two get skipped along with the eighteen.
Write two or three absolutes, as never statements, and stop:
- Never place the logo on a background below this contrast ratio.
- Never stretch, rotate, recolour or add effects to the logo.
- Never use the accent colour for body text.
Three rules get remembered. Everything else is a preference, and preferences belong in the guideline document where they can be read once by someone learning the brand.
Does a brand kit work when assets are generated?
Only if the thing generating them can receive it. A PDF cannot be read by a model.
This is the part that changed. When every asset was made by a person, the kit’s job was to inform a human, and a document did that. When some of the work is generated, the constraints have to be an input to the generation, not a document sitting next to it. A brand kit that lives only as a PDF governs the half of your output a person makes and governs nothing else.
What transfers well: the three reference photographs, the colour values, the fixed never rules, and the templates. What transfers badly: adjectives, tone-of-voice essays, and anything phrased as a principle rather than a constraint.
DesignerBox holds this as a brand profile that a saved workflow reads on every run. Build the job once against the kit, then run it again for the next product and the one after, and row five hundred comes back with the same colours, the same type and the same treatment as row one, without anyone re-typing the rules. The brand consistency guardian is that check running over a whole set rather than over one file. Shared brand kits across a team are Ultra only, at $200 a month billed monthly, so below that the kit is per-account and a small team keeps one canonical copy. Either way the constraints have to travel with the work, not sit beside it.
How often should a brand kit be updated?
Date it, review it twice a year, and version it whenever a file changes.
An undated kit becomes several kits within a year, because there is no way to tell which copy is newest. Put a version number and a date on the kit itself, not only on the individual files.
Review it at a fixed point rather than when someone notices a problem. Two things go stale fastest: the photography examples, because the look moves before anyone declares it moved, and the templates, because platform sizes change. Both are the fields people quietly work around rather than report, so the drift shows up in the output before it shows up in a conversation.
FAQ
What is a brand kit?
The working file set a team pulls from to make anything: logo variants with minimum sizes and clear space, colour values in hex, RGB, CMYK and Pantone, the type family with a size scale, three photo examples, two or three fixed rules, and the templates used weekly. It is what people paste from, not what they read.
What is the difference between a brand kit and a style guide?
A style guide explains the brand and the reasoning behind it, and is read once by someone learning it. A brand kit is the files, and is used every day. Most teams have written the guide and skipped the kit, which is why the guide is excellent and the output still drifts.
What should be in a brand kit for a small business?
The same six components, smaller. Two logo variants rather than five, two colours, one type family with three sizes, three photo examples, two never rules, and the two or three templates you actually use each week. A small kit that is current beats a comprehensive one that is out of date.
How do I stop my team using old logo files?
Give every file one canonical location that is easier to reach than a Slack search, name files so the variant and version are readable, and archive superseded files out of the shared folder. People use the file they can find, so the fix is making the current file the findable one.
Do I need Pantone colours in a brand kit?
Only if you print or produce physical goods. Hex covers screens, RGB covers digital design files, CMYK covers process printing, and Pantone covers spot colour and merchandise. If you never leave the screen, hex and RGB are enough, and adding the rest is upkeep with no payoff.
Can a brand kit be used by AI tools?
The parts expressed as inputs can be: reference images, colour values, and constraints stated as rules. The parts expressed as prose cannot, because a model reads a reference image far more reliably than an adjective. If any of your output is generated, the kit needs to exist in a form the generator receives, not only as a document.
How many rules should a brand kit have?
Two or three, phrased as never statements. Longer lists read as preferences and get skipped under deadline, and they bury the rules that genuinely matter. Everything beyond the absolutes belongs in the guideline document, not in the kit.
Sources
- DesignerBox brand profiles and workflows (designerbox.ai, accessed September 2026)
Brand kit components drawn from standard commercial brand practice. Product capabilities verified from DesignerBox documentation as of September 2026. Individual results vary.
