Fonts and typography

The fonts we use and the way we apply them affect the way our audience perceives our brand just as much as the words that we write. To make our words unmistakably Red Hat, we use the Red Hat® font family—with straightforward and approachable typography.

Font family

Font family

Launched as part of the Open Brand Project in 2019, our font family was created for Red Hat in collaboration with type designer Jeremy Mickel. The family includes 3 fonts: Red Hat Display, Red Hat Text, and Red Hat Mono. Their design is based on who we are: real people with big ideas creating platforms that power technology innovation.

We’re committed to making the things that we create available to everyone. Just like our software, our fonts are open source. They’re free for anyone to download and use under the SIL International license.

Red Hat Display

A diagram highlights the unique features of Red Hat Display font letterforms. Highlighted features include wide letters, tall x-height, open apertures, even strokes, a 12º angle on ascenders, and natural curves.

Our default font—and the one used in our logo—is Red Hat Display. Geometric, sans serif letterforms with even strokes reinforce our tone of voice and reflect our technical expertise and engineering. Meanwhile, human touches—like curved details, tapered links, and angled ascenders—disrupt the rigidity to represent our people and call back to our brand’s history.

We use Red Hat Display at large sizes or in bold (or both) to grab attention. If you’re not sure which font to use, default to Display.

Red Hat Text

Various weights of Red Hat Text.

Red Hat Text takes all of the personality from Display and optimizes it for more demanding applications. As the name implies, it’s easier to read in paragraphs or when text is used at small sizes—like in a whitepaper or tooltip.

To increase readability, Text has more height difference between the upper- and lowercase letters, more space between narrow characters, and more variation in letterform stroke weights.

Red Hat Mono

Various weights of Red Hat Mono.

Red Hat Mono was created to distinguish code from natural-language text. Mono stands for monospaced, meaning each letter takes up the same amount of horizontal space. This creates neat columns of text and makes scanning code easier.

Mono should only be used when demonstrating code snippets in communications and interfaces, or as a stylistic approach for a more technical audience like the Red Hat Developer Program or the Code Comments podcast.

An example of Noto Sans in simplified Chinese.

Non-Latin character sets

The Red Hat font family supports the extended Latin character set. For languages that use other character sets—like Chinese, Japanese, Korean, and Cyrillic—use the Noto Sans font family.

Noto is an open licensed font from Google Developed to support all languages without the little boxes—known as tofu—that show up when a font doesn’t support a character. The simple, clean design makes it a good counterpart to the Red Hat font family.

Gallery

A screenshot shows the Red Hat solutions homepage featuring a large, prominent headline.
A social media post for Developer Sandbox for Red Hat OpenShift uses Red Hat Mono font.
A photo shows a large display of the Red Hat brand personality traits on a window at Red Hat Tower.
A graphic shows the hat used as a mask containing code from the Linux kernel typed in Red Hat Display font. The shape of the mask is the exact trademarked shape from the Red Hat logo.
A wall at Red Hat Summit features very large text that reads

Other font contributions

At Red Hat, our approach to open source extends beyond software: we hope that if we make something that’s useful to us, it can be useful to others. That’s why we’ve contributed a few other open source fonts over the years. We don’t use these fonts as part of the Red Hat brand, but they’re available online for the world to download and use.

Liberation Sans

In the 2000s, adoption of Linux on the desktop was hampered by practical issues, including trouble with fonts when moving between open and proprietary software tools. To solve this, Red Hat worked with type foundry Ascender Corp. in 2007 to release Liberation Sans as an open source substitute for popular proprietary fonts like Times New Roman, Arial, and Courier New.

Overpass

Overpass was developed by Delve Fonts in 2011 on commission from Red Hat. It’s based on Highway Gothic—the iconic font used since 1945 for roadway signage by the U.S. Federal Highway Administration—but was optimized for screen-based viewing. The font family has been expanded multiple times by various designers since its initial release and now includes 9 weights, true italics, and a monospaced version.

Because We Had To

Created in 2018 by designers at Red Hat for an article series of the same name, the Because We Had To font family includes 6 handwritten styles, each representing the women working in open source technology featured in the articles.

Typography

Typography

How we apply our fonts, also known as typography, can be just as impactful as the design of the fonts themselves. We write the way that real people talk, so we use our fonts in a way that reflects that.

The basics of typography at Red Hat align to our brand personality traits.

