Google Fonts

Fonts Visit fonts.google.com

Free library of 1,500+ open-source font families served via Google's global CDN. Used by 42M+ websites worldwide.

91396 detections

20 websites tracked

Updated 15 Jun 2026

Websites Using Google Fonts

What Is Google Fonts?

Google Fonts is a free, hosted web-font service that lets any website embed high-quality typefaces with a single line of code. It is the most widely used web-font service on the internet: Google's own catalog ships well over 1,500 font families, and the service is referenced by tens of millions of websites worldwide. When a site uses Google Fonts, the typeface files are typically downloaded from Google's servers (fonts.gstatic.com) and the styling instructions come from Google's CSS API (fonts.googleapis.com).

The practical appeal is simple. Instead of buying a font license, exporting font files, and hand-writing @font-face rules, a developer copies an embed snippet from the Google Fonts website and pastes it into the page <head>. The fonts are open-source and free for commercial use, which removed the historic friction around web typography and is a large part of why adoption became so broad.

A real, verifiable note worth keeping in mind: loading fonts directly from Google's servers transmits the visitor's IP address to Google, and a 2022 ruling by a German regional court (Landgericht Munchen I) found that embedding Google Fonts this way without consent can violate the EU's GDPR. The widely reported takeaway from that case is that self-hosting the same fonts avoids the third-party request entirely. We will return to the privacy angle below, but the source-of-truth point is: the legal exposure comes from the remote request, not from the typeface designs themselves.

It is worth being precise about scope. Google Fonts is a delivery service, not a font foundry in the traditional sense - many of the typefaces in the catalog are commissioned or contributed by independent designers and foundries and then released under open licenses. That distinction matters when you are profiling a website: detecting "Google Fonts" tells you how the type is being served (remote CSS API plus CDN, or a self-hosted copy), while the font-family names tell you which typefaces are in use. A site can use a Google-catalog typeface like Inter or Roboto without ever touching Google's servers, simply by self-hosting the files. For accurate technology profiling you want to separate the two questions, and the sections below are organized around exactly that split.

How Google Fonts Works

Google Fonts has two moving parts: a CSS API and a font-file CDN.

The CSS API. A request to https://fonts.googleapis.com/css2?family=Roboto&display=swap returns a small stylesheet. That stylesheet contains @font-face blocks that point at the actual font files. Google tailors this response to the requesting browser, serving modern formats (like WOFF2) to modern browsers and falling back to older formats for legacy ones. The css2 endpoint is the current generation; older sites may still use the original css endpoint.
The font CDN. The @font-face blocks reference .woff2 (or other) files hosted on fonts.gstatic.com. The browser downloads only the styles and character ranges the page needs.

Two optimizations matter for performance:

Unicode-range subsetting. Google splits large fonts into character subsets (Latin, Latin-extended, Cyrillic, Greek, and so on) using the CSS unicode-range descriptor. A page that only renders Latin text downloads only the Latin slice.
font-display. The embed snippet usually includes display=swap, which maps to the CSS font-display: swap descriptor. This tells the browser to show fallback text immediately and swap in the web font once it loads, preventing the "invisible text" problem (FOIT) during font download.

Google Fonts increasingly ships variable fonts, which pack many weights and styles into one file. A single variable-font request can replace four or five static-weight requests, reducing both round-trips and total bytes.

Because so many sites pull from the same fonts.gstatic.com origin, fonts are aggressively cached by the browser. (Note that modern browsers partition their HTTP cache per-site for privacy, so the old "already cached from another site" benefit is weaker than it used to be.)

To make the request flow concrete, here is what happens when a first-time visitor loads a page that embeds Google Fonts remotely:

The browser parses the HTML and finds the <link> to fonts.googleapis.com.
It opens a connection to fonts.googleapis.com (DNS lookup, TLS handshake) and downloads the small CSS file.
It parses the returned @font-face rules and discovers references to fonts.gstatic.com.
It opens a second connection, this time to fonts.gstatic.com, and downloads only the font files and character subsets the page actually needs.
With font-display: swap, the browser renders text in a fallback font immediately, then repaints with the web font once the file arrives.

