Firefox Strengthens Protection Against Browser Fingerprinting

Mozilla has limited the information that helps websites recognize Firefox users without cookies. The new measures could affect analytics and visitor identification systems.

· 4 min read · 5 comments

Mozilla has strengthened Firefox’s protection against browser fingerprinting. In a November 11, 2026 article, the company says the changes reduce the amount of information scripts can use to distinguish visitors across websites without cookies. Some measures are already enabled by default, while Mozilla is rolling out additional restrictions gradually.

What information the browser now reveals differently

A browser fingerprint is made up of characteristics of the browser and device: available fonts, screen dimensions, graphics hardware, and other properties. Each may seem like an ordinary technical detail, but together they can help identify a browser as someone moves between websites. This kind of tracking does not require a cookie to be stored.

Mozilla examined which characteristics do the most to set users apart. Its research showed that protecting a relatively small number of browser features can significantly weaken common fingerprinting methods. Rather than trying to hide every property, the company focused on differences whose removal has a measurable effect.

For example, Firefox limits the data available through the screen resolution API, making it harder to determine the size and position of the system taskbar or dock. Instead of reporting the exact number of processors, the browser may report 4 or 8. This makes a device’s configuration less useful for identification.

Firefox still provides information websites need to function, including language and time zone. The browser also randomizes some other signals, but the benefit is harder to measure, so they were not included in this study’s results.

What Mozilla measured and when the restrictions apply

To assess the protections, researchers simulated the measurements collected by Fingerprint Pro, Signifyd, and Akamai scripts, then tested how well combinations of that data distinguish users. The study used measurements from nearly 25 million Firefox users. The results are described in a paper accepted for publication at the 2026 Computer and Communications Security (CCS) conference; Mozilla has also prepared a project page and a browser-based test.

While collecting data, Mozilla used OHTTP to separate IP addresses from request contents: neither the intermediary nor the company received both parts together. Access to the telemetry and its retention period were limited. Individual records were deleted several months ago, leaving only aggregated results for publication.

According to Mozilla, the measures studied made fingerprints less precise: fewer users had a unique combination of properties, and groups sharing the same fingerprint grew. The most recent changes evaluated were included in Firefox 145. The research also helped eliminate differences in image rendering, Web Audio, and mathematical operations on Android that had made browsers easier to tell apart.

The protections are not all being introduced at once. Hiding information about the system taskbar, for example, is enabled by default in every mode. Mozilla is rolling out some other measures first in private browsing and with the Strict setting in Enhanced Tracking Protection. To apply the additional restrictions in all Firefox windows, you need to select Strict. If that setting interferes with a website, you can change it. The company has not said when the remaining measures will be enabled by default.

What this means for websites and analytics

Website owners and marketers should distinguish between counting visits and trying to recognize visitors by their browser characteristics. If an analytics or identification system relies on that kind of fingerprint, its results for Firefox users may change: the combinations of properties studied are now less effective at telling one person from another. The published results cannot show how noticeable the effect will be for a particular website.

Developers should check workflows that depend on exact screen resolution, processor count, or other measurable characteristics. Mozilla aims to keep websites working, but testing only in a regular window with default settings is not enough to see how the additional measures behave in private browsing or with Strict enabled.

This does not mean fingerprinting is now impossible: Mozilla acknowledges that fingerprinting methods may change. Firefox has other protections, too, including Total Cookie Protection, which isolates cookie-based identifiers. But the study’s conclusion is narrower: the measures examined make browsers less distinguishable by the selected characteristics.

My take: test real-world workflows

I appreciate an approach that measures whether a protection works while also making sure websites keep working. For a designer, it is a familiar trade-off: reveal less data without breaking the task that brought someone to the page. An elegant privacy model is not much help if a form stops working under strict protection.

I would test changes like these against real-world workflows, especially on mobile: it helps to account for their constraints from the start of a project. I would also discuss an interface’s dependence on browser data with developers, rather than only at the mockup stage. Understanding HTML and CSS helps you spot earlier where a solution relies on a property being precise when the browser no longer guarantees it.

Sources

Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.

  1. Open research, stronger privacy: Making Firefox users harder to fingerprint blog.mozilla.org

About the author

Nataliia Andrushchenko

Lead UX/UI designer

I design interfaces for SaaS products and online stores, and sometimes contribute to design systems. I like testing trendy techniques against real scenarios, not just pretty mockups.

All posts by the author

Leave a comment

Not published. We’ll send a link to confirm your comment.

No links or ads. Your first comment is published after review. By sending a comment you agree to the privacy notice.

  1. One practical wrinkle for e-commerce teams: fingerprint-based bot and fraud tools may also see less stable signals, so check those alongside analytics before treating a drop in visitor recognition as a tracking bug. I’d test checkout and fraud-review flows in Firefox specifically, not just page-view reporting.

    1. I’d be careful about treating less stable fingerprint signals as a likely cause of checkout or fraud-review issues. The article says Mozilla is limiting some identifying details; test those flows, but verify the change before attributing a problem to it.

      1. The distinction is between claiming causation and treating this as a plausible risk worth testing. Mozilla says it is limiting identifying details such as device and browser characteristics; if a fraud tool weights those signals, its decisions could change even if checkout itself remains unaffected. I’d compare Firefox outcomes before and after rollout rather than dismiss the possibility until a problem appears.

        1. Daan, what would you compare before and after rollout to separate a real change in fraud decisions from ordinary traffic variation? For a small team, I’d want a check we can run without buying another analytics tool.

      2. @pieter_r Agreed that the article doesn’t establish a causal link to checkout issues. The useful check is whether a tool depends on the specific signals Mozilla is changing—such as screen dimensions or graphics characteristics—and whether its Firefox behavior changes after rollout; otherwise, a recognition drop is just a symptom to investigate, not evidence of a regression.