Make it open

Highlight the message using white space rather than filling the entire page with text. Use generous margins and consider editing the length of the copy before decreasing margins or font size to fit more.

Our font family is designed with large, open letterforms, so there’s no need to increase the space between letters (tracking).

Make it authentic

Our words should be real and friendly, so we always type in sentence case rather than title case or all caps (yes, even for headlines).

We follow a straightforward approach to typography, letting the words speak for themselves with minimal formatting or ornamentation. Lean into how text naturally occurs on screens, because that’s where our audience spends their time.

Make it helpful

We’re consistent with how we apply our fonts across applications so that our audience knows what to expect when they hear from us.

Being helpful also means making our words accessible to everyone. Make text readable—with comfortable line spacing (leading) and line length—and legible—with appropriate contrast against the background.

Make it brave

Our font has a lot of personality and we like to show it off. We use prominent headlines that grab attention. Make it big, make it bold, or make it both.

Respect the reader’s time and be confident in what we’re saying. Make the copy concise and compelling, then use type hierarchy to guide the reader through the story.

Do these things

Check mark

Use our fonts: Red Hat Display, Text, and Mono.

Check mark

Use generous margins and a lot of white space.

Check mark

Use sentence case (yes, even for headlines).

Check mark

Make sure text is readable and legible.

Check mark

Let the words speak for themselves.

Check mark

Grab attention by making headlines big, bold, or both.

Avoid these things

X mark

Don't use random fonts.

X mark

Don't fill an entire space with text, it's overwhelming.

X mark

Never use all caps, it's too aggressive.

X mark

Avoid text that lacks appropriate contrast.

X mark

Avoid unnecessary ornamentation.

X mark

Don't increase or decrease text tracking.

Typography specifics

Dive deeper into the specific ways that we apply typography at Red Hat.

Alignment

Alignment

Alignment, sometimes referred to as justification, is the way multiple lines of text are aligned to each other and the elements around them.

At Red Hat, we use flush left text most of the time, and centered text in places where the text needs to be aligned with other centered elements in a narrow space, like presentations or web cards.

A paragraph of text aligned flush left.

Most text should be flush left.

A paragraph of text aligned to the center.

Use centered text when necessary, like short headers or captions on a slide or web card.

A paragraph of text aligned to the right.

Only use flush right text when the context demands it, like a narrow sidebar in collateral.

Image showing misuse: A paragraph of justified text.

Never justify bodies of text. It leaves awkward gaps and looks outdated.

Case

Case

Case is the capitalization of letters in text. We want our messaging to be approachable and authentic, so we designed our font to look best in sentence case. Avoid all caps text.

For guidance on capitalizing specific words, reference the corporate style guide (Red Hat credentials required).

Example text in sentence case.

Use sentence case, even for titles and headlines.

Example text in title case.

Avoid using title case unless you’re referring to a proper noun, like a book title or product name.

Image showing misuse: Example text in all caps.

Never use all caps text, even for small labels.

Color

Color

When applying color to text, legibility is the priority. For that reason, most body copy should be black or white. We often use Red Hat red to draw attention to large headlines or pull quotes, but long paragraphs should never be red.

Image showing red headline and black body copy.

To draw attention, we often use red for large text like headlines. Use black or white for the rest of the text.

Image showing red headline and red body copy.

In most cases, avoid using a color other than black or white for body copy.

Color contrast is measured as a ratio that describes the difference in perceived brightness between the foreground and background color. Low contrast can make text hard or impossible to read.

Text contrast is important and must be considered in all applications—even internal presentations or pages on The Source. We aim to meet WCAG 2.1 AA contrast ratio standards meaning that—with a few exceptions—text and images of text should have a 4.5:1 contrast ratio against the background.

Image showing adequate color contrast.

Check the contrast of your text with a tool like Adobe Color to make sure that it’s meeting accessibility requirements.

Image showing misuse: Image showing inadequate color contrast.

Don’t use text that fails to meet color contrast requirements.

Emphasis

Emphasis

Emphasis helps important words and phrases stand out, but too much emphasis can be distracting. Emphasize text by making it bold or changing the color, but only use 1 treatment at a time.

Do not create emphasis using italics, underline, or all caps.

Image showing proper use of emphasis with bold text.

Use 1 treatment to create emphasis. Choose the most important word or phrase to emphasize.

