Works with your stack
Cookie consent and web fonts: Google Fonts, Adobe Fonts, Bunny Fonts
fonts from your own server
Fonts set no cookie, but a font loaded from another company’s server sends each visitor’s IP address there before any choice. Cookie Rocks Pro copies the Google Fonts it finds in your pages and stylesheets, on by default, so those addresses stop going to Google. Adobe Fonts cannot be copied, because of its licence: the free Audit flags it, and the cookie policy names it.
Fonts, one by one
Where your fonts can come from
- Google Fonts
- Loaded from Google’s servers, often by the theme or a page builder: Google Fonts. No cookie, but each visitor’s IP address reaches Google.
- Adobe Fonts
- Loaded from Adobe’s servers, with a page-view counter that serves Adobe’s licence: Adobe Fonts. No cookie, but the IP address reaches Adobe in the United States.
- Bunny Fonts
- A drop-in replacement for Google Fonts, on servers in the European Union: Bunny Fonts. No cookie, but the IP address still reaches the font provider.
- Your own server
- Font files served by your site like any image. Nothing reaches another company.
- OMGF
- A free plugin that copies Google Fonts to your server and rewrites the links to them. It also handles Bunny Fonts links, and sets no cookie.
What matters for consent with Fonts
Never held
A page without its fonts looks broken. Cookie Rocks never holds Google Fonts, Adobe Fonts or Bunny Fonts, so your site keeps its look for every visitor.
Named in your cookie policy
The cookie policy that Cookie Rocks writes names each font provider it finds on your pages, so visitors know where their address goes.
A report of your fonts
After a scan, the free Audit lists the fonts that load from another site before any choice: Google Fonts, Adobe Fonts, Bunny Fonts, Font Awesome, Fontshare, Monotype, or another font file. You see the families, on how many pages, and what each licence allows.
Google Fonts: copied to your site
Cookie Rocks Pro copies the Google Fonts it finds in your pages and stylesheets, on by default, including those a stylesheet loads with @import. Once that is done, visitors’ addresses stop going to Google for those fonts. Without Pro, OMGF or your theme may host them.
What Pro cannot copy
Cookie Rocks Pro lists each font with its state. Adobe Fonts, Font Awesome, Fontshare and Monotype show as not copied, and Bunny Fonts stays in the Audit report. A font loaded by a plugin in another way can escape the copy: check the list.
Adobe Fonts cannot move
Adobe’s licence does not allow hosting its fonts on your site. Name Adobe Fonts in your policy, or choose fonts you can host yourself.
Bunny Fonts: closer, not at home
Bunny Fonts keeps the address in the European Union and sets no cookie. The address still leaves your site. Its fonts are open, so you can host the same fonts yourself and go one step further.
What OMGF does not catch
The free version of OMGF does not catch fonts loaded with @import, inline @font-face rules or a script. Fonts inside embedded maps, videos or reCAPTCHA come with the embed and wait for consent with it.
What our tests found on Fonts
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.
Fonts
Other plugins of the same kind.
Questions
Does the free Audit check my fonts?
Yes. After a scan, it lists the fonts loaded from another site before any choice, with their families, the number of pages and what each licence allows, and it offers to install OMGF for Google Fonts. It reads the pages it opens: a font used only on another page does not appear.
Why not hold fonts until consent?
Your pages would show fallback fonts to every visitor who has not chosen yet, and to everyone who refuses. Cookie Rocks prefers to name the fonts and help you host them.
I use Divi. Does OMGF find its fonts?
Only once Divi’s Improve Google Fonts Loading option is turned off, under Theme Options, Performance. See Divi.
Should I switch to Bunny Fonts?
It keeps the address in the European Union with no change to your design. Hosting the fonts yourself, with OMGF or your theme, avoids any third party at all.
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 sites with web fonts
Your fonts, named and explained.
fonts are never held
Every feature of the complete plugin for 30 days, no card. Your fonts keep loading as they do 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.