Google Fonts and GDPR: Why Many Sites Now Host Fonts Themselves
Short answer: When a website loads a Google Font from Google's servers, the visitor's browser sends its IP address to Google, which is personal data under the GDPR. A 2022 ruling by a German regional court against a website that loaded fonts this way brought the issue to wider attention, and many European sites have since moved fonts onto their own server. Self-hosting means downloading the font files, placing them on your domain and pointing your stylesheet at them. Check the font's licence allows this, then open your browser's developer tools and confirm that no requests go to Google's font domains. Fonts loaded from your own server also tend to appear faster.
What actually happens when a font loads
A typical website includes a line in its head section that calls a Google Fonts stylesheet. When a visitor opens a page, their browser asks Google's servers for the stylesheet and then for the font files. The request includes the visitor's IP address and the browser details that come with any web request. Google does not need the visitor to log in for this to happen.
For a business that has an EU or UK audience, that transfer can count as processing personal data. The question is whether your site gives visitors a choice before it happens, and whether you have a lawful basis and a clear privacy notice. Many sites could not show either, which is why the issue became a regular source of complaints.
Here is a fictional example. A Dublin-based law firm called Harcourt Quay used a font from Google's servers on every page. A visitor in Berlin complained, and the firm was asked to explain the transfer. The simplest answer was to remove the external call, which took an afternoon.
Check whether your site makes the call
Before you change anything, see what your site does now.
- Open your website in a private browser window.
- Open the developer tools and go to the Network tab.
- Reload the page and filter for requests to fonts.googleapis.com and fonts.gstatic.com.
- Note each request and the page where it appeared.
- Check the page source for "fonts.googleapis.com" in stylesheets, scripts and plugins.
Plugins are the usual cause. A theme or page builder may load Google Fonts by default, even when you never selected it. Look in the plugin settings for an option to load fonts locally, or disable the font feature if you do not need it.
Download and serve the font
Google Fonts provides a download for each family, and the families are generally released under the SIL Open Font License, which permits self-hosting. Check the licence file in the download before you publish the font. Then follow these steps:
- Download the font family from the official Google Fonts page.
- Keep only the weights and styles you use. A typical body text needs regular and bold, and a heading may need one more weight.
- Convert or choose the WOFF2 format, which is supported by all modern browsers. Add WOFF as a fallback if you need older browser support.
- Upload the files to a folder on your own server, such as /fonts/, and keep the licence file with them.
- Write an @font-face rule that points to your local files and sets the font-display value. Setting font-display to swap shows text in a fallback font while the custom font loads, which keeps the page readable.
- Remove the old link to Google's stylesheet from your template, theme or plugin.
Here is an example rule for a font called Harbor Serif, using a made-up file name:
@font-face {
font-family: "Harbor Serif";
src: url("/fonts/harbor-serif-regular.woff2") format("woff2");
font-weight: 400;
font-style: normal;
font-display: swap;
}
Verify the change
Clear your website cache and any caching plugin, then repeat the network check. The page should show the font files coming from your own domain, and no requests to Google's font domains. Check on a phone as well, because some mobile themes load fonts through a different path.
Run the same check after any theme update, since a new version can bring the external link back.
Update your privacy notice
If you used Google Fonts before, your privacy notice may have described the transfer. Once you have removed it, you can simplify the text. If you still use other third-party tools, such as maps, video players or analytics, list them separately. Keep a dated record of the change, including the date you verified the network requests.
Speed and display notes
Self-hosting often improves speed because the font files come from the same server as the rest of your site, which reduces the number of connections the browser needs to open. Use only the weights you need, because each extra file adds weight. Preload the main font file if your heading is large and visible at the top of the page, and check the effect with a page speed tool before you keep the change.
Choose fallback fonts that look similar to your custom font, so the page does not jump when the custom font arrives.
Common mistakes
- Removing the link from the theme but leaving it in a plugin
- Copying the font files without the licence
- Forgetting to update the font files when a font family is revised
- Using a font that does not allow self-hosting, such as a paid licence that only covers web embedding through a provider
- Testing only on the homepage, when another template loads the stylesheet
A short checklist
- Network requests checked on the key pages
- Font families confirmed as licensed for self-hosting
- Licence file saved next to the font files
- Stylesheet updated and old link removed
- Plugin and theme settings checked
- Privacy notice updated if it mentioned Google Fonts
- Check repeated after each theme or plugin update
FAQ
Do I have to self-host Google Fonts?
Not legally in every case, but many European sites now do so to reduce the risk of transfers to Google without a lawful basis. Ask your privacy adviser for the position that applies to your site.
Will self-hosting slow my site down?
It usually helps, because the font files are served from your server and not a separate domain. The results depend on your hosting, so measure before and after.
Can I use a font from another vendor instead?
Yes. Any font that you license for web use can be self-hosted. Check the licence terms, which may limit the number of page views or domains.
Where can I find the official guidance?
Google's Fonts FAQ explains the download and self-hosting process, and the Data Protection Commission website covers the GDPR rules that apply in Ireland.
If you would like help checking your site for external font calls and moving the fonts onto your own server, reach out through our enquiry page.