This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung →
Data protection
Why should Google Fonts be hosted locally?
Because fonts from Google's server transmit the visitor's IP address to Google on every page visit — without the visitor being asked. If the same font files sit on your own server, this transmission disappears entirely. Our check measures whether your website loads fonts from third-party servers like Google Fonts or Adobe Fonts, and names the providers involved in the report.
How the IP address reaches Google
Many websites embed their fonts with a single line that points to Google's servers. Every visitor's browser then fetches the font files directly from there — inevitably transmitting its IP address to Google in the process, on every single page visit. The visitor notices none of this, and a consent banner usually doesn't help, since the font loads before any decision is made. The alternative is simple: the font files are downloaded once and served from your own server. The typeface stays identical, because they're the same files.
The ruling behind the wave of cease-and-desist letters
The Munich I Regional Court ruled in 2022 (case no. 3 O 17493/20) that embedding Google Fonts via Google's server without consent violates the general right of personality — with an obligation to cease and desist, and to pay damages. Numerous cease-and-desist letters to website operators subsequently relied on this ruling. Our check is a technical examination, not legal advice; but it does establish exactly the fact at issue in such proceedings: whether the website loads fonts from third-party servers or its own. That answer is stated clearly in the report.
What the check exactly measures
The checker watches every browser connection while your page loads and recognises the known font servers: the Google Fonts addresses as well as Adobe Fonts (Typekit). If either is contacted, the rule counts as unmet, and the report names the provider. If every font comes from your own server, the rule passes. Watch out for ready-made design templates and plugins: many load Google Fonts without asking, even when the website itself has been set up cleanly. That's why it's worth checking again after every major change.
- Open the developer tools (F12 key), the "Network" tab, reload the page, and search for "fonts.googleapis.com" or "use.typekit.net".
- Ask your agency to download the font files used and serve them from your own server.
- Check design templates and plugins separately — many load Google Fonts without asking.
- Repeat the test after every theme or plugin update.
- While you're at it, also move other third-party files like icon fonts to your own server.
FAQ
How can I tell whether my website loads Google Fonts from Google's server?
Open the page, press the F12 key, select the "Network" tab, and reload. If "fonts.googleapis.com" or "fonts.gstatic.com" shows up in the list, the fonts come from Google. Our check performs the same observation automatically and names the font providers found in the report.
Do locally hosted fonts look different?
No. They're exactly the same font files — they just sit on your own server instead of Google's. Nothing changes about the typeface for visitors. The difference is purely in the data flow: the visitor's browser no longer contacts a Google server, and their IP address stays with you.
Does the check only cover Google Fonts?
No. The check also recognises Adobe Fonts (Typekit) as a third-party font service. The same pattern applies to both: the font loads from a third-party server on page visit, and the visitor's IP address flows there in the process. The report names every provider found individually.
Do I need to ask visitors if the fonts are hosted locally?
For the fonts themselves, there's then no contact with third-party servers left — there's simply nothing for the visitor to consent to. The check counts the rule as met in this case. Whether your website needs consent for other reasons depends on the other services it uses.