Image showing improper use of emphasis with multiple bold text.

Avoid overusing emphasis. If everything stands out, nothing does.

Image showing misuse: Image showing improper use of emphasis with different color text, bold text and underlined text..

Don’t use more than 1 type of emphasis at once. It creates confusion and makes it difficult for the audience to decide what’s most important.

We emphasize hyperlinks so they clearly stand out from the rest of the text. In most cases, hyperlinks should be blue (blue-50 on light backgrounds and blue-40 on dark backgrounds) and have an underline. For web and product design, refer to the link guidance in the Red Hat digital design system (web) or PatternFly (product).

Image showing hyperlink that is underlined and blue.
Hierarchy

Hierarchy

Good hierarchy is key to telling a story, and there are many ways to create it—spacing, color, text size, and text weight. We use hierarchy to guide the reader through the text in the order that we want them to read it.

Make headlines big, bold, or both, to capture attention. We also often make headlines red to make them unmistakably Red Hat.

A diagram shows good hierarchy, with a large headline, slightly smaller subhead, and small body copy.
Line height

Line height

Line height—also known as leading—is the vertical space between lines of text in the same paragraph. Line heights that are too tight or too loose can make the text difficult to read. Typography at Red Hat should feel open, but we don’t want to impact legibility by overly increasing line heights.

The line height you should use depends on the application, but the Red Hat font family looks best with line height between 110% (1.1x) and 150% (1.5x) of the font size. PatternFlythe Red Hat digital design system, and our templates recommend specific line heights for their applications.

Image showing text with comfortable line height.

For most text, set the line height to between 120% and 150% (or 1.2x to 1.5x the font size). Prioritize legibility.

Image showing line height details for large text.

For large text over 150, decrease the line height to 110% or 1.1x the font size.

Image showing misuse: Image showing excessive line height.

Never increase the line height to more than 150% or 1.5x times the font size.

Image showing misuse: Image showing too little line height.

Never use line height less than 110% or 1.1x the font size. It looks awkward.

Line length

Line length

Line length is measured by the number of characters in a single line of text, including spaces. Lines that are too long can be difficult to follow. At the same time, lines shouldn’t be so short that only a few words fit per line.

Use line lengths between 20 and 100 characters, including spaces. It’s okay—and preferable—to have white space beside the text rather than filling the entire area. This increases readability and makes our layouts feel more open.

Image showing various line lengths.

Use line lengths between 20 and 100 characters, including spaces. It’s okay—and preferable—to have white space beside the text rather than filling the entire area. This increases readability and makes our layouts feel more open.

Appropriate line length for headlines depends on the size of the text. In general, they should be short and broken into multiple lines rather than running across the entire box or page. If a headline needs more than 3 lines, it’s too long.

Image showing a headline broken into two lines.

Break headlines into multiple lines when necessary.

Image showing a headline broken into two lines with a widow.

Whenever possible, avoid breaking a single word in a headline onto its own line and creating a widow.

Image showing headline on one line spanning the entire width.

Whenever possible, avoid headlines that run the entire length of the text box or width of the page.

Image showing misuse: Image showing a headline broken into multiple lines.

Avoid headlines that are too short. Ideally, headlines should be around 3/4ths of the length of the text below (depending on font size).

Margins

Margins

The margin is the space between text and the edge of the container or nearby objects. We use generous margins for open, approachable layouts. Don’t crowd or fill an entire space with text—find a more concise way to get your point across instead.

The exact size of the margin depends on the design system and size of the layout. Refer to the appropriate template or design system guidelines for specifics.

Image showing text with large margins.

