Are Google Fonts really free for commercial use?

The short answer, in Google’s own words

If you are about to put a Google Font on a client’s packaging and want to be sure before you do, here is the source. The Google Fonts FAQ says that all Google Fonts are open source and without cost. It says you can use them commercially, and even include them within a product that is sold commercially.

The fonts are not owned by Google in most cases. They are made by independent designers and foundries who chose to publish them under an open source license. Google Fonts is the catalog and the delivery service. According to the FAQ, the most common license is the SIL Open Font License (OFL), some families use the Apache License 2.0, and the Ubuntu family uses the Ubuntu Font License. Google now only accepts new fonts under the OFL.

All three licenses allow commercial use. They differ in the details of modifying and redistributing the font files, which matters to far fewer people. For background on how these compare with paid licenses, see font licensing in plain English.

What you are allowed to do

You do not need to credit the font or its designer on your website, in your logo or in your printed piece. The OFL FAQ is clear that a mention is appreciated and not required. The license covers the font software. It does not reach the documents and designs you make with it.

The few things you cannot do

The restrictions are about the font files themselves, and they only come into play when you redistribute or modify them.

• You cannot sell the font by itself. The OFL allows fonts to be bundled with and sold as part of software or a larger product. Selling the font files on their own, original or modified, is forbidden.
• Respect Reserved Font Names. Many OFL fonts reserve their name. If you change the font file, your version must carry a different name unless the copyright holder gives written permission. This keeps altered copies from passing as the original.
• Keep the license with the files. When you pass the font files on, for example inside an app, a theme or a template pack, the copyright notice and the license text go with them.
• Modified OFL fonts stay under the OFL. You cannot relicense a derivative under different terms.
• Do not use the authors’ names to promote your modified version.

Apache 2.0 works a little differently. It asks you to keep the license and notices when you redistribute and to mark files you changed, and it has no reserved name rule. The Ubuntu Font License has its own renaming rule for modified versions. If you only use fonts and never modify or repackage them, none of this affects you.

One more thing that trips people up: not every font Google uses is a Google Font. The FAQ states that Product Sans, the typeface of the Google logo, is owned by Google and is not available for use by anyone else. Google Sans and Google Sans Flex, on the other hand, were released under the OFL in November 2025.

How to check the license of any family

Do not take a blog’s word for it, including this one. Checking takes under a minute.

1. Open the family’s specimen page on fonts.google.com.
2. Open the page’s license section. It shows the copyright line, names the license and prints the full text. For an OFL font you will see “SIL Open Font License, Version 1.1”.
3. Read the copyright line at the top. If the author reserved a font name, it is stated there, next to the copyright notice.
4. When you download the family, keep the license text file that comes in the download, such as OFL.txt, next to the font files.

While you are there, Google Fonts Knowledge is worth a bookmark. It is Google’s free library of typography lessons, from choosing type to using web fonts and variable fonts. If variable fonts are new to you, start with variable fonts explained.

How to tell whether a font you spotted is a Google Font

You like the type on someone’s site and hope it is free. Here is how to find out by hand.

1. Open DevTools, go to the Network panel, filter by Font and reload the page.
2. Look at the domain of the font files. Files from fonts.gstatic.com are served by Google Fonts. You will usually also see a stylesheet request to fonts.googleapis.com.
3. If the files come from the site’s own domain, the font may still be a Google Font that the team hosts itself. Get the family name from the Rendered Fonts section of the Computed tab, then search for it on fonts.google.com.

The step-by-step version, including Adobe Fonts, is in is it Google Fonts or Adobe Fonts?.

With Font Inspector you click Pick text on page, then the text. The panel names the family and its source: Google Fonts, Adobe Fonts, a self-hosted web font or a system font. When the source is Google Fonts, the Get this font section opens the family there. When the font is a paid typeface, the same section suggests free Google Fonts look-alikes. They are similar, not identical, so compare them with your own text first.

Embedding through Google’s API or self-hosting

There are two ways to put a Google Font on a website. The license allows both.

The Google Fonts API

You paste a <link> tag that points to fonts.googleapis.com, and Google serves the CSS and the font files. Google’s FAQ lists the benefits: the smallest suitable file for each browser, WOFF2 compression, and updates to the fonts without any work from you.

The privacy side deserves a careful look. According to the same FAQ, each request to the API includes the visitor’s IP address, the requested URL and HTTP headers such as the user agent and the referring page. Google says the API sets no cookies, is unauthenticated, and that the data is not used to build profiles or for targeted advertising.

In January 2022 the Regional Court of Munich I ruled against a website operator for passing a visitor’s IP address to Google through embedded Google Fonts without consent, and awarded the visitor 100 euros. It was one regional decision, but it is the reason many European sites now self-host. The background and a full how-to are in Google Fonts and GDPR.

Self-hosting

You download the family, put the WOFF2 files on your own server and write the @font-face rules yourself. Google’s FAQ confirms that when fonts are loaded from your own server, Google receives no data about your visitors. The trade-offs Google names are real but manageable: you choose the subsets yourself, and you update the files yourself.

@font-face {
  font-family: "Inter";
  src: url("/fonts/inter-latin-variable.woff2") format("woff2");
  font-weight: 100 900;
  font-style: normal;
  font-display: swap;
}

body {
  font-family: "Inter", system-ui, sans-serif;
}

• Serve WOFF2. Every current browser supports it.
• Remove the old <link> tags to fonts.googleapis.com and the preconnect hints to fonts.gstatic.com. Otherwise the page still calls Google.
• Keep the license text file on the server next to the font files.
• Pick sensible fallbacks so a slow font does not shift the layout. See CSS font stacks and fallbacks.

Common worries, answered

• “Will Google start charging later?” Your right to use a font comes from its open source license, granted by the font’s copyright holders, not from a Google account or subscription. The license text ships with the files you download.
• “My client wants exclusive rights to the font.” That is not possible with an open source font. Anyone else may use the same typeface. The logo you draw with it can still be protected as a logo.
• “Can I sell T-shirts or templates with it?” Products that show the font, such as shirts, posters and printed goods, are fine. Templates that include the font files count as redistribution, so include the license text and do not sell the font by itself.
• “Can I convert or subset the files?” Yes, but the OFL FAQ treats subsetting and some conversions as modification. For a font with a Reserved Font Name, a modified version you redistribute should be renamed.

Once the license question is settled, the fun part starts. Try your shortlist with real copy in the font pairing playground, and read font pairing basics if you are choosing a heading and body combination.