Google Fonts Control by Volade
Google Fonts locally — GDPR and LCP without duct tape.
Google Fonts Control by Volade scans theme and enqueued styles, downloads woff2 files, rewrites front-end URLs and ships four presets (GDPR strict, performance, agency, block editor safe). Modern Easy Google Fonts fork — no account for essentials.
3-step workflow
- 1Run scan — inventory detected Google fonts
- 2Sync woff2 locally — one click per family
- 3Apply GDPR or performance preset — JSON export for client
GDPR context
Google Fonts and data transfers
Loading fonts from Google servers exposes visitor IPs to a US third party. Local hosting is the simplest fix on WordPress.
Munich 2022
GDPR fines possible
Automatic scan, local woff2 hosting, 4 presets and JSON export — no account, no Google requests on page load.
4
Presets
100%
Local hosting
woff2
Modern format
€0
Usage fees
At a glance
Easy Google Fonts has been abandoned for five years — your Google fonts still load from fonts.googleapis.com with US data transfers and LCP penalty. Google Fonts Control by Volade v1.0.0 scans theme and enqueued styles, downloads woff2 locally, rewrites front-end URLs, ships four presets (GDPR strict, performance, agency, block editor safe) and free JSON export — modern fork without breaking Gutenberg or the customizer.
Screenshots
Admin-Oberfläche in voller Seitenansicht — Voreinstellungen, Diagnose und detaillierte Einstellungen.
Why Google Fonts are a problem on WordPress
Munich ruling, abandoned Easy Google Fonts, complex OMGF or tedious manual hosting — your fonts deserve better.
The problem: Google fonts still external
Munich, LCP and abandoned plugins — typical WordPress stack.
Your theme, page builder or legacy plugin still loads fonts.googleapis.com. Easy Google Fonts is unmaintained. OMGF needs careful setup. Manual hosting doesn't follow theme changes.
- fonts.googleapis.com: visitor IP sent to Google — Munich C-252/21 context
- Easy Google Fonts: abandoned ~5 years — broken customizer on recent WP 6.x
- OMGF: excellent but heavy UI — no ready agency presets
- Manual hosting: @font-face forgotten on every variant change
- CDN proxy: better than direct Google, still third-party and DNS latency
The Google Fonts Control answer
Scan + local sync + rewrite — in WordPress, no mandatory cloud.
A Volade plugin that inventories Google fonts, downloads woff2 to your server, rewrites URLs and ships four business presets — free without account for scan, sync and JSON export.
- Theme + wp_enqueue scan — sources and handles identified
- woff2 download to uploads/volade-gfc/
- Front-end URL rewrite — no more fonts.gstatic.com
- 4 presets: GDPR strict, performance, agency, block editor safe
- Optional display:swap and strip preconnect
- JSON inventory export — agency / DPO handoff
- wp gfc scan | sync | preset — scriptable (V+)
4 presets, zero guesswork
GDPR strict, performance, agency or block editor — settings ready for your context.
GDPR strict
Local hosting + block residual external requests — DPO recommended preset.
RecommendedPerformance
display:swap, strip preconnect, subsetting with connected account — Core Web Vitals.
LCPAgency
Full scan, sync all families, JSON client handoff — clean delivery.
AgencyBlock editor safe
Doesn't break Gutenberg preview or customizer — editor fonts preserved.
Gutenberg4 sync states
Detected, syncing, synced, blocked — clear inventory of every Google Fonts family.
Google URL found in theme, enqueue or inline CSS.
woff2 download in progress from fonts.gstatic.com.
Local file served — URL rewritten on front.
External request blocked by GDPR strict preset.
Every font is tracked in inventory — exportable proof for GDPR audit or client sign-off.
Before / after in code
External URLs become woff2 files served from your domain.
Detected
Scan finds Google URL in theme.css or wp_enqueue_style.
Sync
woff2 download to wp-content/uploads/volade-gfc/.
Rewritten
Front-end serves /volade-gfc/... instead of fonts.gstatic.com.
Blocked
GDPR preset option: block any remaining external request.
Page header
Headline in Playfair Display
Visitors no longer contact fonts.googleapis.com or fonts.gstatic.com — less DNS, fewer implicit third-party requests, better DPO control.
Real scenarios
What changes after activation.
Elementor brochure site
Before: 12 Google families via theme + Elementor — Munich unaddressed
After: Scan + sync + GDPR preset — zero fonts.googleapis.com requests
GDPR +
WooCommerce store
Before: LCP 3.2s — fonts block render
After: Performance preset + display:swap — LCP often < 2.5s
Perf +
Agency multisite
Before: 40 sites — fonts copied manually in child themes
After: wp gfc scan per site + V+ JSON rollup
Fast handoff
What Easy Google Fonts and manual hosting don't deliver
Theme + enqueue scan, woff2 download, URL rewrite and presets — without breaking Gutenberg.
Automatic scan
Theme, enqueue and inline CSS — full Google URL inventory.
woff2 hosting
Files in uploads/volade-gfc/ — served from your domain.
URL rewrite
Replaces fonts.gstatic.com and fonts.googleapis.com at runtime.
4 presets
GDPR strict, performance, agency, block editor safe.
Site Health
Remaining external fonts indicator — clear dashboard.
JSON export
Downloadable inventory — audit handoff without Volade cloud.
WP-CLI
wp gfc scan, sync, preset — agency pipelines (V+).
Volade SDK
Discover, XP, V+ premium — same chart as other extensions.
The Munich ruling (C-252/21) confirmed that loading Google Fonts from fonts.googleapis.com can transfer visitor data to the US — local hosting reduces that risk and often improves LCP.
WordPress Google Fonts landscape in 2026
Easy Google Fonts is dead, OMGF is powerful but heavy, manual hosting doesn't scale — GFC targets the agency sweet spot.
Easy Google Fonts
100K+ historical installs — Google Fonts customizer, last update 5 years ago.
Limit: Abandoned, still loads from Google, unpatched security issues, poor PHP 8.3 fit.
OMGF (Optimize My Google Fonts)
Popular local hosting, subsetting, preconnect, Elementor/Divi compatibility.
Limit: Dense UI, many settings, agency learning curve, no Easy Google Fonts fork or Volade presets.
Manual self-hosting
Download woff2, @font-face in child theme, disable Google enqueue.
Limit: Every font change needs FTP, no auto scan, italic variants often forgotten.
Bunny Fonts / CDN proxy
Replaces fonts.googleapis.com with EU proxy — not local files.
Limit: Still a third-party request, CDN dependency, less DPO control than full self-host.
Privacy-friendly theme
Some premium themes bundle system or local fonts.
Limit: Locked to theme — change theme, lose config; no cross-plugin inventory.
Ignore the issue
Leave Google Fonts as-is — "everyone does it".
Limit: Documented GDPR risk, LCP penalty, hard to defend to clients.
Comparison table — 4 approaches
Google Fonts Control by Volade vs Easy Google Fonts, OMGF and manual hosting — agency and DPO criteria.
| Feature | GFC Volade | Easy Google Fonts | OMGF | Manual |
|---|---|---|---|---|
| Free sans compte (cœur core) | ||||
| Maintenu en 2026 | ~ | |||
| Auto theme scan + enqueue | ~ | |||
| Download woff2 local | ||||
| Rewrite URLs runtime | ~ | |||
| 4 presets core ready | ~ | |||
| Blocking requests external | ~ | |||
| Block editor / customizer safe | ~ | ~ | ||
| Export JSON inventaire | ~ | |||
| WP-CLI agence | ~ | ~ | ||
| Subsetting par page | ~ | ~ | ||
| Courbe apprentissage faible | ||||
| Fork Easy Google Fonts | ||||
| Zero Google requests on load | ||||
| Cost usage unlimited | 0 € | 0 € | 0 € | Temps |
Public sources: WordPress.org, OMGF docs, CJEU C-252/21 — July 2026. OMGF remains excellent for power users; GFC targets agency simplicity, presets and Volade JSON export. Verify DPIA with counsel.
Three tiers, one plugin
Core features, scan and presets free without account. Volade account for subsetting. V+ for multisite and WP-CLI bulk.
No account
- Theme + enqueue scan
- Local woff2 sync
- 4 presets
- URL rewrite
- JSON export
- Fonts Site Health
Volade account
- All free features
- Per-page subsetting
- Multi-site config sync
- CSV inventory export
V+ Premium
- WP-CLI bulk scan/sync
- Multisite rollup
- Network font policy
- 50+ site onboarding
WP-CLI and multisite to deploy the same font rules across the network.
WP-CLI
Scan, sync and apply presets from SSH — no admin UI needed.
wp gfc scan wp gfc sync wp gfc preset gdpr_strict
Multisite
Per-site font policy; central inventory rollup on V+ Premium.
- Per-site network dashboard
- Consolidated agency export
- Harmonized GDPR presets
Download
Install the ZIP, run scan, apply GDPR strict preset — local fonts in under five minutes.
ZIP with Volade SDK — activate under Volade → Google Fonts Control (or Settings → Google Fonts Control).
- 1Plugins → Add New → Upload → select ZIP → Activate
- 2Volade → Google Fonts Control (or Settings → Google Fonts Control)
- 3Run scan → sync fonts → apply GDPR strict preset
First local fonts in under 5 minutes
Frequently asked questions
GDPR, Munich ruling, Easy Google Fonts, OMGF, LCP performance and Volade account.
No. Munich (C-252/21) concerns transferring visitor data (IP) to Google without legal basis. Local hosting or explicit consent are common paths — local is often simplest technically.
Free vs V+ Premium
The extension works without an account. V+ unlocks premium on this extension and the full catalog.
| Feature | Free | V+ |
|---|---|---|
| Installation & configuration de base | ||
| Mises à jour automatiques | ||
| Support communauté | ||
| Fonctions avancées & exports | ||
| Quotas & limites relevés | ||
| Automatisations & intégrations pro | ||
| Licence multi-sites (selon formule V+) |
Community
Share your experience with Google Fonts Control by Volade and follow the latest releases.
Ready for local fonts?
Download Google Fonts Control by Volade v1.0.0 — scan, sync and GDPR strict preset in one click, no signup.
Download v1.0.0