What Does Firefox Let a Page Measure?
The font fingerprinting Firefox allows depends on which local fonts a page can see. Standard mode exposes every installed font; Private Browsing and Strict tracking protection restrict the set; Resist Fingerprinting locks pages to base system fonts. Remote web fonts still load, so Firefox cuts font entropy in some contexts without removing every font signal. For a stable result, you need to know which layer applies and keep it consistent.
📌 TL;DR Executive Summary
- Core Takeaway: Firefox restricts local fonts by context: Standard mode shows all installed fonts, Private Browsing and Strict tracking protection restrict the set, and Resist Fingerprinting locks pages to base system fonts. Remote web fonts still load.
- Key Risk/Challenge: Font metrics, canvas hashes and fallback tests can identify a browser even when its visible font list looks ordinary. Strict settings also break sites that depend on local fonts or language packs.
- Recommended Solution: Pick the least restrictive setting that meets your privacy need, verify preference names for your Firefox version, whitelist only fonts you need, and keep each managed account in a consistent isolated profile.
What Is Font Fingerprinting?
Font fingerprinting is the practice of measuring which fonts a browser can render and how those fonts draw text. A site does not need a neat list of installed fonts. It can test candidate names one by one, compare text dimensions against a generic fallback, and turn the results into a stable identifier. The font fingerprinting Firefox reports also shifts with the browsing context, which is why two windows on the same machine can look different to the same script.
The signal is stronger than many people expect. In the 2010 EFF Panopticlick study, the font list was one of the most identifying attributes alongside plugins and user agent. A 2015 study by Fifield and Egelman found that font metrics alone uniquely identified 34% of more than 1,000 browsers tested. That is why font fingerprinting protection has to address both the font list and the way fonts render.
Your font set says something about your machine. Designers install display and editorial families. Windows and macOS ship different defaults. Language packs add CJK, Arabic or Indic families. Office suites, PDF tools and creative apps add their own fonts. Each extra family narrows the population you blend into, which is the entropy problem in plain terms.
How Font Enumeration Works Under the Hood
Most font detection uses CSS fallback measurement. A script writes a string in a candidate font with a generic fallback behind it, then measures the element’s width and height. If the candidate is installed, the text uses its metrics; if not, the fallback renders. A difference in size reveals the font. Repeating this across dozens or hundreds of families builds a list without any permission prompt.
Canvas adds a second layer. The page draws the same text in several fonts, reads the pixels back and hashes them. Antialiasing, hinting, glyph shapes and fallback behaviour differ by font and operating system, so the hash acts as a compact font-and-rendering signature. The 2016 Princeton crawl of the top 1 million sites found canvas font fingerprinting on 3,250 sites.
Metric tests are efficient. The same research found that only 43 of more than 125,000 Unicode code points were needed to capture all the font-metric variation observed. A tracker does not need your full font list; a small set of well-chosen glyphs can separate you from other visitors.
The Local Font Access API Is Not a Silent Shortcut
The Local Font Access API exposes queryLocalFonts(), which returns the local font list. It is experimental, requires HTTPS and triggers a local-fonts permission prompt, so a tracker cannot read the list silently through this route. A permission-gated API is not the same as CSS measurement, which works without a prompt.
If you want to see whether Firefox’s canvas protections are active on your build, compare a normal window with a private one; this walkthrough on check Firefox canvas blocking shows what to look for. Canvas and font measurement often travel together, so a change in one usually shows up in the other.
Firefox’s Font Visibility Levels
Firefox does not use a single font setting. It applies a font visibility level to a browsing context. Level 1 exposes base OS fonts only. Level 2 adds fonts supplied by language packs. Level 3 exposes all local fonts. The level can differ between normal browsing, private windows and pages where tracking protection is active.
Standard tracking protection keeps level 3 by default to limit site breakage. Private Browsing windows and Strict tracking protection apply restrictions by default. Three preferences control the level: layout.css.font-visibility.standard, layout.css.font-visibility.private and layout.css.font-visibility.trackingprotection.
| Font visibility level | What a page can measure | Typical effect |
|---|---|---|
| Level 1 | Base OS fonts only | Smallest font set; strongest privacy; most likely to break sites that rely on installed families. |
| Level 2 | OS fonts plus language-pack fonts | Better rendering for non-Latin text; adds region-related entropy. |
| Level 3 | All local fonts | Highest compatibility; exposes your full installed set. |
This tiering is deliberate. Mozilla’s approach preserves information sites need to function, such as language and time zone settings, rather than randomising everything. Font visibility follows the same logic: restrict the high-entropy local set, but keep enough coverage that pages remain usable.
A common mistake is to assume Private Browsing always applies the strongest font restriction. It applies the private-context preference, which is restrictive by default but separate from Resist Fingerprinting. Strict mode applies the tracking-protection preference. Changing one preference does not necessarily change the others.
What Resist Fingerprinting Changes for Fonts
Setting privacy.resistFingerprinting to true is the strongest built-in option, and it alters font fingerprinting Firefox behaviour more than any other switch. It overrides the font-visibility preferences and locks visibility to Level 1, so pages see base system fonts regardless of browsing mode. Mozilla documents this behaviour in its font-visibility bug, and it is the setting most likely to cause site breakage.
RFP is inherited from the Tor Uplift work, and it changes more than fonts. It limits screen resolution APIs and can report processor counts as 4 or 8 instead of the exact count. Mozilla recommends it for experienced users rather than as a default. If a site behaves oddly, disable extensions one at a time; add-ons can flip Resist Fingerprinting preferences themselves.
Bundled Fonts, System Copies and the Whitelist
Firefox makes an exception for fonts bundled inside its install directory, such as C:\Program Files\Mozilla Firefox\fonts on Windows. Those fonts remain available with RFP on because they ship with the browser. A system-installed copy of the same font is treated differently: it is not exposed and can shadow the bundled one. That is why a font you can use in another app may appear unavailable to a page in Firefox.
From Firefox 81, the hidden preference font.system.whitelist takes a comma-delimited list of font names and overrides font visibility. You can use it to keep specific families visible on top of the base set, which is useful for CJK text or a house style. Add only the fonts you need; every extra family adds entropy.
Remote web fonts loaded through CSS @font-face are still allowed. They reveal nothing about your local machine, so blocking them would break design without improving font privacy. The restriction is about local fonts, not the web font a site chooses to serve.
Firefox’s newer fingerprinting work goes beyond fonts. Mozilla reports that Firefox 145’s expanded protections cut the share of users trackable by fingerprinters by about half, and its research describes reducing unique fingerprints and enlarging shared groups. Mozilla also states that these protections do not make fingerprinting impossible, since trackers can adapt. New protections debut in Private Browsing and Strict mode first, then move toward default-on. Treat font settings as one layer, not a complete identity system. You can read the overview in Mozilla’s fingerprinting protections.
layout.css.font-visibility.* or font.system.whitelist, check the preference names in your installed Firefox version. Bugzilla preferences can change between releases, and a copied value from an older build may do nothing.
How Font Entropy Affects Teams and Profile Consistency
Font entropy matters most when several people or sessions need to look like separate, stable environments. An agency managing client accounts, a support team testing as different users, or a QA team checking regional content all need predictable browser profiles. If one profile exposes a designer’s font collection and another exposes a clean OS set, the two sessions do not represent the same setup.
The browser fingerprint entropy concept explains the trade-off. A rare font combination puts you in a small group; a common combination puts you in a large one. Restricting fonts can enlarge the group, but randomising fonts per session can create a different problem: the font set changes between visits, so the session no longer looks like the same returning browser. For authorised account management, consistency usually matters more than maximum randomness.
| Browser | Font approach | Trade-off |
|---|---|---|
| Firefox | Visibility levels 1-3; RFP locks visibility to Level 1 | Context-dependent; strict settings can break local-font sites |
| Brave | OS fonts for top language; user-installed fonts presented as a random set per site and session since 1.39 | Not on Linux or iOS; per-session changes can look inconsistent |
| Tor Browser | System font allowlist plus bundled Noto fonts on Windows and macOS; bundled fonts only on Linux | Small shared set; less local-font compatibility |
None of these approaches erases fingerprinting; they change how much font data a page can collect. Language-pack exceptions are a subtler leak. Level 2 improves CJK rendering, but it also tells a page that your system has that language pack. If you enable Level 2 for one profile, keep it consistent and document why. That is the practical rule for the font fingerprinting Firefox exposes in any team setup: decide the level once, write it down, and apply it the same way to every profile that should look alike.
A Practical Checklist for Firefox Font Privacy
Use this checklist to choose a setting you can live with, then verify it in the contexts you actually browse.
- Start with Strict ETP or a private window. Both apply font restrictions by default and avoid about:config edits. Test your key sites there before changing anything else.
- Check the three visibility preferences. Open
about:configand inspectlayout.css.font-visibility.standard,.privateand.trackingprotection. Match each to the level you want for normal, private and tracking-protected contexts. - Enable RFP only if you accept breakage. Set
privacy.resistFingerprintingtotruewhen you need Level 1 everywhere. Expect some sites to render poorly or behave differently, and keep a separate profile for those sites. - Whitelist sparingly. If a language or house font fails under RFP, add its exact family name to
font.system.whitelistas a comma-delimited entry. Remove entries you no longer need. - Test bundled versus installed copies. If a font works in one app but not in Firefox, compare the bundled Firefox font with the system-installed copy. The system copy can shadow the bundled one.
- Verify in both normal and private windows. A setting that works in one context may not apply in the other. Repeat your font fingerprinting Firefox test in a normal window and a private window, then compare the measurements.
- Keep profiles separate and consistent. If you manage several authorised accounts, use separate Firefox profiles with documented font settings; this guide to set up Firefox profiles covers the basics. Do not share one profile across unrelated clients.
Common Mistakes with Firefox Font Settings
Most problems come from treating one preference as a complete privacy switch.
- Expecting RFP to erase font signals. Level 1 is a restriction, not a guarantee. Sites can still use canvas, WebGL, audio and other signals.
- Assuming private browsing covers every window. Private windows use the private font preference; normal windows do not. Extensions and site exceptions complicate the picture.
- Over-whitelisting. Adding ten fonts to
font.system.whitelistrestores compatibility but also restores entropy. Add one family at a time and test. - Randomising fonts per session. A font set that changes on every visit makes the browser look like a different device, and users see unstable rendering.
- Blaming Firefox for a bundled-font conflict. A system-installed copy of a bundled font can be withheld and shadow the copy inside the install directory.
- Forgetting extensions. An add-on can change RFP-related preferences. If behaviour changes after an update, disable add-ons one at a time.
- Treating the font list as the only signal. Metrics, canvas hashes and fallback behaviour can identify a browser even when the visible list looks common.
Where Send.win Fits
Firefox’s font controls are browser-wide or context-wide. They work well for one person on one machine, but they are not a per-client profile system. If you manage several authorised accounts, you need each account to open in its own isolated environment with a consistent fingerprint, not in the same Firefox install with the same font set and cookies.
Send.win is a browser profile manager for professionals and teams. The Sendwin Browser is a native desktop app for Windows, macOS and Linux, built on Chromium, with isolated profiles that each keep their own cookies, storage, sessions, fingerprint settings and proxy. The cloud browser runs profiles on Send.win’s cloud server in Helsinki, Finland, from any device. Each profile keeps a consistent browser fingerprint, including fonts, canvas, WebGL, audio and hardware, handled inside the browser engine.
That is different from a Firefox extension. Send.win is a standalone desktop and cloud application, not a browser add-on. Use Firefox’s own preferences when Firefox is the browser you need. Use Send.win when your team needs repeatable, isolated profiles across client accounts, QA cases or support roles, and when you want timezone, locale, WebRTC and geolocation to follow the proxy’s exit IP automatically. Use it only with accounts you own or are authorised to manage.
🏆 Send.win Verdict
Firefox gives you fine-grained font visibility controls, but they are browser-wide or context-wide, not per client account. Send.win is relevant when each authorised account needs its own isolated profile with consistent fingerprint settings, including fonts, instead of sharing one Firefox install.
See Send.win plans — paid plans start at $19/mo with a 7-day money-back guarantee on the first card purchase, and the free cloud demo needs no install.
Frequently Asked Questions
What is font fingerprinting and how does it identify me?
A site measures which fonts your browser can render and how they draw text. CSS fallback tests, canvas pixel hashes and font metrics combine into a signature. It identifies you by narrowing the population that shares your font set and rendering behaviour, not by reading a filename.
Does Firefox block font fingerprinting by default?
Not completely. Standard mode keeps Level 3 and exposes all local fonts by default, so the font fingerprinting Firefox performs in a normal window is the broadest case; Private Browsing and Strict tracking protection restrict fonts, and Resist Fingerprinting locks Level 1. Remote web fonts still load, and other fingerprinting surfaces remain.
How do I enable resistFingerprinting in about:config?
Open about:config, search for privacy.resistFingerprinting, and set it to true. It overrides font visibility to Level 1 and changes other surfaces, so expect site breakage. Test key sites and keep a separate profile for anything that fails.
What do the font-visibility levels mean?
Level 1 exposes base OS fonts, Level 2 adds language-pack fonts, and Level 3 exposes all local fonts. Firefox applies them per context through the standard, private and trackingprotection preferences. RFP ignores those preferences and uses Level 1.
Can sites still see my installed fonts in private browsing?
They see the restricted set that the private-context preference allows, not necessarily your full installed list. Remote web fonts still load, and canvas or metric tests can still gather rendering signals. Private browsing is a restriction, not a blank font list.
Does clearing cookies change my font fingerprint?
No. Fonts, font metrics and canvas rendering are tied to the browser and operating system, not to cookies. Clearing cookies removes state but leaves the font signal stable unless you change the font visibility level or the underlying system fonts.
Will Resist Fingerprinting break websites?
It can. RFP changes fonts and other browser surfaces, and Mozilla warns that it can cause odd behaviour. Start with Strict ETP or a private window, then enable RFP only for profiles where you can tolerate breakage.
What does font.system.whitelist do?
It is a hidden preference from Firefox 81 that takes a comma-delimited list of font names and overrides font visibility. You can use it to keep specific fonts visible with RFP on, but every added family increases entropy. Add only what you need and test.
How Send.win Helps With Font Fingerprinting Firefox
Send.win is a browser profile manager for professionals and teams: every account gets its own isolated browser profile.
- Isolated profiles – separate cookies, storage and sessions per profile
- Fingerprint protection – each profile keeps its own consistent browser fingerprint, so profiles never share one browser identity
- Desktop app + cloud browser – native app for Windows, macOS and Linux, or run profiles in the cloud with no install
- Residential proxies included – on Pro and Team, with timezone and locale matched to the proxy
- Team sharing – share a signed-in profile with a teammate without sharing the password
Try the free cloud demo — no install — or download the desktop app. Paid plans start at $19/month, and your first card purchase is covered by a 7-day money-back guarantee (see pricing).