Adrian Mörchen

moewe.io

Markus Weigelt

Embed Google Fonts tries to automatically replace registered Google Fonts from themes and plugins with local versions, directly loaded from your own server.
Contribute: <a href="https://github.com/moewe-io/embed-google-fonts" rel="nofollow ugc">https://github.com/moewe-io/embed-google-fonts</a>
Notes
<ul>
<li>The first request might be very slow, as fonts are downloaded and cached the first time they are requested.</li>
<li>This doesn’t automatically replace all your Google fonts with local versions. If a plugin/theme doesn’t use WordPress wp_enqueue_style it probably won’t work.</li>
<li>Loaded fonts are not optimized, means, the whole font including all subsets is loaded</li>
<li>See FAQ for instructions to use locally hosted fonts directly and avoid using Heroku</li>
</ul>
Thank you: Fonts are downloaded using: <a href="https://gwfh.mranftl.com/fonts" rel="nofollow ugc">https://gwfh.mranftl.com/fonts</a>

Embed Google Fonts

Really great, thanks a lot! Works out of the box, prevents from GDPR/DSGVO issues. 

Great plugin!

Embed Google Fonts tries to automatically replace registered Google Fonts from themes and plugin with local versions, directly loaded from your own se …

Browse.FYI

LocalFonts automatically detects, downloads, and serves Google Fonts from your own server instead of loading them from Google’s external CDN. No manual configuration needed — just activate and your site’s fonts are instantly self-hosted.
<h4>Why Self-Host Google Fonts?</h4>
Loading web fonts from Google’s servers (fonts.googleapis.com and fonts.gstatic.com) sends your visitors’ IP addresses to Google with every page load. This raises serious privacy concerns and has legal implications under data protection regulations worldwide.
<ul>
<li>GDPR & DSGVO Compliance — European courts have ruled that loading Google Fonts from Google’s servers without consent violates GDPR (General Data Protection Regulation) / DSGVO (Datenschutz-Grundverordnung). A German court fined a website operator for transmitting visitor IP addresses to Google via externally loaded fonts. Self-hosting fonts eliminates this risk entirely.</li>
<li>Privacy Protection — When fonts are served locally, zero connections are made to Google’s servers. No visitor IP addresses are transmitted, no tracking occurs, and no third-party requests are made. Your visitors’ data stays on your server.</li>
<li>Faster Page Load Times — Eliminate extra DNS lookups, TCP connections, and TLS handshakes to fonts.googleapis.com and fonts.gstatic.com. Local fonts load from the same server as your site, reducing latency and improving Core Web Vitals metrics including Largest Contentful Paint (LCP), First Contentful Paint (FCP), and Cumulative Layout Shift (CLS).</li>
<li>Better PageSpeed & Performance Scores — Google PageSpeed Insights, GTmetrix, and Lighthouse often flag external font loading as a performance bottleneck. Self-hosting fonts eliminates “Reduce the impact of third-party code” and “Preconnect to required origins” warnings.</li>
<li>Reliability & Uptime — No dependency on Google’s CDN availability. Your fonts work even if Google’s servers are slow, blocked, or unreachable in certain regions or corporate networks.</li>
<li>Simplified Cookie Consent — By eliminating third-party connections to Google, you reduce the scope of your cookie consent and privacy policy requirements, as there are fewer external services to disclose.</li>
</ul>
<h4>What Google Font References Does It Catch?</h4>
This plugin intercepts Google Fonts loaded through every common method used by WordPress themes, plugins, and page builders:
<ul>
<li>Enqueued stylesheets — Fonts registered and enqueued via <code>wp_enqueue_style()</code> using the Google Fonts CSS API v1 (<code>/css?family=</code>) and CSS API v2 (<code>/css2?family=</code>)</li>
<li>Hardcoded <code><link></code> tags — Font references hardcoded directly in theme templates, header.php, footer.php, or plugin output</li>
<li>CSS <code>@import url(...)</code> rules — Import statements in inline <code><style></code> blocks and external stylesheets</li>
<li>CSS <code>@import "..."</code> rules — Import statements without the <code>url()</code> wrapper (valid CSS syntax)</li>
<li>Google Material Icons — References to the <code>/icon</code> endpoint at fonts.googleapis.com for Material Design icon fonts and Material Symbols</li>
<li>Protocol-relative URLs — URLs starting with <code>//fonts.googleapis.com</code> (without https:)</li>
<li>HTML-encoded URLs — URLs containing <code>&amp;</code> and other HTML entities commonly output by themes and page builders</li>
</ul>
It also removes <code>dns-prefetch</code> and <code>preconnect</code> resource hints for <code>fonts.googleapis.com</code> and <code>fonts.gstatic.com</code>, ensuring your site makes absolutely zero connections to Google’s font servers.
<h4>How It Works</h4>
<ol>
<li>Detect — On the first page load after activation, the plugin automatically identifies all Google Font URLs across your entire site.</li>
<li>Download — Font files are downloaded in the background via WP-Cron so visitors experience no delay. The plugin requests WOFF2 format — the smallest and fastest web font format supported by all modern browsers.</li>
<li>Rewrite — All Google Font references in your page HTML are rewritten to point to the locally hosted copies on your server.</li>
<li>Serve — Subsequent page loads serve the cached local font files instantly from your own server with no external requests.</li>
</ol>
Font files are stored in <code>wp-content/uploads/lgfl-fonts/</code> with each unique font URL getting its own subdirectory.
<h4>Compatibility</h4>
LocalFonts works with virtually any WordPress setup:
<ul>
<li>Any WordPress theme — flavor starter themes, starter themes, commercial themes, custom themes, classic themes, and block themes (Full Site Editing)</li>
<li>Page builders — Elementor, Beaver Builder, Divi, WPBakery, Brizy, Oxygen, Bricks, Breakdance, Kadence, GeneratePress, Avada, and more</li>
<li>WooCommerce — Catches fonts loaded by WooCommerce and its extensions</li>
<li>Block Editor (Gutenberg) — Works with the native WordPress block editor and block-based themes</li>
<li>Multilingual plugins — Compatible with WPML, Polylang, TranslatePress, and other translation solutions</li>
<li>Caching plugins — Works alongside WP Super Cache, W3 Total Cache, LiteSpeed Cache, WP Rocket, and other caching solutions</li>
<li>Any plugin that loads Google Fonts — If it loads fonts from fonts.googleapis.com, LocalFonts will catch and self-host them</li>
</ul>
<h4>Features</h4>
<ul>
<li>Zero configuration — Works automatically on activation with no settings to configure</li>
<li>Enable/disable toggle — Easily turn local font hosting on and off from Settings</li>
<li>Manual download button — Pre-download all detected Google Fonts with one click</li>
<li>System status dashboard — Check write permissions, filesystem method, and font storage directory status at a glance</li>
<li>Async background downloads — Fonts are downloaded via WP-Cron in the background so the first visitor is never delayed</li>
<li>Clean uninstall — All downloaded font files and plugin settings are removed when you uninstall the plugin, following WordPress best practices</li>
</ul>
<h3>External services</h3>
This plugin connects to the Google Fonts API (fonts.googleapis.com) and the Google Fonts CDN (fonts.gstatic.com) to download font files for local hosting. These connections happen only when a Google Font URL is first detected on your site and is not yet cached locally.
What is sent: the Google Font family name and variant parameters as they appear in the requesting CSS URL (e.g., <code>family=Roboto:wght@400;700</code>). No site data, user data, or personal information is transmitted.
When it is sent: once per unique Google Font URL, during an asynchronous WP-Cron job triggered the first time the font is seen. All subsequent page loads serve font files from your own server with zero external requests.
Service provider: Google LLC 
Terms of Service: https://developers.google.com/fonts/faq#what_does_using_the_google_fonts_api_mean_for_the_privacy_of_my_users 
Privacy Policy: https://policies.google.com/privacy

LocalFonts

Self-host Google Fonts for faster load times, GDPR/DSGVO compliance, and visitor privacy. Zero configuration required.

Embed Google Fonts vs LocalFonts