The preconnect hints in the standard embed snippet exist precisely to overlap steps 2 and 4 - they warm up the connection to gstatic.com before the CSS has even been parsed, shaving latency off the critical path. Understanding this two-origin, two-hop pattern is also what makes Google Fonts so straightforward to detect: both origins show up as distinct network requests no matter how the markup was generated.

How to Tell if a Website Uses Google Fonts

Google Fonts leaves obvious, reliable fingerprints. Here are the signals and the tools to find them.

Signal 1 - Link tags to Google domains. The clearest tell is one or more <link> elements pointing at Google:

<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;700&display=swap" rel="stylesheet">

Signal 2 - @import in CSS. Some sites import the stylesheet from within CSS instead of HTML:

@import url('https://fonts.googleapis.com/css2?family=Lora&display=swap');

Signal 3 - Network requests. Even when the markup is generated by JavaScript, the browser still has to fetch from fonts.googleapis.com and fonts.gstatic.com. Those requests are visible at runtime.

Signal 4 - font-family names. Recognizable Google Fonts names (Roboto, Open Sans, Lato, Montserrat, Poppins, Inter, Nunito) appearing in the computed CSS are a soft signal. They are not proof on their own, because a site could self-host those same open-source families.

How to check, tool by tool:

View Source (right-click - View Page Source, or Ctrl/Cmd+U): search the HTML for fonts.googleapis.com or fonts.gstatic.com. Fast, but only catches fonts referenced in the initial HTML.
DevTools - Network tab: filter by Font or type gstatic in the filter box, then reload. You will see the actual .woff2 downloads and their origin. This catches dynamically injected fonts that View Source misses.
DevTools - Elements / Computed: select a text element and read the Computed font-family. The Rendered Fonts subsection (in Chrome) shows exactly which font glyphs were drawn.
Wappalyzer (or similar tech-profilers): flags Google Fonts automatically by matching these request patterns, so you do not have to inspect by hand.

For URL-level, server-side detection without a browser, StackOptic fetches the page and inspects the HTML and linked stylesheets for these fonts.googleapis.com / fonts.gstatic.com signatures. For a manual walkthrough, see our guides on how to find what fonts and colors a website uses and how to find out what technology a website uses.

Key Features

Free, open-source catalog. Over 1,500 families, all licensed for commercial use at no cost.
One-line embed. Copy-paste <link> or @import integration with no licensing workflow.
Global CDN delivery. Files served from edge locations close to the visitor.
Automatic format negotiation. Modern browsers get WOFF2; older browsers get compatible fallbacks.
Unicode-range subsetting. Only the needed character ranges download.
Variable font support. Many weights and styles in one file.
font-display control. Configurable loading behavior to avoid invisible or shifting text.
Self-hosting path. The same fonts can be downloaded and hosted on your own origin when you need to.

Pros and Cons

Pros

Zero cost and a huge, well-curated selection.
Trivial to integrate, even for non-developers.
Strong default performance: subsetting, WOFF2, and a fast CDN out of the box.
Open-source licenses remove legal ambiguity about using the typefaces.

Cons

Third-party dependency. Your typography relies on Google's uptime and DNS resolution for fonts.googleapis.com.
Privacy and GDPR exposure. Remote loading sends visitor IPs to Google; this has been ruled non-compliant in at least one German case absent consent.
Extra connections. Each new origin (googleapis, gstatic) adds DNS, TLS, and connection overhead unless you preconnect or self-host.
Cache partitioning. The cross-site caching benefit is largely gone in modern privacy-partitioned browsers, so the "everyone already has it cached" argument no longer holds.

Google Fonts vs Alternatives

The main alternatives are Adobe Fonts (a subscription service bundled with Creative Cloud), self-hosting fonts on your own server, and the native system font stack.

Option	Cost	Hosting	Selection	Privacy (default)	Best for
Google Fonts	Free	Google CDN (or self-host)	1,500+ open families	Sends IP to Google when remote	Most websites, fast setup
Adobe Fonts	Creative Cloud sub	Adobe CDN	20,000+ foundry fonts	Sends IP to Adobe	Brand/design teams on CC
Self-hosted fonts	Varies by license	Your own server	Whatever you license	Fully first-party	GDPR-strict, full control
System font stack	Free	None (local)	OS-installed fonts	No external request	Maximum performance

