---
title: "What is a brand style guide? What to include, and a template | Rainbrand"
description: "A brand style guide, also called brand guidelines or brand standards, sets the rules for how a brand looks and sounds. Download a Word template with a completed example section, then see what each section should settle and a published guide that does it well."
url: "https://www.rainbrand.com/blog/what-is-a-brand-style-guide/"
---

By Siddharth Borderwala

Published 17 Nov 2026

13 min read

# What is a brand style guide? What to include, and a template

A brand style guide, also called brand guidelines or brand standards, sets the rules for how a brand looks and sounds. Download a Word template with a completed example section, then see what each section should settle and a published guide that does it well.

## TL;DR

A brand style guide is the document that sets how a brand looks and sounds: its logo, colours, typefaces, imagery, voice and writing rules, with the files to use. Brand guidelines, brand standards and brand book usually mean the same thing. A useful one gives rules someone could check, explains the ones that aren't obvious, and links the real files.

A brand style guide is the reference anyone making something for a brand works from. It says which logo goes where, gives the exact colours and typefaces, describes the photography and sets out how the brand writes, so a designer, an agency, a partner or an AI agent can make an ad, an email or a slide without asking the brand team each time.

It can be a PDF, a website or a shared document. What decides whether it's any use is [how specific it is](https://www.rainbrand.com/blog/brand-guidelines-examples/). "Use our blue" leaves every reader to guess. "Use the green logo only on black or white" doesn't, and anyone can check whether a finished asset followed it.

## The template and its sections

