Works with your stack
Cookie Rocks and OMGF: Google Fonts from your own server
fonts at home
OMGF copies Google Fonts to your server and rewrites the links to them, so visitors’ addresses no longer reach Google for those fonts. It sets no cookie and stores nothing in the browser. Some fonts escape it in the free version.
By Daan.dev · daan.dev · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
OMGF
WordPress plugin
- Tested version
- 6.4.1
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 6.4.1 tested
- Active installs
- 300,000+
What OMGF adds to your visitors’ browser
No trackers In our test of OMGF 6.4.1 on 7 November 2026, the plugin itself added no tracker and no cookie. What you place in your pages with it, such as a video or a map, still counts.
What matters for consent with OMGF
Font links served locally
OMGF replaces font stylesheet links from Google Fonts and Bunny Fonts with local copies, and removes the hints that connect to those hosts. It touches no script and no iframe.
What stays on Google
Fonts loaded by @import, inline @font-face or a script still come from Google in the free version. Fonts inside maps, videos or reCAPTCHA come with the embed. OMGF’s dashboard lists them.
Test mode is for admins
In test mode, only administrators get local fonts. Visitors still load Google Fonts until you leave test mode.
Divi fonts too
On a Divi site, OMGF served every font, Divi’s included, from the site’s own domain, with no request to Google’s font servers.
Cookie Rocks with OMGF
- Suggests it when your site loads Google Fonts from Google, so the fonts come from your own site.
What our tests found on OMGF
Good to know · Cookie RocksThe audit names the local fonts setting of your theme
When the home page loads Google Fonts, the Cookie Rocks 2.9.5 audit names the setting of the active theme or plugin that serves them from the site: Elementor, WP Rocket, Spectra, Kadence Blocks, OMGF, Local Google Fonts, Astra, Kadence, OceanWP or Neve. Otherwise it suggests a plugin such as OMGF. Divi, Bricks, Oxygen and Beaver Builder have no such setting. With Cookie Rocks Pro, it points to « Serve Google Fonts from this site » instead.
Read in its code, 1 November 2026, Cookie Rocks.
Good to know · Cookie Rocks ProCookie Rocks Pro leaves local fonts alone
Cookie Rocks Pro 2.9.5 reads the page as it is served. Fonts that a theme or another plugin already serves from the site leave no Google address in the page, and the Pro does not touch them. It copies only what still points to Google: for example when Elementor falls back to Google after a failed download, or when OMGF is still in test mode.
Read in its code, 1 November 2026, Cookie Rocks Pro.
Good to know · DiviDivi 5 links variable Google Fonts, and OMGF still serves them
Divi 5.15.1 links its Google fonts as variable fonts, in a stylesheet with id et-builder-googlefonts-cached-variable-css (et-builder-googlefonts-variable-css on the first page built without cache). On a live Divi 5 site with OMGF, both were served from /wp-content/uploads/omgf/, with no request to Google. Turning « Improve Google Fonts Loading » on did not change that: Divi 5 kept the link and OMGF kept serving it.
Seen in our tests, 1 November 2026, Divi 5.15.1.
Good to know · OMGFOMGF replaces Google Fonts links with local copies and sets no cookie
It rewrites only font stylesheet links (Google, Bunny, WordPress.com) and removes hints to those hosts; it touches no script or frame. After Save & Optimize it empties known page caches.
Read in its code, 16 October 2026, OMGF 6.3.13.
Full detail
OMGF 6.3.13 works in its own output buffer (template_redirect, priority 3) and only rewrites <link> stylesheets from fonts.googleapis.com, fonts.bunny.net and fonts-api.wp.com to local copies in uploads/omgf/, removing preconnect, dns-prefetch and preload hints to those hosts; it touches no script or iframe. It sets no cookie and no browser storage; its front script loads only for logged-in administrators. After Save & Optimize it purges known page caches.
Depends on a setting · OMGFSome fonts still come from Google with OMGF free
setting “Test mode”
- Fonts loaded by @import, inline @font-face, webfont.js or JavaScript.
- Fonts inside third-party frames (maps, videos, reCAPTCHA), listed in its dashboard.
- In test mode, visitors still load Google; only administrators get local fonts.
- If a download fails, the original link is kept.
Read in its code, 16 October 2026, OMGF 6.3.13.
Full detail
With OMGF's free version, fonts loaded by @import, inline @font-face, webfont.js or JavaScript still come from Google, as do fonts inside third-party iframes (maps, videos, reCAPTCHA), which its dashboard lists. If a download fails, the original link is kept (since 6.3.12). In test mode, only administrators get local fonts and visitors still load Google. A request with ?nomgf returns the unprocessed page.
Good to know · OMGFOMGF serves Divi's Google Fonts from the site, with no request to Google
The free version did this by itself on activation. Its warning about unused fonts concerns fonts the browser does not download.
Seen in our tests, 9 October 2026, OMGF.
Full detail
On a Divi site, OMGF (free version) replaced the Google Fonts stylesheets with local copies by itself on activation: every font, Divi's included, was served from /wp-content/uploads/omgf/ on the site's own domain, and the page sent no request to Google's font servers. OMGF's warning about unused fonts concerns @font-face declarations the browser does not download.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- OMGF 6.4.1, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- Settings of the test: Default settings after activation.
- Last run: OMGF 6.4.1 on 7 November 2026, with WordPress 7.1.4.
Fonts
Other plugins of the same kind.
Questions
Do fonts need consent?
Fonts set no cookie, and Cookie Rocks never holds them. See fonts for why hosting them yourself is the safest choice.
Does Cookie Rocks Pro copy fonts too?
Yes: it copies the Google Fonts it finds in your pages and stylesheets, including those loaded with @import, which the free version of OMGF leaves on Google. The free Cookie Rocks Audit lists what your pages load, with or without OMGF.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For OMGF users
Fonts at home, trackers held.
fonts are never held
Every feature of the complete plugin for 30 days, no card. OMGF keeps working as it does today.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.