Every web font a page pulls from someone else's server tells that server who is\nvisiting. Before a single letter appears, the browser has to send the visitor's\nIP address, the referring page and the user agent to that provider. Nothing is\ncached away, nothing is anonymous \u2014 it happens on every page view, for every\nvisitor.<\/p>\n\n
In the EU that is a data transfer, and it needs a legal basis. A German court\ndecided in January 2022 (LG M\u00fcnchen I, 3 O 17493\/20) that embedding Google Fonts\nwithout consent violates the GDPR, and awarded damages to the plaintiff; a wave\nof warning letters followed. The same reasoning applies to Font Awesome, to icon\nfonts pulled from a CDN, and to any other font host.<\/p>\n\n
Serving the fonts from your own domain removes the problem at its source: no\nthird party is contacted, so there is nothing to consent to and nothing to\ndeclare. Your pages also stop depending on someone else's uptime.<\/p>\n\n
This plugin removes those requests. Whether your site is compliant overall is a\nlegal question, and no plugin can answer that for you.<\/p>\n\n
Web fonts arrive on a WordPress site in more than one way. A theme may enqueue a\nstylesheet, a page builder may write the font CSS straight into the page, and a\nstylesheet from a CDN may pull in font files of its own. Tools that only filter\nenqueued stylesheets see the first case and miss the rest \u2014 which is why fonts\noften still load from a third party after a font localiser reports success.<\/p>\n\n
This plugin looks in all three places, lists what it finds, and tells you where\neach request came from. Nothing is downloaded until you say so.<\/p>\n\n
This plugin exists to end<\/em> the connections your site makes to third-party font\nhosts. It never loads a script, stylesheet, image or font from a remote server\ninto your pages, and it contacts no service of ours: there is no account, no\nAPI key, no registration and no telemetry.<\/p>\n\n The one thing it does over the network is the localisation itself, and it is\nthe service this plugin provides: it downloads a copy of the font stylesheets\nand font files your site is already<\/strong> loading from a third party, stores them\nunder Which hosts are contacted therefore depends entirely on what your own site\nloads, and on nothing this plugin decides. The names below are the detection\nlist \u2014 the hosts the plugin recognises as font providers so that it can offer\nto take their files off your pages. They are not assets it loads:<\/p>\n\n Providers whose licence forbids self-hosting are recognised as well, so that\nthey can be reported to you with an explanation. They are listed and never\ndownloaded from: Adobe Fonts (use.typekit.net, p.typekit.net), Monotype\n(fast.fonts.net) and Hoefler & Co. (cloud.typography.com).<\/p>\n\n Any other font host can be added by name in the settings, one per line; those\nare treated exactly the same way and are contacted only by the same explicit\naction. Only the URL of the font resource is requested \u2014 no data about your\nsite or its visitors is transmitted.<\/p>\n\n The \"Check front page now\" button requests a page of your own site, nothing else.<\/p>\n\n\n That is the first column of the table. The plugin reads the stylesheet handle\nWordPress prints with every asset, and resolves it to the plugin or theme behind\nit \u2014 so you can fix the cause instead of just the symptom, or decide the feature\nis not worth the request at all.<\/p><\/dd>\n No. Detection is entirely local. Files are downloaded only once you tick\n\"Store pending fonts locally\" and save, or on the hourly schedule if you switch\nthat on yourself.<\/p><\/dd>\n That is the usual case with page builders. They fetch and inline the font CSS\nthemselves, so it never passes through the stylesheet filter other plugins hook\ninto. This plugin also searches the finished page output, which is where that\nCSS ends up. It reads that output through the template output buffer WordPress\n6.9 provides for the purpose, which is why that version is the minimum.<\/p><\/dd>\n No. The stored files point at each other by file name, and the public address is\nrebuilt on every request, so a move is invisible to them. Copies made by earlier\nversions did contain the old address; opening the settings screen once after the\nmove repairs them and says so.<\/p><\/dd>\n In Yes, one host name per line in the settings. Only stylesheets and font files are\ntaken from additional hosts.<\/p><\/dd>\n\n<\/dl>\n\n\nwp-content\/uploads\/wonderful-selfhosted-fonts\/<\/code>, and serves them from\nyour own domain from then on. A request happens only after you tick \"Store\npending fonts locally\" in the settings and save, or on the hourly schedule if\nyou switch that on yourself. Nothing is downloaded while a page is rendered.<\/p>\n\n\n
\n
\n
Which of my plugins is actually loading a font from Google?<\/h3><\/dt>\n
Does this send anything anywhere on its own?<\/h3><\/dt>\n
My font localiser said everything was fine, yet fonts still load from Google.<\/h3><\/dt>\n
I moved the site to another domain. Do I have to mirror everything again?<\/h3><\/dt>\n
Where are the files stored?<\/h3><\/dt>\n
wp-content\/uploads\/wonderful-selfhosted-fonts\/<\/code>, protected against PHP\nexecution. Deleting the plugin removes the folder again.<\/p><\/dd>\nCan I add my own font host?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n