Google Fonts

Overview

Google Fonts launched in 2010 and is maintained by Google, making it the broadest free font library in the Web Fonts space. Most families ship under the SIL Open Font License or Apache licence, free for commercial use, embeddable, and modifiable, which makes it the default for indie sites and small teams.

It solves delivery as well as availability. The official CDN serves language subsets with format negotiation, so a Chinese family such as Noto Sans SC can be subset to the characters actually used, shrinking a multi-megabyte font to the required glyph set, the step self-hosting most often misses.

As infrastructure it has trade-offs. The CDN is unreliable in some regions and directly drags first paint, and careless loading strategy around preload and font-display causes flashes or invisible text. Treat it as a free font source rather than a free performance strategy.

Core Strengths

• Live since 2010 with 1,500+ open-source families, most free for commercial use and open to embedding and modification
• The CDN serves language and character subsets with automatic format negotiation for woff2, cutting transfer size
• Variable fonts cover multiple weights and widths in one file, reducing requests
• Both self-hosted downloads and CSS references, so a domestic CDN mirror can route around access problems

Product Ecosystem

Library and licensing

Filter by language, weight, width, and style, with licence type and character coverage on each family page. Confirm glyph coverage first, the most common trap for Chinese and multilingual sites.

Integration and performance

Use the official CSS link or self-hosted files. In production, subset with tools like subfont, preload the first-screen font, and set font-display swap so fonts never block rendering into a blank screen.

Drawbacks

• The official CDN is unreliable in some regions, so direct links can slow first paint instead
• Chinese families are heavy, reaching several megabytes without subsetting, which hurts mobile
• Poor integration without font-display or preload causes flashes or delayed text
• Chinese families offer fewer weights and styles than Latin ones, limiting design freedom

Use Cases

• Indie and content sites (★★★★★) - Free commercial use with parametric integration makes it the default
• Chinese site font optimisation (★★★★☆) - Subsetting brings size down but needs engineering effort
• First-paint sensitive projects (★★★☆) - Self-host, subset, and preload, and measure the official CDN
• Projects needing a distinctive brand face (★★) - Free libraries are limited, so custom branding still needs commercial fonts

Pricing

Fonts are free and cost sits in bandwidth and engineering. Real spending on Chinese sites comes from subsetting pipelines and CDN traffic rather than licensing, so list both separately instead of treating the stack as simply free.

FAQ

• Is Google Fonts free for commercial use? Mostly yes, under SIL OFL and Apache 2.0. Licences differ per family, so open the family page before commercial use, especially when embedding in apps or modifying files.

• How do I keep Chinese sites fast? Subset to the characters actually used, then self-host or use a domestic CDN with preload and font-display swap. Referencing the full Chinese family on the official CDN is usually the main first-paint bottleneck.

• Any privacy compliance concerns? The CDN logs requesting IPs, and EU rulings have addressed this. Sites with strict compliance should self-host or use a privacy-friendly mirror such as Bunny Fonts.