[Download the brand style guide template](https://www.rainbrand.com/downloads/blog/what-is-a-brand-style-guide/brand-style-guide-template.docx), a Word document for the people who use your brand. It has the sections below, each with a table of decisions to fill in and a line from a published guide showing what a checkable rule looks like, and a change log at the end.

It also has one section already filled in: Asana's logo rules, taken from its public brand page, so you can see what a finished section looks like. That includes the gap Asana's page leaves open, a minimum size, which is the kind of thing a completed section should flag rather than paper over. If you want a file written for AI agents to read instead, start from the [Markdown brand guidelines template](https://www.rainbrand.com/blog/markdown-brand-guidelines-template/).

These are the sections, with a published guide that does each one well:

| Section | What it settles | A guide that does it well |
| --- | --- | --- |
| Foundations | What the brand does, for whom, and how it should feel | Customer.io |
| Logo | Versions, clear space, minimum size, backgrounds, misuse | Asana |
| Colour | Exact values, roles and proportions | GitHub |
| Typography | Typefaces, their roles and where to get them | NASA |
| Imagery | What photos and illustrations show, and how | Experian |
| Voice and tone | How the brand sounds, and how that shifts | Dropbox |
| Writing style | Names, numbers, capitals and word choices | Intuit, Mailchimp |
| Accessibility | Contrast, and meaning that doesn't rely on colour | GitHub |
| Applications | How it looks on the things people make, with templates | Experian, GitHub |
| AI-made assets | What AI tools may make, and which files they must use | Customer.io, Experian |
| Files and changes | Where the files are, who decides and what changed | Asana, NASA, Intuit |

## What each section should settle

### Foundations

Open with what the brand does, who it's for and how it should feel. It gives the later rules a reason, and it's where a reader turns when no rule covers their case. Keep it short. [Customer.io's foundations](https://brand.customer.io/docs/foundations) fit on one page: a mission, "Transform the way companies communicate with customers", a vision, three attributes (powerful, adaptive and helpful, each explained in a sentence or two) and the tagline "More impact from every message".

Write [approved wording](https://www.rainbrand.com/blog/brand-messaging-framework/) out in full. People and agents paste a tagline or a boilerplate paragraph as it stands; give them a summary and they'll paraphrase it.

### Logo

List each version of the logo with a link to its file, then say where each one goes. [Asana's logo guidelines](https://asana.com/brand) set rules anyone can check:

- **Versions:** the horizontal lockup is the primary logo. The vertical lockup is only for when space or size rules the horizontal one out.
- **Clear space:** "equal to the height of the symbol" on every side, which Asana calls "the absolute minimum safe distance."
- **Colour:** the three-dot symbol is always coral. The wordmark is black on white or light grey, and white on black.
- **Misuse:** no past versions, no recolouring, no effects or drop shadows, no symbol without the wordmark or wordmark without the symbol, and no secondary brand colours as backgrounds.
- **Partners:** beside a partner's logo, the two are the same size, with the width of Asana's three-dot symbol between them.
- **Files:** a downloadable guidelines kit, linked from the same page.

![Asana's horizontal logo inside a grid of guides, with the clear space on each side marked x, equal to the height of the three-dot symbol](https://www.rainbrand.com/downloads/blog/what-is-a-brand-style-guide/asana-logo-clear-space.webp)

Clear space

![Asana's logo on black: the coral three-dot symbol beside a white wordmark](https://www.rainbrand.com/downloads/blog/what-is-a-brand-style-guide/asana-logo-on-black.webp)

On black

![Asana's logo recoloured entirely in magenta, struck through with a red diagonal line](https://www.rainbrand.com/downloads/blog/what-is-a-brand-style-guide/asana-logo-recoloured.webp)

Not allowed: recoloured

Three of the illustrations from [Asana's brand page](https://asana.com/brand).

Asana's page doesn't set a minimum size. Many guides add one, in pixels for screens and millimetres for print, so the logo never shrinks past the point where its details blur. [Logo usage guidelines](https://www.rainbrand.com/blog/logo-usage-guidelines/) goes through each of these rules with more examples.

The links to the files matter more than they used to. Image models redraw a logo from what they've seen rather than copying it, and small details go wrong. That's why [Customer.io](https://brand.customer.io/docs/ai-usage-guidelines) tells its team to take logo files from its guidelines site, "as AI recreations can introduce subtle inconsistencies that will render the logo off-brand." An agent laying out a slide or a page can place the real SVG if your guide links it. From a picture of the logo, it can only imitate.

### Colour

Give every colour a name, its exact values for each medium and a role. [GitHub's colour page](https://brand.github.com/foundations/color) lists GitHub Green as `#0FBF3E`, with its RGB and CMYK values and spot colour 360 for print. Then it says how much to use: "In most brand applications, green should be the key player", grounded by neutrals, black and white, and its examples show "mostly neutral colors with small moments of green."

![GitHub's light example layout: the Invertocat, a placeholder headline in black on pale grey, and a narrow strip of green pixel blocks down the right side](https://www.rainbrand.com/downloads/blog/what-is-a-brand-style-guide/github-colour-proportion-light.webp)

Light

![GitHub's dark example layout: a placeholder headline in white on near-black, with an Octocat illustration over blocks of green and blue on the right](https://www.rainbrand.com/downloads/blog/what-is-a-brand-style-guide/github-colour-proportion-dark.webp)

Dark

GitHub's two examples of "a good proportion of color", from the [colour page of its Brand Toolkit](https://brand.github.com/foundations/color). The headlines are GitHub's placeholder text.

Proportion is the part a row of swatches can't show. Without it, an accent colour can take over a layout and still follow every rule. Give each value a role too, such as text, background or accent. An agent building a page can use `#0FBF3E` exactly; it can do nothing exact with "our signature green".

### Typography

Name each typeface, the job it does and where to get it. [NASA's guidelines](https://www.nasa.gov/nasa-brand-center/brand-guidelines/) split by medium. For print, the recommended typefaces are Helvetica and Garamond, and "Helvetica is required for the NASA identifier configuration and NASA portal (web) address." Its website's design system, Horizon, uses Inter for display type and headings, Public Sans for body copy and DM Mono for "numbers and small labels", each linked to Google Fonts. A designer laying out a poster and a developer building a page can both see exactly what to use.

Link the font files or the licensed source, and give a fallback. [GitHub](https://brand.github.com/foundations/typography) links Mona Sans, its open-source typeface, from the page, and adds rules such as "Don't use letterspacing to track letters." An agent making a page or a deck can embed a linked font file. Image models can't reproduce a typeface reliably, so type over a generated image is usually set afterwards; [applying brand guidelines to AI images](https://www.rainbrand.com/blog/apply-brand-guidelines-to-ai-images/) covers how.

### Imagery

Describe what the photographs show and how they're taken, then link approved examples. [Experian's photography guidelines](https://www.experian.com/brand-central/brand-identity/photography) are specific enough to brief a photographer:

- people in candid moments that "look natural and unfiltered, never staged or over edited";
- images that are "fully saturated", with a bright, optimistic look;
- subjects off-centre, with a shallow depth of field;
- landscape framing "to allow space for content in layouts";
- no visual metaphors, which "can seem overused and unoriginal."

Pair rules like these with three to five approved images. Image models follow what they see more closely than what they read, so a reference photo carries detail that adjectives can't. Experian's [generative AI guidelines](https://www.experian.com/brand-central/brand-guidelines/genai-guidance) lean on this section: "Ensure AI-generated images and videos follow Experian photography standards and are photorealistic."

### Voice and tone

Voice is how the brand sounds every time; tone is how that shifts with the situation, from a launch to an apology. Most guides name three or four traits. The useful ones turn each trait into instructions. [Dropbox's voice](https://brand.dropbox.com/voice-and-tone) is "simple, helpful, human, & magic", and "simple" means "Keep it crystal clear. Trim words. Use strong nouns. Craft a story." "Human" means "Stay real and relatable. Write the way you talk. Avoid jargon."

Then add approved copy, and say how the tone changes in the situations you write for most; [brand voice vs tone](https://www.rainbrand.com/blog/brand-voice-vs-tone/) shows how to map them. [Brand voice examples](https://www.rainbrand.com/blog/brand-voice-examples/) reads seven published voice guides in detail, and [writing a brand voice guide for AI](https://www.rainbrand.com/blog/write-a-brand-voice-guide-for-ai/) shows how to turn traits into rules an agent can follow.

### Writing style

This is the editorial part: how to spell names, when to use capitals, how to write numbers and dates, and a word list. It's the easiest section to make exact. [Intuit's content design system](https://contentdesign.intuit.com/style-and-usage/numbers/) uses numerals by default, puts the minus sign "in front of the currency symbol" for negative amounts and doesn't use ordinals in dates. [Mailchimp's word list](https://styleguide.mailchimp.com/word-list/) settles single words: "login (noun, adjective), log in (verb)".

Rules this small are easy for an agent to apply and for a reviewer to check, so write them down even when they seem too obvious to need saying.

### Accessibility

Set a minimum contrast and say how meaning is carried without colour. [GitHub](https://brand.github.com/foundations/accessibility) asks that "all text has a minimum contrast ratio of WCAG AA" and says "Never use only color to convey meaning." AA means at least 4.5:1 for normal text and 3:1 for large text ([W3C](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html)). List which of your colour pairs pass, so nobody has to test them again.

### Applications

Show the brand on the things people make, and link a template and a finished example of each. Experian's guidelines have pages for the web, video, social media, events and trade shows. GitHub's "brand in action" section covers presentations, social posts, ebooks, events and swag. Finished examples show proportion, density and spacing in a way rules can't, for a new designer and an agent alike.

### Rules for AI-made assets

More guides now have a section for this, and the good ones are specific. [Customer.io's AI guidelines](https://brand.customer.io/docs/ai-usage-guidelines), published in May 2026, require the official logo files rather than AI recreations, allow AI-assisted visuals that get "a Brand review before publishing as official assets", and ask whoever submits them to "note how AI was used so reviewers can give faster, better feedback." [Experian's](https://www.experian.com/brand-central/brand-guidelines/genai-guidance) say which tools are allowed ("enterprise-approved GenAI tools" only), require written consent before using anyone's likeness, and ask teams to disclose AI "where it could influence customer understanding, regulatory interpretation, or trust."

Between them they cover what this section needs: which tools may be used, what AI must never generate (usually the logo and real people), which files to use instead, who reviews the result before it's published, and when to say AI was involved.

### Files and changes

Finish with [where to get everything](https://www.rainbrand.com/blog/branding-kit/), who decides and what changed. Asana's logo page links a downloadable guidelines kit. Experian's guidelines link to its Brand Asset Hub and a logo request page. Date the guide and keep a record of changes: NASA's page shows when it was last updated, and Intuit's content design system has a "What's new" page. A reader who can see the date of the last change knows whether a rule is current.

## Style guide, guidelines or standards?

Mostly the same thing. Publishers even disagree with themselves: Bynder's glossary says a brand style guide is ["more formally known as 'brand guidelines'"](https://www.bynder.com/en/glossary/brand-style-guide/), while its longer [brand guidelines guide](https://www.bynder.com/en/glossary/brand-guidelines-definition/) says a style guide "is narrower. It focuses on written language". The names organisations give their own documents show the distinctions that matter in practice:

| What it's called | Whose | What it covers |
| --- | --- | --- |
| Brand Toolkit | [GitHub](https://brand.github.com/) | The whole identity, from logo to motion |
| Content Style Guide | [Mailchimp](https://styleguide.mailchimp.com/) | Voice, grammar and a word list |
| Design system | [Atlassian](https://atlassian.design/) | Components and code for building a product |
| Brand Guidelines, headed Graphic Standards | [NASA](https://www.nasa.gov/nasa-brand-center/brand-guidelines/) | Rules that follow a federal regulation |

- **Editorial style guide.** If your writers say "style guide" and mean spelling and grammar, keep it as one section of the brand guide, so the two never contradict each other.
- **Design system.** It's the components and code for building a product. In Bynder's words, brand guidelines "inform a design system, but the two are not the same."
- **Brand standards.** The word fits when the rules bind people outside the brand team and someone checks them. NASA's insignia, seal and "worm" logotype follow [14 CFR Part 1221](https://www.law.cornell.edu/cfr/text/14/part-1221), so its rules read as requirements: the worm "should never appear without the Insignia in appropriate proximity except on commercial merchandise." Its 1976 [Graphics Standards Manual](https://www.nasa.gov/wp-content/uploads/2015/01/nasa_graphics_manual_nhb_1430-2_jan_1976.pdf) set the pattern.

Beyond those, call it whatever your team will search for.

## How agents use a style guide

[Frontify's style guide page](https://www.frontify.com/en/guide/style-guide) says a guide "now has a second audience". AI agents make ads, emails, slides and pages from the same guide your designers use, and they [read it more literally](https://www.rainbrand.com/blog/make-brand-guidelines-ai-ready/) than people do. They need:

- **The files, not pictures of them.** A PDF page showing the logo gives an agent an image to copy. A link to the SVG gives it the logo.
- **Values, not names.** A brand's own name for a colour means nothing to a model without the value behind it.
- **The part of the guide that fits the task.** A person opens the guide at the page they need. Given the whole guide for every task, an agent has to sort out which rules apply, and a print rule can end up on a web page. [Brand guidelines vs brand context](https://www.rainbrand.com/blog/brand-guidelines-vs-brand-context/) explains why more context isn't better.

Here is one rule travelling to one task. Dropbox's voice traits, quoted in the voice section above, include "simple" and a fourth, "magic": "Charm them with wit. Clever is great. Fresh language is even better." They're written for everything Dropbox says. A message shown in an empty shared folder needs something narrower.

Rainbrand maintains a brand's guidelines and files as context that AI agents call while they work. Its [brand guidelines library](https://www.rainbrand.com/brand-guidelines/dropbox/) has a page for Dropbox, built from brand.dropbox.com, and on November 16, 2026 a [Brief](https://docs.rainbrand.com/guides/request-brief) was requested for that brand: the guidance and files one task needs. The task was the heading, one sentence and button label shown when someone opens a shared folder with no files in it yet. The Brief turned the two traits into this:

> Keep the heading, single-sentence body, and button label concise and clear; use plain language and strong, specific nouns.

> A small flash of wit or fresh language is okay only if it doesn't obscure the empty-folder status or what the user can do.

"Simple" became instructions sized for three short lines. "Magic" stayed, but with a limit for this situation: wit only if the folder's status and the next step stay clear. The Brief also said where the guide stopped. The brand source has "no prescribed empty-shared-folder wording, product-specific terminology, or button action", so the button has to come from what the product actually does, not from the brand.

That is the step a person takes when they open a style guide at the page they need, and it works best when the guide's rules can be checked. To try it with your own guide, [add your brand](https://docs.rainbrand.com/guides/create-brand) from your style guide, website and files, request a Brief for one task you know well, and compare what it picked with what you would have picked.

## FAQ

### How long should a brand style guide be?

As long as the decisions you've made, and no longer. Asana's logo and trademark rules fit on one web page, Customer.io's guidelines run to eight pages, and GitHub's toolkit has more than 20. A small company with one logo, a few colours, one typeface and a voice can cover it all in a few pages.

### Who writes and owns a brand style guide?

The designer or agency that creates the [identity](https://www.rainbrand.com/blog/what-is-brand-identity/) usually writes the first version. After that it needs one named owner, usually in marketing or the brand team, who approves exceptions, records changes and answers questions. Put that person's name and contact details in the guide.

### Should a style guide be a PDF or a website?

A website is easier to keep current and lets people link to a single rule; a PDF is easier to hand to a printer or an agency. Either works for agents if the rules are text and the files are linked. A PDF whose rules are set inside images gives an agent little to read. [Which brand guideline formats AI tools can use](https://www.rainbrand.com/blog/brand-guideline-formats-for-ai/) compares the options.

### Can AI write our brand style guide?

An agent can draft one from your website, existing files and past assets, and it's a quick way to find what your brand does consistently but has never written down. The decisions still have to be yours: which logo goes on which background, which colours text may sit on, what the brand never says. [Turning your website into brand guidelines](https://www.rainbrand.com/blog/turn-website-into-brand-guidelines/) covers how to check a draft against the evidence.

## More in Brand guidelines

[All 18 Brand guidelines articles](https://www.rainbrand.com/blog/topics/brand-guidelines/)

- 17 Nov 2026 18 min read

    ### [Brand guidelines examples: 12 real brand books and what to copy from each](https://www.rainbrand.com/blog/brand-guidelines-examples/)

    Twelve brand guidelines you can open today, from Mastercard’s logo rules to NASA’s 1976 standards manual, with the exact rule worth copying from each, which ones an AI agent can read, and what it took to correct an agent’s version of Starbucks.

- 17 Nov 2026 10 min read

    ### [Branding kit checklist: what to include, file formats and real examples](https://www.rainbrand.com/blog/branding-kit/)

    What a branding kit should contain, from logo files and colour values to fonts, templates and rights; what to agree with your designer; what real companies’ kits hold; and a bounded web sample kit, with its index, a template and an asset made from it.

- 17 Nov 2026 11 min read

    ### [Logo usage guidelines: what to include and how to write them](https://www.rainbrand.com/blog/logo-usage-guidelines/)

    Logo usage guidelines say which logo goes where, how much space it needs, how small it can go, which colours and backgrounds it allows and what never to do. See how Amazon and Strava write each rule, how AI tools get logos wrong, and a template to download.

## Connect Rainbrand.

Use Rainbrand with your agents, or embed it into your product.

[Use it with your agents](https://docs.rainbrand.com/mcp/getting-started) [Integrate it with your product](https://docs.rainbrand.com/getting-started/embed-into-your-product)

### ChatGPT + Codex

1. Open the Rainbrand plugin and add it.

    [Open Rainbrand plugin](https://chatgpt.com/plugins/plugin_asdk_app_6ac6e5030ec88191a88001f6dc0628ca)

2. Connect your Rainbrand account when asked. It works in ChatGPT and in Codex.

### Claude

1. Open the Rainbrand connector in Claude and add it.

    [Open Rainbrand connector](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Rainbrand&connectorUrl=https%3A%2F%2Fmcp.rainbrand.com%2Fmcp)

2. Select Connect, then sign in to Rainbrand.

You can also install the [Rainbrand Skill](https://docs.rainbrand.com/mcp/getting-started#standalone-rainbrand-skill) or the [plugin](https://github.com/rainbrandai/rainbrand-skills/releases/latest/download/rainbrand.claude-plugin.zip).

### Claude Code

1. Add Rainbrand's plugin marketplace in your terminal.

    ```
    claude plugin marketplace add rainbrandai/rainbrand-skills
    ```

2. Install the Rainbrand plugin, including its Skill and MCP connection.

    ```
    claude plugin install rainbrand@rainbrand
    ```

3. Start a new Claude Code session, then use /mcp to sign in to Rainbrand.

You can also [connect with MCP](https://docs.rainbrand.com/mcp/getting-started#claude-code-installation-options) or install the [Rainbrand Skill](https://docs.rainbrand.com/mcp/getting-started#standalone-rainbrand-skill).

### Cursor

1. Add Rainbrand to ~/.cursor/mcp.json.

    ```
    { "mcpServers": { "rainbrand": { "url": "https://mcp.rainbrand.com/mcp" } } }
    ```

2. Sign in from the Cursor CLI.

    ```
    agent mcp login rainbrand
    ```

You can also install the [Rainbrand Skill](https://docs.rainbrand.com/mcp/getting-started#standalone-rainbrand-skill) or the [plugin](https://github.com/rainbrandai/rainbrand-skills/releases/latest/download/rainbrand.cursor-plugin.zip).

### API

1. Create an API key in your account settings, then list your brands.

    ```
    curl https://www.rainbrand.com/api/v1/brands -H "x-api-key: $RAINBRAND_API_KEY"
    ```

Integrating Rainbrand into your app? [Read the API docs](https://docs.rainbrand.com/api).

The brand layer for agents

Rainbrand builds and maintains shared brand context for your agents and products

[Get started](https://www.rainbrand.com/auth/sign-in) [Read the docs](https://docs.rainbrand.com/)

[View pricing](https://www.rainbrand.com/pricing/)
