Google Fonts for Commercial Use: Licensing, Self-Hosting, and Privacy

Google Fonts for Commercial Use: Licensing, Self-Hosting, and Privacy

Google Fonts looks like one free library. In legal terms it is a delivery service in front of hundreds of separate families, and each family carries its own license file. That fact explains why a modified version sometimes needs a new name, why redistribution duties differ between two families in the same layout, and why loading from Google servers or hosting the file yourself is a privacy and performance choice, not a license shortcut.

This guide is general information, not legal advice.

The Short Answer

Google states the headline in its Google Fonts FAQ: all Google Fonts are open source, there is no cost for any of them, and you can use them commercially, including in a product sold commercially, in a logo, and on any surface the FAQ lists, from print and websites to apps, teaching materials, e-books, store fronts, and jewelry. The FAQ adds the condition that does the real work: usage and redistribution conditions are specified in the license for that font.

• Use is broad. Commercial use, logos, print, web, and app use are allowed for families in the catalog.
• Redistribution has duties. They depend on the family license: most often the SIL Open Font License 1.1, sometimes Apache License 2.0, and for Ubuntu families the Ubuntu Font License 1.0.

Why the License Lives Per Family, Not Per Platform

Google is not the author of most families in the catalog, and the platform imposes no single license over all of them. The official repository, github.com/google/fonts, shows the structure: its top-level folders are named for licenses - ofl, apache, and ufl among them - and the repository states that the top-level directories indicate the license of all files within them.

So a screenshot of the Google Fonts homepage is not a license record. The record is the license file in the folder you downloaded. Two families in one project can carry different duties, and the same family name from a random archive is a separate question, because that copy does not inherit the Google Fonts record.

The SIL Open Font License 1.1, in Plain Terms

Most families use the SIL Open Font License, version 1.1 (26 February 2007), published at openfontlicense.org. Its preamble states that fonts may be used, studied, modified, and redistributed freely as long as they are not sold by themselves, and can be bundled, embedded, redistributed, and sold with any software, provided reserved names are not used by derivative works. Five conditions apply.

1. Do not sell the font by itself. The font software, or any component, in original or modified form, may not be sold by itself. Selling a site, app, book, or template that contains the font is normal commercial use.

2. Carry the notice and license when the font travels. Each redistributed copy must contain the copyright notice and the license, as a text file, readable header, or viewable metadata. Keep OFL.txt beside the font files in every handoff and build.

3. Respect Reserved Font Names. A modified version may not use a Reserved Font Name without written permission from the copyright holder. See below.

4. Do not use author names to promote a modified version. Holder and author names may not be used to promote a modified version, except to acknowledge their contribution or with written permission.

5. Modified fonts stay under the OFL. The font software must be distributed entirely under this license. The same condition states this does not apply to any document created using the font software: your poster, PDF, logo file, and web page do not become OFL material because the typeface inside them is OFL.

The OFL site sums up the result: OFL fonts can be used in books, posters, artwork, logos, and on websites, with no acknowledgement required for work you create.

Apache License 2.0 Families: What Changes

A smaller set of families, including older and widely used ones, uses Apache License 2.0, published at apache.org. It is a general software license, not a font-specific one.

Section 2 grants a perpetual, worldwide, royalty-free copyright license to reproduce the work, prepare derivative works, display and perform it, sublicense it, and distribute it in source or object form. Section 3 adds a patent license on stated terms. Section 6 states that the license does not grant permission to use licensor trade names, trademarks, service marks, or product names, except for reasonable and customary use describing the origin of the work and reproducing a NOTICE file.

Redistribution under section 4 has four duties: give recipients a copy of the license; mark modified files with prominent change notices; retain the copyright, patent, trademark, and attribution notices from the source form in derivative works, apart from notices that do not pertain; and, if the work includes a NOTICE file, include a readable copy of its attribution notices in a NOTICE file, the source or documentation, or a display where third-party notices normally appear.

Contrasts with the OFL: Apache has no Reserved Font Name rule and no standalone-sale bar in OFL form. A third bucket exists: Ubuntu families under the Ubuntu Font License 1.0, also named in the FAQ. Read that file rather than applying these summaries by analogy.

Reserved Font Names

The OFL lets a copyright holder declare Reserved Font Names after the copyright statement. The google/fonts repository calls this an OFL option used with some fonts, and warns anyone modifying those fonts to take care of it.

Using the font as supplied raises no naming issue. Distributing a modified version - a redrawn weight, added character set, or converted build passed on as a font - may not keep a Reserved Font Name as its primary font name without written permission. The normal fix is a new name, with the OFL and notices kept. Find the declaration at the top of OFL.txt, in the copyright lines, in the form with Reserved Font Name followed by the name.

Commercial Use, Case by Case

