Mozilla's index lists 160.0 as the desktop stable release as of November 12, 2026, with a November 10 release date. This guide covers everyday Firefox on Windows, macOS and Linux. Confirm your version and profile before changing settings.
Check your version and define the goal
On desktop, use Menu → Help → About Firefox to check the version, or open about:support to see the version and update channel. Mozilla also lists 153.7.0esr, plus a 115.45.0esr branch for older systems. ESR, Linux packages and managed installations may expose different interfaces or policies. Some newer layouts give permissions, data and autofill their own pages. Search Settings for Location, DNS over HTTPS or Passwords when the navigation differs.
Mozilla version index · Firefox 160.0 release notes · Firefox release branch settings strings
Identify who would receive the information. Embedded analytics can combine cross-site state and device signals. A service can identify its signed-in account. Local traces matter to the next person using the machine. The internet provider, VPN and destination each see different parts of a connection. Choose a concrete goal, such as limiting cross-site cookies on news sites or removing a persistent microphone grant.
Choose a tracking protection preset
Open Settings → Privacy & Security → Enhanced Tracking Protection (ETP). Start with Standard. The address-bar shield shows the current site's protection and exceptions. Total Cookie Protection (TCP) partitions cookie state by top-level site so an embedded service has separate storage in different sites. A site can still maintain its own login, and Firefox includes compatibility handling.
Mozilla Enhanced Tracking Protection · Firefox tracking protection matrix
| Preset or mechanism | Effect | What to check |
|---|---|---|
| Standard in a regular window | Known-fingerprinter blocking and TCP are among the default protections, with more room for embedded content to work | Open a news site and a login page and inspect the shield |
| Standard in a private window | Adds tracking-content and suspected-fingerprinter protection, with temporary private session data | Sign in to a test account, close all private windows and check the session again |
| Strict | Stronger blocking and signal protection in regular and private windows | Test federated login, checkout, comments and embedded video |
| Custom | Individual controls for tracking content, cookies and known or suspected fingerprinters | Record each choice and change one at a time |
| TCP | Partitions cookie state by top-level site, reducing reuse of the same third-party cookie across sites | Cross-site authentication may still need narrowly scoped exceptions |
Mozilla Enhanced Tracking Protection · Firefox tracking protection matrix · Mozilla fingerprinting protection · Mozilla Private Browsing
If Strict breaks something, check for Fix major site issues and Fix minor site issues in your build. These compatibility controls allow relevant resources to load. Validate them against the task. For a trusted site, temporarily turn off its shield, reload and reproduce the issue. Re-enable it and check the exceptions list after testing. Record whether the break occurred during the sign-in redirect, embedded playback or payment submission.
Mozilla Enhanced Tracking Protection · Firefox release branch settings strings
Global Privacy Control (GPC) communicates a preference against the sale or sharing of data. The recipient and applicable rules affect what happens next. Inspect actual shield actions and GPC independently. The PPA experiment described in older guides was removed. For sponsored placements or recommendations, inspect the Home or new-tab settings separately.
Mozilla Global Privacy Control · Firefox release branch settings strings · Mozilla PPA historical documentation
Understand the four fingerprinting layers
Fingerprints can combine language, time zone, window dimensions, graphics, fonts and capabilities. Known-fingerprinter blocking matches resources against a list. Fingerprinting Protection (FPP) limits or changes what a page can read, including standardization and randomization of some signals, even when the script loads. Mozilla's settings matrix separates regular Standard browsing from Standard private browsing and Strict. Baseline protections can still apply in a regular Standard window.
Firefox tracking protection matrix · Mozilla fingerprinting protection · Mozilla November 10 fingerprinting research
Resist Fingerprinting (RFP) is the advanced privacy.resistFingerprinting preference in about:config. Mozilla describes possible changes to time zones, visuals and site behavior. Keep the original value in your daily profile. If you have a compatibility question, note the original value in a separate test profile and observe a single change. Use the reset control for the default, or restore the recorded value if it was already customized. Follow mobile documentation for mobile settings.
Mozilla's November 10, 2026 study uses aggregate data from almost 25 million Firefox users and estimates effects under three modeled fingerprinting services. Some evaluated protections had already shipped in Firefox 145, with further changes in later versions. The estimates exclude gains from randomization and have a different scope from a local test. Desktop 160 moved macOS WebGL to Metal. Treat the browser version as a variable when graphics results change across an update.
Firefox 160.0 release notes · Mozilla November 10 fingerprinting research
The paper weights four operating system populations and models three fingerprinting services on its measurement sample. The percentages are the estimated shares classified as unique under each model. The result after cumulative protections depends on the signals the model uses. For a personal reading, first check the operating system, browser version and test population.
| Modeled service | Unique at baseline | After cumulative protections |
|---|---|---|
| Fingerprint Pro | 75.7% | 46.8% |
| Signifyd | 60.9% | 38.5% |
| Akamai | 18.2% | 9.0% |
Manage cookies, history and private windows
Search Settings for Cookies and Site Data, Browsing data or History. Start with the site data manager and locate the relevant domain. Removing data for one site can end the session and discard offline content or a local draft. Save work before clearing. In a test profile, choose which categories to clear on exit and record any site exceptions you actually need.
Mozilla site data controls · Mozilla history clearing · Firefox release branch settings strings
| Control | Effect | Cost |
|---|---|---|
| Manage site data | Remove cookies or storage by domain | Signs you out and can remove offline data |
| History and clearing on exit | Choose whether Firefox remembers browsing, download, search and form history | Deletion is irreversible and downloaded files remain on disk |
| New private window | Clears temporary session data after all private windows close | Bookmarks and downloads can remain, and websites still see sign-ins and connections |
| Cookie exceptions | Allow or restrict storage for particular domains | Broad exceptions reduce isolation or cleanup |
Mozilla site data controls · Mozilla history clearing · Mozilla Private Browsing
Review passwords, autofill and Sync
Search for Passwords or open Passwords and autofill. Review credential saving, automatic filling, strong-password suggestions and breach alerts separately. If you disable autofill, inspect saved entries separately in the password manager. Use separate operating-system accounts on shared machines. Where available, consider device authentication or a Firefox Primary Password and safeguard the information needed for recovery. Address and card autofill vary with region and build. Inspect saved entries and the visible save and fill controls.
Mozilla password manager · Firefox release branch settings strings · Mozilla Primary Password
Under Mozilla account → Sync settings, inspect categories such as bookmarks, history, open tabs, passwords, add-ons and settings. Select the categories you need across devices. Turning off Sync, signing out of Mozilla, signing out of a site and deleting records from a site's servers are separate operations. Check data already synced or retained on other devices individually. Run fingerprint tests in a fresh, signed-out profile to avoid restoring extensions or settings.
Audit site permissions and location
Open Settings → Privacy & Security or Permissions and data → Permissions and open the Location settings. Remove obsolete Allow entries. To deny new requests by default, enable the option to block new requests for your location. For a mapping task, grant access when needed and revoke it afterward. A site can still infer a location from your connection IP, account region or a saved address. Review the operating-system location grant for Firefox separately.
Mozilla location permissions · Firefox release branch settings strings
| Permission | Action | Trade-off |
|---|---|---|
| Camera and microphone | Remove unused grants and allow meeting sites when needed | Calls may prompt again |
| Notifications | Revoke unfamiliar sites and block new prompts if appropriate | You may miss site alerts |
| Autoplay | Start by restricting audio autoplay, with exceptions for specific sites | Some videos need a click to play |
| Pop-ups and third-party redirects, extension installation warnings | Keep protections enabled and restrict necessary exceptions to specific sites | Checkout or work sign-in may need a one-site exception |
| Device apps and services, local network devices | Where offered, review saved grants and deny requests from unfamiliar sites | Printers, casting and companion apps can require access |
| Speaker, virtual reality and other visible controls | Review saved choices by site and device | External audio or XR may require a new permission |
| App link requests (Firefox 160) | When a website asks to handle app links such as mailto:, choose Never allow if shown to block future requests from that site. Where the new Permissions and data → Permissions panel offers Allow sites to ask to open app links, unchecking it blocks these requests for all sites. | To undo a site block, enable the global request setting, then remove the site in Manage blocked sites and save. It can ask again. Blocking requests globally can affect webmail and other app integrations. |
Mozilla location permissions · Mozilla device and local network permissions · Firefox release branch settings strings · Firefox 160.0 release notes
Review diagnostic data, HTTPS and security
Read each item under Firefox Data Collection and Use in Permissions and data or Privacy & Security. Technical and interaction data helps improve the browser. Studies run experiments. Crash reports support troubleshooting and may include sensitive information. Some builds also offer a daily usage ping or remotely delivered improvements. Decide separately based on the controls in your build. Updates, Sync and website requests have their own purposes and controls.
Mozilla data collection settings · Firefox release branch settings strings
Search for HTTPS-Only Mode and choose all windows or private windows. An older HTTP-only site can trigger a prompt before continuing. For certificate errors, check the domain, clock and organizational guidance. Keep protections against phishing, dangerous downloads and unusual software enabled. Your organization may manage certificates or security devices. Adjusting privacy settings does not require importing unfamiliar root certificates.
Mozilla HTTPS-Only Mode · Mozilla deceptive content protection · Firefox release branch settings strings
Separate DoH, the public IP and WebRTC
Search for DNS over HTTPS and open Advanced settings if it is present. DoH protects applicable queries between the browser and its resolver. Websites still see the IP of the connection that reaches them. Work domains, captive portals and VPNs can require a particular DNS path. Before changing a mode, record the provider, status and exceptions. Not active can reflect network detection or a resolver failure. Compare it with the intended resolver and route.
| Mode | Browser behavior | What to verify |
|---|---|---|
| Default | Enables DoH where available and can fall back. VPN detection, parental controls or enterprise policies can suppress it | Check the resolver against network requirements |
| Increased | Prefers the selected provider and can fall back if it fails | Confirm acceptable fallback behavior |
| Max | Warns if secure resolution fails or returns no address, with optional domain exceptions for system DNS | Verify work and internal domains |
| Custom, where shown | Uses the selected provider and can be set to always warn if secure DNS is unavailable | Check the warning setting and exceptions |
| Off | Uses the default resolver | System or VPN settings can determine the resolver |
For a route test, check the HTTPS egress category at the same trusted endpoint, then examine WebRTC ICE candidates. MDN documents how candidate addresses may reveal network information. A private address or mDNS hostname, a public reflexive candidate and a TURN relay are distinct signals. Compare them with the intended IPv4 and IPv6 paths. Camera and microphone denial controls device access. A third-party WebRTC test receives your test connection, so choose whether to use it. Check a real call in an environment you control, then restore the original settings.
Use the controls for your platform
On Android, open the three-dot menu → Settings → Privacy and Security → Enhanced Tracking Protection. The site shield controls exceptions in Mozilla's current instructions. On iOS and iPadOS, open Menu → Settings → Tracking Protection. Mozilla documents Standard and Strict there. Also review location in the phone's operating-system settings. Use the app's own help for networking, clearing data and private tabs, since desktop preferences, profile management and extension steps can differ.
Mozilla Android tracking protection · Mozilla iOS tracking protection
This guide uses the public desktop stable documentation. Managed installations can lock controls. Record both browser and OS versions and look for organization management in the interface. Follow your administrator's guidance for workplace certificates, sign-on and DNS policy. Updates to either the browser or the OS can affect measurement results.
Mozilla version index · Firefox 160.0 release notes · Firefox release branch settings strings
Interpret community reports and independent tests
In an August 2026 r/firefox thread, a user reported that EFF still detected a fingerprint after choosing Strict or Custom. The post documents that experience. It lacks a replayable record of the device, previous configuration and site coverage. If comments suggest several changes, isolate one variable in a test profile.
TweakTown published a comparison on one Windows 11 laptop on October 6, 2026. The Firefox version was 157.0. In a private window, the observed thread count moved from 12 to 8 and font signals changed, while EFF still reported a unique fingerprint. Mozilla Bugzilla 1937096 records a separate OffscreenCanvas font-protection gap marked fixed in Firefox 144. Historical defects help identify dimensions worth testing.
EFF Cover Your Tracks methods · Mozilla Bugzilla 1937096 · TweakTown single-device comparison
Read EFF's simulated tracker results and fingerprint rarity separately. Its sample, time period, observed features and combination method affect the result. Some signals can change while the combination remains unusual. Three identical hashes show stability for that reading under those conditions. Separate tests are needed across sites, restarts, account states and different signal sets.
Mozilla November 10 fingerprinting research · EFF Cover Your Tracks methods
Run a repeatable single-variable experiment
Open about:profiles and create and launch a blank profile. Leave Mozilla Sync disconnected and avoid installing extensions. Hold browser version, OS, window size, zoom, network and the test page constant. Save work in your daily profile first. This is an experiment protocol with synthetic example data. Actual measurements come from your own device.
- Use a regular Standard window for A. Run the same page three times. Record prompts, missing values, stable values and changed values.
- For B, change only ETP to Strict, reload the same page and repeat three times. If needed, verify login and video with a recoverable test account.
- Return to Standard and repeat A. If the change follows the setting in both directions, describe it as an observation for that version and page.
- Compare private browsing in a separate run. For cross-site randomization, use the same script on two origins you control, holding other conditions constant. Reopening one URL only repeats the same site.
- If checking the public network, record HTTP egress, DNS resolver and WebRTC candidate types separately. Keep address categories and whether they match expectations. Omit real IPs, fingerprint hashes and account screenshots from a public report.
run,version,os,window,etp,network,signal,result
A1,160.0,example,normal,standard,same,canvas,hash-a
B1,160.0,example,normal,strict,same,canvas,hash-b
A2,160.0,example,normal,standard,same,canvas,hash-aExternal tests are optional. EFF measures browser signals and a WebRTC test site receives your connection. A public write-up should include the date, version, window type, protection mode and replay steps without identifying results. Mark a failed reading as unavailable. An empty result covers only the attempted measurement.
Compare browser signals locally
Keep the version, profile, address and window size fixed. Measure twice with the original settings to see which readings vary on their own, then set one as baseline A. Change one setting and measure B. If you need another window or a restart, paste the JSON for A into the comparison field and record the window change as a variable.
The tool compares language, time zone, screen and viewport size, pixel ratio, logical processor hints, low entropy UA-CH, WebGL capability and a digest of a fixed Canvas drawing. A match means the readings agreed in those runs. A change, missing value or failed read needs the browser version, environment and setting for context. Use the same downloaded HTML file for both runs to test offline. API availability can differ between HTTPS and a local file.
Diagnose extensions and restore narrow exceptions
Open about:addons to inspect permissions and access in private windows. Temporarily disable a new or suspect extension, reload the same task and restore extensions individually. Firefox Troubleshoot Mode can temporarily disable extensions and other components. If several variables changed during that test, isolate the cause after returning to normal mode. Preserve the daily profile and its data. Reproduce in a test profile before considering a browser reset.
Mozilla extension permissions · Mozilla profile management · Mozilla Troubleshoot Mode
After testing, restore the recorded ETP, DoH and RFP values and remove experimental permission, cookie, DNS and shield exceptions. Changing a setting cannot recover history or storage already deleted. Before making a payment, recheck navigation and prompts. If you cannot validate the experimental setup, use the known working profile and retain only the minimal steps needed for diagnosis.
Mozilla Enhanced Tracking Protection · Mozilla Resist Fingerprinting · Mozilla site data controls · Mozilla DoH modes
Repeat the same checks after changes
Keep a configuration that meets your privacy goals and passes daily tasks. Repeat the relevant checks after a browser update, device change or network switch.
- Record the version, network and original settings
- Write down the steps to reproduce the task
- Change one item and retest
- Verify daily tasks
- Restore or keep the setting and record any exception
Standard, a short permission list and a few necessary extensions are a starting point. When a new risk or compatibility problem arises, reproduce one specific behavior, compare the result and restore as needed.