# GitHub brand guidelines, annotated

> GitHub’s brand toolkit names its open source typeface with download links and limits the logo to a few colors. Its best rules, quoted with notes, and its gaps.

- Published by: GitHub
- Format: Website, PDF and Figma files
- Date on the guide: None on the pages. The PDF has 2026 in its name
- Source: [GitHub Brand Toolkit](https://brand.github.com/), checked 2026-11-11

The GitHub brand toolkit covers the logo, color, typography, and voice. A PDF and Figma files are available next to the web pages. Its typeface, Mona Sans, is open source, so the guide can link directly to the files. The logo rules are clear on color, and on where the mark can stand alone.

## Best parts, quoted with notes

### Logo

> The standalone invertocat may be used in GitHub-owned environments or where the brand is already clearly established.

Has: where it applies. Says where the mark can appear on its own. Everywhere else, the lockup with the wordmark is the default. Source: [GitHub Brand Toolkit, “Invertocat”](https://brand.github.com/foundations/logo), checked 2026-11-11.

### Logo

> The Invertocat and our wordmark should only appear in white, black, or in few cases grey or green. Like text, the logo should be legible and pass accessibility requirements in all settings. When in doubt, use the highest contrast option.

Has: exact value, reason. Lists the allowed logo colors and gives a fallback. It does not say which cases allow gray or green. Source: [GitHub Brand Toolkit, “Color”](https://brand.github.com/foundations/logo), checked 2026-11-11.

### Color

> In most brand applications, green should be the key player. We use neutrals, black, and white to ground it and create focus.

Has: reason. Says that green leads and neutrals support it, and why. It gives no ratio, but example images show the balance. Source: [GitHub Brand Toolkit, “Primary palette”](https://brand.github.com/foundations/color), checked 2026-11-11.

### Color

> Always ensure that all text has a minimum contrast ratio of WCAG AA.

Has: exact value. Names a contrast level from the Web Content Accessibility Guidelines that a reviewer can test. Source: [GitHub Brand Toolkit, “Text and color contrast”](https://brand.github.com/foundations/accessibility), checked 2026-11-11.

### Typography

> Our typographic approach centers around Mona Sans, an open source super family with an optical size, 5 widths, italics, and a mono companion. Mona Sans is always improving and expanding, so make sure you’re always using the latest version.

Has: exact value, real file. Names the typeface, and the page's download buttons link to its open source repository. Source: [GitHub Brand Toolkit, “Mona Sans”](https://brand.github.com/foundations/typography), checked 2026-11-11.

### Typography

> Don’t use the other width styles available in Mona Sans. These are reserved for special events like Universe.

Has: where it applies, reason. Says which styles of the font are off limits and what they are kept for. Source: [GitHub Brand Toolkit, “Usage”](https://brand.github.com/foundations/typography), checked 2026-11-11.

### Voice and tone

> We bring Nerdy to the brand by walking the walk, but not in an overtly showy way. We don’t sweat the details, we relish in it.

Has: where it applies. Says what the trait is not, then lists separate rules for copy, design and events under it. Source: [GitHub Brand Toolkit, “Nerdy”](https://brand.github.com/brand-identity/attributes), checked 2026-11-11.

### Words and style

> GitHub is always one word with a capitalized G and H. When referring to GitHub the product, company, or service, keep it simple—GitHub.

Has: exact value. A spelling rule anyone can check, placed next to the logo it matches. Source: [GitHub Brand Toolkit, “Wordmark lockup”](https://brand.github.com/foundations/logo), checked 2026-11-11.

## What it leaves out

- The Voice and tone page only links to a separate guide in a GitHub repository, and that link returns 404 to the public. ([source](https://brand.github.com/brand-identity/voice-and-tone))
- The logo page gives no clear space or minimum size in words. Clear space exists only inside some of the downloadable logo files. ([source](https://brand.github.com/foundations/logo))

## What to take from it

- Link the font files from the rule that names the font.
- Say where a logo can appear alone. Make the full lockup the default everywhere else.
- Put the clear space in words, and not only in the files.

---

Source: https://aibrandguidelines.org/examples/github
Last updated: 2026-11-11
Published by Annotated Guidelines. Annotated Guidelines is run by the team at Rainbrand.