Logos. The FAQ answers yes directly: you can use the fonts within any logo. Two limits apply, and neither is a fee. A logo set in a Google Font is not exclusive, since every business holds the same right to the same letters, and a font license does not clear a name or mark for trademark registration.

Print, packaging, and products for sale. The FAQ lists print and store fronts among covered surfaces, and the OFL allows work created with the font to be sold.

Websites, apps, and e-books. Allowed on either delivery route below, and embedding is named in the OFL permission list. For apps, bundle the license file in the build resources or a licenses screen.

Client handoffs. You may hand font files to the client as part of the project, license file included, because redistribution with the license is part of the grant. Add one line per family to the handoff note: family name, license name, and where the license file sits.

Templates containing the font. The OFL allows a font to be bundled and sold with software and products, provided it is not sold by itself and the license travels with it. A pack of raw font files for resale is the standalone sale the OFL bars.

Decision Table: Three Ways to Deliver a Google Font

All three routes deliver licensed files. They differ in control, visitor data, performance work, and updates.

Privacy: What Loading From Google Servers Sends

The privacy question is about delivery, not the font files. Google explains the mechanics on its Privacy and Data Collection page. When a site embeds Google Fonts through the Web API, the visitor browser requests the CSS and then the font files named in it. Those requests include the IP address used by the visitor to access the internet, the requested URL on the Google server, and HTTP headers including the user agent describing browser and operating system versions, plus the referer, meaning the webpage where the font is to be displayed. Google states it receives the IP address to respond to the request and for security,.

Google also states limits on its side. The API is designed to limit collection, storage, and use of end-user data. Use of the Web API is unauthenticated, the API does not set or log cookies, requests go to resource-specific domains such as fonts.googleapis.com or fonts.gstatic.com, and font requests contain no credentials sent to google.com for authenticated services such as Gmail.

Why owners act anyway, in general terms: in privacy regimes such as the GDPR, an IP address can be treated as personal data, so a routine third-party request raises questions about legal basis, notice disclosure, and data transfer that a first-party file does not raise. This guide reports no individual court decisions. Google states that when a font is loaded from the website operator own servers, Google does not receive any data related to visits to that website. Self-hosting closes this one flow; it does not by itself make a whole site compliant.

Self-Hosting, Step by Step

Google lists drawbacks on its privacy page: a full file can be larger than the pieces the API delivers, a self-hosted file is not tailored to each browser, and updates become manual. Subsetting, WOFF2, and a dated check answer those points.

Step 1: Record the license first. Note the license named on the family page and save the license file before any font file. The Space Grotesk font page shows the pattern: its repository folder sits under the ofl directory, with an OFL.txt inside.

Step 2: Download from an official source. Use the family page download, the family folder in github.com/google/fonts, or the CSS API response for the exact styles you need, saving the WOFF2 files its CSS names.

Step 3: Decide variable or static. If the design uses a weight range, keep the variable file. Our variable fonts guide covers axes and CSS ranges, If the design uses two fixed weights, static files for those weights usually total less.

Step 4: Subset to served ranges. Subsetting removes glyphs your pages never render. Keep latin, latin-ext, and each added script as separate files with separate @font-face rules and matching unicode-range values, so browsers fetch only the ranges page text requires. Record the ranges shipped.

Step 5: Serve WOFF2, keep masters separate. Keep the original TTF or OTF download untouched in a source folder with the license file.

Step 6: Write @font-face with font-display. Google Fonts Knowledge, in Using web fonts, gives the order: reference each file with an @font-face declaration carrying family, style, and weight, and add font-display to control rendering while the font loads. A self-hosted rule sets font-family to your family name, src to the WOFF2 URL with format woff2, font-weight to one value or a range such as 400 700, font-style to normal or italic, font-display to swap, and unicode-range to the subset range.

Step 7: Apply preload discipline. Preload at most one or two files: the file rendering the largest visible text on the first screen, usually one weight of the primary family in the latin subset. Its line uses as font, type font/woff2, and crossorigin, which font preloads require even on the same origin.

Step 8: Cache, update, verify. Serve fonts with a long cache lifetime, and immutable caching if file names carry a version or hash. Set a dated update check, quarterly as a default, against the official repository. Verify in a browser network panel: font responses come from your own domain, no request goes to fonts.googleapis.com or fonts.gstatic.com, and rendered weights match declared weights.

The License-Per-Family Check Routine

Run this for every family in a project, including families cleared before, because a new download is a new record.

1. Name the family and its source. Write down the family name as on fonts.google.com and where you will take files from, including the repository license folder, such as ofl or apache.
2. Open the license file in that folder. Read the license name and version in the file itself. If the folder has no license file, stop and take the family from a source that includes one.
3. Scan an OFL header for Reserved Font Names. Copy any declared name into your record. That line decides your renaming duty if you distribute a modified version.
4. Note the redistribution duties. For OFL: license and notice travel, no standalone sale, modified versions stay under the OFL. For Apache: license copy travels, modified files carry change notices, source notices are retained, NOTICE content is included where provided.
5. File the record. Save the license file, family page address, download date, and notes in one folder per family, named for the family.
6. Repeat at handoff. Confirm the delivery folder still contains each license file. The common failure is a clean-up pass that deletes text files.

Traps That Cause Rework

Assuming the CDN link settles the license. Duties at handoff, app bundling, or template sale come from the family license; the CDN link plays no part in those acts. File the license anyway.

Sharing a subset as the family. A distributed subset is a modified version: under the OFL it stays under the OFL with its notices, and a declared Reserved Font Name may not be its primary name without permission. Pass subsets on with the license and a note naming the build as a subset.

Leaving a Google fallback in production CSS. A stack that falls back to the Google API for a missing italic or subset reintroduces the third-party request. Search production CSS for fonts.googleapis.com after migration.

A Worked Example: One Brand Site, Two Families

This hypothetical example shows the checking and delivery order. No real client or brand is involved. A designer builds a site for a small consultancy: Fraunces for headings, Space Grotesk for text, both first loaded from the Google CDN.

1. License check. Both repository folders sit under ofl, each with an OFL.txt. The designer files both and records what each header states on Reserved Font Names.
2. Delivery decision. The consultancy has European Union clients and a privacy notice promising no third-party requests on first load. The team picks self-hosting, at the cost of manual updates.
3. File build. Headings use Fraunces across a weight range, so the variable file is kept, subset to latin and latin-ext. Text uses Space Grotesk in two weights, so static subsets are built.
4. Handoff. The delivery folder holds the font files, both OFL.txt files, and a record naming each family, license, subsets, and the next update check date.

FAQ

Can I use Google Fonts in a logo for a paying client?

Yes. The FAQ states you can use the fonts within any logo, and the OFL permits use in artwork and logos. File the family license in the brand folder.

Can I send Google Font files to my client at the end of a project?

Yes, with the license file included. OFL condition 2 allows redistribution with the copyright notice and license in each copy, and Apache families redistribute on Apache duties. Send the family folder as downloaded, plus your font record.

Can I use Google Fonts in an app or a product I sell?

Yes. The FAQ allows use in a commercial product and inclusion within a product sold commercially, with conditions set by the family license. Keep license and notices in the build resources or a licenses screen, and do not sell the font files by themselves.

Does self-hosting change what the license allows?

No. Self-hosting changes delivery: who serves the files, what visitor data a font request sends, how files are cached, and who applies updates. The family license still governs use and redistribution.

What is a Reserved Font Name and why does it matter to me?

It is a name the copyright holder declares in the OFL.txt header and protects for modified versions. Use the font as supplied and it does not affect you. Distribute a modified version and you may not use that name as the primary name without written permission, so the build takes a new name.

Does loading Google Fonts from Google servers set cookies or build visitor profiles?

According to the Google Fonts privacy page, no on both points as Google states them. The API does not set or log cookies, requests carry no credentials from authenticated Google services, and Google states it does not use information collected by Google Fonts to create profiles of end users or for targeted advertising. The same page confirms requests include visitor IP address, requested URL, and browser headers, which is the flow self-hosting removes.

Sources Read for This Guide

• Google Fonts FAQ, Google for Developers: https://developers.google.com/fonts/faq
• Privacy and Data Collection, Google Fonts, Google for Developers: https://developers.google.com/fonts/faq/privacy
• Google Fonts Knowledge, including Using web fonts: https://fonts.google.com/knowledge and https://fonts.google.com/knowledge/using_type/using_web_fonts
• SIL Open Font License, official text version 1.1 and site summaries: https://openfontlicense.org/ and https://openfontlicense.org/open-font-license-official-text/
• Apache License, Version 2.0, Apache Software Foundation: https://www.apache.org/licenses/LICENSE-2.0
• google/fonts repository, including the license folder structure and the Space Grotesk family folder with its OFL.txt: https://github.com/google/fonts and https://github.com/google/fonts/tree/main/ofl/spacegrotesk

What to Read Next

• Commercial font licensing guide - desktop, web, app, and embedding licenses across foundries.
• Free fonts for logos guide - testing and clearing a typeface that will carry a brand mark.
• Variable fonts guide - axes, CSS ranges, and file-size trade-offs for variable families.
• Complete guide to choosing fonts for web design - selection, pairing, and language support before license checks.
• Fraunces variable serif - a variable serif profile, with the axes a heading system can use.
• Space Grotesk font - a text and interface family profile, from the OFL folder pattern in this guide.

This guide is maintained by the Lucky Graphics editorial team and reviewed when the sources above change their terms or delivery guidance.