Use a large margin with lots of white space (even if it's not the color white) for maximum impact.

Image showing misuse: Image showing too much text with small margins.

Never decrease or remove margins to fit more text—it looks awkward and can be hard to read. Be more concise instead.

Pull/block quotes

Pull/block quotes

We use several different quote styles. Which style you choose depends on the context and layout, but in general, make sure that a quote looks like a quote.

Image showing a pull quote in a slide deck.

In marketing materials 

In places like social media posts or presentation slides, we stylize quotes using the talk bubble icon. Use a hanging indent for the opening quotation mark.

Image showing a block quote on the web.

On the web

Web applications use the blockquote style built into the digital design system, which combines the quote icon and large text. The style is determined by the website code.

There are other ways that quotes can be stylized, plus some things we should avoid. Learn more.

Punctuation

Punctuation

Quotation marks, apostrophes, and primes look similar but mean different things. The Red Hat font family uses slanted marks for quotation marks and apostrophes. Straight vertical marks should be used only to designate feet and inches, and not used interchangeably with quotation marks and apostrophes.

Image showing quotation marks.

Quotation marks

Image showing an apostrophe in use.

Apostrophe

Image showing primes in use.

Primes (foot and inch marks)

Hyphens, en dashes, and em dashes also look similar. Hyphens are short dashes that join words together, like “log-in.” En dashes are slightly wider and separate numbers, like “2023–2024.” Em dashes—the widest dashes—are used to indicate a pause or break in a sentence. At Red Hat, we don’t place spaces before or after dashes.

Image showing a hyphen in use.

Hyphen

Image showing an en dash in use.

En dash

Image showing an em dash in use.

Em dash

Always use the word “and” when there’s space. When space is constrained—in places like UI labels or headlines—replace “and” with an ampersand rather than a plus sign.

Image showing when to use an ampersand.

Replace “and” with an ampersand when space is constrained.

Image showing misuse: Image showing use of a plus sign.

Don’t replace “and” with a plus sign or any other symbol.

For more details on punctuation at Red Hat, review the corporate style guide.

Rag, widows, and orphans

Rags, widows, and orphans

The rag is the alignment (or lack of alignment) of words along the edge of a body of text. When random lines in a paragraph stick out much farther than others, it can make the text difficult to follow. The rag will never be perfectly straight but we avoid big gaps by adjusting the width of the text box or manually moving words to the next line when needed.

Image showing ideal text rag.

Adjust the width of the text box (when possible) or manually move words to create a rag that's neat, without random lines that stick out.

Image showing misuse: Image showing text with untidy rag.

Avoid rags where random lines stick out much farther than other lines. This is difficult (and annoying) to read.

Widows are single words that appear on their own line at the end of a body of text. Avoid widows by adjusting the width of the text box or by editing the copy.

Image showing a paragraph with no widows.

Make sure that the last line of every paragraph has at least 2 words. Manually adjust the position of words if needed.

Image showing misuse: Image showing paragraph with a widow.

Don’t leave a widow in a paragraph.

Orphans are single lines of text that are separated from the rest of their paragraph. They’re most common when text is split across multiple columns or pages in a document, making it easy to miss the last line of text. Avoid orphans by moving another line to the next column or page.

Image showing a paragraph with no orphans.

When paragraphs split across columns or pages, make sure at least 2 lines appear after the split.

Image showing misuse: Image showing a paragraph with an orphan.

Don’t leave an orphan at the top of a column or page. The reader might miss it.

Tracking

Tracking

Tracking, also known as letter or character spacing, is the horizontal space between all of the letters in a line of text. Tracking that’s too tight or too loose can impact legibility.

While we want typography at Red Hat to feel open, we don’t want to change the tracking in text for no reason. Our fonts have wide letterforms with open details, so the auto tracking is set to an optimal visual density for legibility.

Image showing proper use of auto tracking.

Use the auto tracking built into the Red Hat fonts.

Image showing misuse: Image showing tracked out text.

Never increase the tracking. Our typeface has appropriate tracking built in.

Image showing misuse: Image showing narrow tracking.

Don’t decrease it either.

In rare cases where text is used at less than 6px—like a boilerplate or in a dashboard—we can increase the tracking to 10 or 20 to maximize legibility.

Variable fonts

Variable fonts

The variable version of our fonts include weight as a variable option, and are best used on web properties to decrease load times. If your desktop app doesn’t support variable fonts, use the traditional version instead.

Variable weight are sometimes adjusted via number instead of name. When using variable fonts, stick to the named weights (regular, bold, etc.) for consistency across applications. Don't use weights that aren't part of this set:

An image showing Red Hat Display, Red Hat Text and Red Hat Mono variable fonts.
Download fonts

Download fonts

Red Hat font family

Red Hatters can find our font family pre-installed on their Red Hat-issued laptop. The fonts are also already available in the apps we use every day including Google Workspace apps and templates, Miro, and creative software like Figma and Adobe Creative Cloud.

Red Hat fonts are also publicly available online:

Noto Sans font family

We use Noto Sans for languages that use non-Latin character sets. You’ll need to download the specific family of Noto Sans for your language or project: