What goes in a brand guidelines PDF — the 9 canonical sections
1. Cover and quick reference
Brand name, version number, last-updated date, and the URL where the latest version lives. Add a one-page 'TL;DR' index card with primary color hex, primary font name, and a sample logo lockup. Most readers reference only this page.
2. Brand voice and personality
3–5 personality traits (e.g. 'calm, operator-to-operator, distinctive, plain-spoken'), a tone profile (where you sit on formal-casual, serious-playful, reserved-bold sliders), and 4–6 do/don't writing examples. Skip brand archetype frameworks — they impress other branding folks, not the people applying the guidelines.
3. Color system
Each color with: name, role (primary/secondary/accent/neutral/semantic), hex value, RGB, HSL, and 9-step shade scale. Include the WCAG contrast matrix — every role pair tested against the others. This is the single most useful section for engineers; treat it as canonical.
4. Typography system
Three fonts max: heading, body, accent. For each: family name, weight set used, license info, Google Fonts URL or @import statement, and a type scale (Display/H1/H2/H3/Body/Small/Mono with sizes and line-heights). Include a specimen page showing a paragraph in each font at body size.
5. Logo and lockups
Six lockups: primary, stacked, reversed, mark only, wordmark only, mono. Show clear-space rules around each. Include a 'misuse' page with 6–8 examples — wrong color, wrong proportion, wrong placement on photography, etc. Misuse examples save more brand drift than use examples.
6. Accessibility report
WCAG 2.2 contrast matrix (every role pair, with AA/AAA pass/fail flags), plus accessibility usage rules (which colors are large-text-only, which are AAA, where focus rings are required). This is increasingly required by enterprise procurement teams; including it preempts a back-and-forth.
7. In-application — favicon, email, social, merch
Show the brand applied to the contexts your team actually ships in: favicon (16/24/32/48/64), email signature, Twitter/X header, LinkedIn header, Instagram square and story, merch t-shirt mockup. One page per context.
8. Out-in-the-wild — real product UI examples
Show the brand applied to a marketing landing, an admin dashboard, and a mobile app screen. This is the section that proves the system works in production, not just in mockups. ColorFlowPro generates these previews automatically; if you're building the PDF manually, sketch them in Figma in 30 minutes.
9. Downloads and developer assets
A page-long manifest of every downloadable asset and where it lives: logos in SVG/PNG @1x/2x/3x, design tokens in CSS/Tailwind/SCSS/JSON, Figma styles file, social templates folder, accessibility report. Link to a shared drive or your asset CDN — this PDF is the index, not the storage.
How long should a brand guidelines PDF be?
10–20 pages for early-stage startups, 20–40 pages for established companies, 40+ pages only for multi-brand portfolios or large enterprises. Anything past 50 pages is performative — nobody reads it, and the team-internal Notion/Slack canonical replaces it within months.
Do you need a designer to make a brand guidelines PDF?
No. ColorFlowPro auto-generates a multi-page PDF (cover, all 9 sections, downloads manifest) on every brand kit. The Free plan PDF is watermarked; Creator and Studio plans export clean. If you're not using ColorFlowPro, Notion's free brand book template is the next best alternative — designed for non-designers, reasonably professional output.
What to NOT include
- Brand history or origin story. Nobody reading a PDF cares; put it on the about page.
- Mission and vision statements. Same — they belong elsewhere.
- Marketing strategy or messaging frameworks. Different deliverable.
- Photography style guides at MVP stage. Premature; add when you commission custom photography.
- Multiple language voice guides. Localize when you're actually localizing, not before.