For a deeper comparison of the subscription model, see Adobe Fonts. The pragmatic middle ground that many privacy-conscious teams choose is to take a Google Font and self-host it, keeping the design while removing the third-party request.

Use Cases

Marketing sites and blogs that want professional typography without a licensing budget.
Prototypes and MVPs where speed of setup beats fine-grained control.
CMS-driven sites (WordPress, Webflow, Shopify) where Google Fonts is the built-in default.
Multilingual sites that benefit from the broad script coverage and subsetting.
Self-hosted production deployments that start from a Google Font and bring it in-house for performance and GDPR reasons.

If you care about loading behavior and Core Web Vitals, pair Google Fonts with the techniques in how to optimize web fonts for performance - preconnecting to gstatic, using font-display: swap, and preloading critical fonts.

A practical detection workflow

When you are profiling an unfamiliar website specifically to understand its typography, a repeatable order of operations saves time:

Start with the network, not the markup. Open DevTools, go to the Network tab, filter to Font, and reload. This immediately shows every font file the page fetched and the origin it came from. If you see fonts.gstatic.com, the site is using Google's CDN. If you see fonts coming from the site's own domain with Google-catalog names, it is self-hosting a Google typeface.
Confirm the CSS source. Filter the Network tab to CSS (or search googleapis) to see whether the stylesheet came from fonts.googleapis.com or from the site itself.
Read the rendered fonts. In the Elements panel, select a headline and a paragraph, then read the Computed font-family and the Rendered Fonts list. This tells you which families are actually drawn versus merely declared as fallbacks.
Cross-check with a profiler. Run Wappalyzer or a server-side scan to confirm the automated verdict matches what you saw by hand.

This workflow distinguishes the three real-world scenarios that a naive "is it Google Fonts?" question conflates: remote Google Fonts, self-hosted Google-catalog fonts, and entirely unrelated fonts that merely share a popular name.

Frequently Asked Questions

Is Google Fonts free to use commercially?

Yes. The fonts in the Google Fonts catalog are released under open-source licenses (most under the SIL Open Font License) that permit commercial use, embedding, and self-hosting at no cost. There are no per-pageview fees and no usage caps.

Does using Google Fonts violate GDPR?

It can, when fonts are loaded directly from Google's servers without consent, because that transfers the visitor's IP address to Google. A 2022 German court ruling found this non-compliant in a specific case. The widely recommended fix is to self-host the fonts so no request ever reaches Google. Always confirm specifics with your own legal counsel.

How do I know which Google Font a site is using?

Open DevTools, select a text element, and read the Computed font-family and Rendered Fonts. Then check the Network tab (filtered to fonts or gstatic) to confirm the file is actually coming from fonts.gstatic.com. Wappalyzer and StackOptic can detect it automatically from the page's requests.

Is self-hosting Google Fonts faster than the CDN?

Often, yes, on modern browsers. Because browser HTTP caches are now partitioned per site, the old cross-site caching advantage of the CDN is largely gone. Self-hosting removes an extra DNS lookup and TLS handshake to a third-party origin, and lets you preload and cache fonts under your own control.

What is the difference between the css and css2 endpoints?

css2 is the current Google Fonts API, with cleaner syntax for requesting multiple weights, italic styles, and variable-font axis ranges. The original css endpoint still works for older embed codes. Both return @font-face stylesheets that point at fonts.gstatic.com.

Want to know exactly which font services any URL relies on - including Google Fonts, self-hosted files, and third-party CDNs? Analyze any website with StackOptic.

Alternatives to Google Fonts

Font Awesome91471 sites Adobe Fonts13427 sites Material Icons10643 sites Adobe Fonts8168 sites Ionicons1614 sites Feather Icons198 sites Glyphicons Fork Awesome Cufon i30con

Compare Google Fonts

Google Fonts vs Font Awesome→Google Fonts vs Adobe Fonts→Google Fonts vs Material Icons→Google Fonts vs Adobe Fonts→Google Fonts vs Ionicons→

Analyze a Website

Check if any website uses Google Fonts and discover its full technology stack.

Analyze Now