Skip to main content
All guides

Free check · Google Fonts · Updated

Does my website load Google Fonts from Google?

If your pages request fonts.googleapis.com or fonts.gstatic.com while they load, yes — and every visitor’s browser sends its IP address to Google before anyone has touched your consent banner. Enter your address below: PrivaScan opens the page in real Chrome without clicking anything and lists Google Fonts, together with every other third party the page contacted.

Scan your page now

Real Chrome, nothing clicked: everything it finds happened before consent.

Free, no sign-up. Results in under a minute.

Why it matters

A font file looks harmless, but the request for it carries the visitor’s IP address to Google, a US company, the moment the page loads. In January 2022 a German regional court (Landgericht München I, 3 O 17493/20) held that passing a visitor’s IP address to Google this way without consent was unlawful and awarded the visitor damages. Fonts are needed to draw the page, so a consent banner is an awkward fix; hosting the same files yourself removes the transfer altogether.

Check it yourself in 30 seconds

No tool needed — your browser shows it:

  1. Open your site in a private window and press F12 (Developer tools) → Network.
  2. Type “fonts.g” in the filter box and reload the page without clicking the banner.
  3. Any row for fonts.googleapis.com (the CSS) or fonts.gstatic.com (the font files) means the page loads Google Fonts from Google.
  4. Repeat on a few page types (home, product, blog): a theme, plugin or page builder can add Google Fonts to some templates and not others.

What the free PrivaScan scan shows

The scan records every request the page makes while it loads, before any click. For Google Fonts you get:

How to fix it

Download the font files (WOFF2 is enough for current browsers), put them on your own domain, declare them with @font-face and remove every <link> or @import that points at fonts.googleapis.com. Many themes and page builders also have a “local fonts” or “disable Google Fonts” setting. Then scan again: the Google Fonts finding should be gone.

/* Self-hosted: no request to Google */
@font-face {
  font-family: 'Inter';
  src: url('/fonts/inter-var.woff2') format('woff2');
  font-display: swap;
}

/* Remove: <link href="https://fonts.googleapis.com/css2?family=Inter" rel="stylesheet"> */

Frequently asked questions

Is Google Fonts GDPR compliant?

The fonts themselves are not the problem; where they are loaded from is. Loaded from Google’s servers, every page view sends the visitor’s IP address to Google. Served from your own domain, the same fonts involve no third party. This page is general information, not legal advice.

Am I allowed to self-host Google Fonts?

Yes. Google Fonts are published under open licences (most under the SIL Open Font License), which allow you to download the files and serve them from your own server.

Can I ask for consent before loading the fonts instead?

You can, but until the visitor accepts, the page has to render with fallback fonts. Self-hosting is simpler and usually makes the page faster as well.

Does the free scan check my whole site?

The free scan checks the page you enter — as many single pages as you like. A site-wide crawl (up to 25 pages on Monitor, 250 on Compliance) finds pages where a different template still loads Google Fonts.

Do I need to sign up?

No. The scan is free, needs no account and returns results in under a minute.

See what your page does before consent

One page, free, no account. Monitoring and site-wide evidence when you need them.

Related

Sources

PrivaScan is automated: it reports what a browser can observe on the pages it tested. This page is general information, not legal advice.

Also from Talivio: A11yProof TCSR CanopyProof All Talivio products Talivio Technology OÜ · Tallinn, Estonia Made by Talivio.