GitHub’s brand is visually expressed in a multitude of ways depending on your project, audience, and more. Use this document to manage expectations on what should be created for your project.


Brand isn’t limited to one particular logo or graphical asset—one project may receive a series of icons, another may warrant a fully illustrated octocat, and others may receive a full logo. And while branding assets account for a significant portion of your project’s branding, the voice and tone of your messaging is just as important.

Please consult the Content section of the Brand Guide for how to pair effective branding with effective messaging.


At a high level, here’s how we use our brand assets to represent the various aspects of GitHub:

  • Invertocat represents the company and product.

  • Invertocat logos represent our products, programs, and events under our IP.

  • Custom logos can be used where an immediate GitHub-owned connection isn’t required (e.g., Atom and Electron). Most things at GitHub do not warrant custom logos, as we want our customers to have an immediate brand connection through the Invertocat. Do not create your own custom logos; most of the time, it’s unnecessary.

  • Illustrated octocats are for GitHub owned programs and customer segments. Do not use these to represent GitHub. Do not create your own octocats.

  • Icons are for conveying various concepts and ideas. Icons alone are not branding; they require a clear logo and familiar context to be successful.

Keep reading below to dive into more detail on these.


For the company itself, stick to the Invertocat, and the Invertocat alone without modification or an additional “GitHub” in text near it.

For the company, as well as products, programs, and events that the company owns, we require the use of an Invertocat logo. The Invertocat is GitHub’s primary logo mark, the symbol of the octocat.

Example Invertocat logo

An Invertocat logo should be no smaller than 32px tall, with at least half the height in negative space around all sizes (e.g., 16px at the absolute minimum). Less space may be used in GitHub products where navigation constraints may apply.

Example Invertocat logo dimensions

GitHub’s name is never included. Remember to consider name length for these, as anything too long doesn’t read well across all implementations. Similarly, do not attempt to stack words in an Invertocat logo—single line only.

For additional considerations, please direct questions to the Design team.

Custom logos

Custom logos are limited to GitHub owned IP, including our official applications (e.g., Desktop and Mobile) and those that doesn’t require an immediately clear connection to GitHub (e.g., Atom and Electron).

The overall style of the icon may depend on where it will live, but by default a white invertocat with black background is required. In the case of official applications, we require the Invertocat to be used as the primary element in the logo.

In these cases, the supporting context should make it clear that these products come from GitHub, both in overall aesthetic and direct written attribution somewhere in the project (e.g., footer of website or document).

Illustrated octocats

Select GitHub owned programs and customer groups can be branded with illustrated octocats from the internal Design team. Illustrated octocats represent every member of our customer audience, signaling their representation, belonging, and individual identity.

Do not create your own octocats. Do not create derivative works from the octocat. Do not modify the octocat.

For more details on requesting an octocat, see the Mascots section of the Brand Guide.

Additional logos and mascots

Through history and acquisition, GitHub has become home to more mascots than just the Octocat. Hubot was created and released in house, and he and Mona have been joined by some amazing friends. The rules that apply to our Octocats also apply to these mascots—do not modify, distribute, or use without permission from the Design teams.

For more details on requesting an octocat, see the Mascots section of the Brand Guide.


Icons are the bare minimum when it comes to GitHub branding as most of our icons are used for multiple concepts and ideas, and not an individual product or program. As such, their use should be limited to contexts where, together with additional icons, they bring through GitHub’s overall branding.

Icons are used to represent product features, benefits, workflows, customer audiences and segments, customer benefits, and general developer concepts.

These icons are separate and distinct from our product icons, Octicons. Whereas Octicons are simple and product feature focused, brand focused icons are more visually complex with richer details and higher fidelity.

For more details on how to create and request icons, please consult the Icons section of the Brand Guide.

In this section

  • Philosophy

    As people become more familiar with GitHub, we can begin to move introduce new or different brand elements to celebrate their level of brand engagement and affinity.
  • Attributes

    Articulating and upholding our brand beyond the aesthetic and trends of the day by focusing on what we and our customers truly value.
  • Names

    Naming things is hard, but thankfully, we don't need to debate our company name. Here's how to refer to our platform and business.
  • Logos

    Learn about our logos. how and when to include the GitHub logomark or logotype, how we identify sub-brands, and more.
  • Extensions

    For projects that aren't part of the core GitHub platform or product, we use extensions to signal our involvement.
  • Typography

    Type should be approachable and informative without trying to be futuristic or stylish. Like GitHub's interface, it shouldn't stand out and should appear uniform.
  • Microsoft & GitHub

    Learn how and when to use GitHub and Microsoft brand elements together.