Advice Request Which Firefox "about:config" setting would you suggest adjusting?

Please provide comments and solutions that are helpful to the author of this topic.
Rather than using browsers based on Firefox (for security reasons), I want to modify Firefox. Which Firefox about:config setting would you recommend changing for speed and privacy?

Thank you.
If your goal is “modify Firefox instead of switching browsers,” the safest approach is to focus on (1) privacy hardening that does not weaken security and (2) avoiding “speed tweaks” that often do little or can backfire. Most meaningful performance gains come from extensions, content blocking, and keeping Firefox lean—not from changing obscure networking limits.

Best single about:config privacy setting (high impact, with trade-offs)
  • privacy.resistFingerprinting = true
This is Firefox’s main built-in anti-fingerprinting switch. It meaningfully improves privacy against tracking via browser fingerprinting, but it can also cause website quirks (time zone/locale behavior, some canvas/WebGL behaviors, some site compatibility issues). It’s a solid “one setting” recommendation if privacy is the priority and you can tolerate occasional breakage.

Privacy settings I’d change before “speed tweaks” (generally safe)
  • Disable telemetry (privacy, not speed)
    • toolkit.telemetry.enabled = false
    • datareporting.policy.dataSubmissionEnabled = false
    • datareporting.healthreport.uploadEnabled = false
  • Reduce connection “leaks” (minor privacy gain, may slightly reduce convenience/performance)
    • network.prefetch-next = false
    • network.dns.disablePrefetch = true
    • network.http.speculative-parallel-limit = 0
  • WebRTC (prevents direct IP exposure in some scenarios, but breaks WebRTC calling)
    • media.peerconnection.enabled = false
    Only do this if you do not use browser-based voice/video (Meet, Teams in browser, Discord in browser, etc.).

DNS-over-HTTPS (privacy depends on provider; not automatically “more secure”)
If you want to use DoH, the key pref is:
  • network.trr.mode
However, whether this is a privacy improvement depends heavily on which resolver you use and your threat model. If you change this, also review Firefox’s DoH UI settings so you know which provider is used. I would not recommend random DoH changes purely as a “security” tweak without understanding the trade-off (you’re moving DNS visibility from your ISP/network to a DoH provider).

About speed: what I’d recommend (and what I would not)
Meaningful, low-risk “speed” wins from about:config are uncommon today. Many popular “speed tweak” lists change connection limits/caches in ways that can reduce stability, increase memory use, or even slow real browsing.

What actually tends to help performance without risky tweaking:
  • Use a reputable content blocker (commonly, uBlock Origin) to reduce script/ad load (often the biggest speed win).
  • Keep extensions minimal (each extension can add overhead).
  • Leave Firefox’s networking and cache defaults alone unless you have a specific problem you’re solving.

Conclusion
If you change only one about:config key for privacy, use privacy.resistFingerprinting = true and accept potential site quirks. For “speed,” avoid about:config tweak lists; focus on content blocking and a clean extension set instead.

Sources
 
I'm using these:

browser.compactmode.show set to true — enables compact mode; makes tabs, navigation keys and address bar more compact like it was before everything got big spacing for touch compatibility

browser.translations.enable set to false — disables Firefox Translate entirely; it's terrible for Croatian and I simply have no use for it (using TWP add-on instead)

urlclassifier.trackingSkipURLs & urlclassifier.features.socialtracking.skipURLs — exceptions for Firefox ETP; using them to unblock social media embeds on news sites so I don't have to click annoying "allow" button while keeping Strict protection enabled

browser.sessionstore.interval set to 1800000 — reduces writing to SSD, but restoring session won't work great in case Firefox crashes (never happened to me)

media.videocontrols.picture-in-picture.video-toggle.min-video-secs set to 5 — adds ability to open shorter videos in PiP (useful when player doesn't have a seek bar like on Instagram for example so I can fast forward them)

view_source.wrap_long_lines set to true — wraps the code when looking at website source code, so I don't have to scroll sideways when looking something up
 
Last edited:
The advice from the Bot and @Marko :) already covers practically all the essentials (especially regarding telemetry and compact mode). To avoid being redundant, I’ll only add a couple of structural isolation tweaks that are key in 2026 and haven't been mentioned yet:

  • First-Party Isolation (FPI):privacy.firstparty.isolate = trueThis is the same tech used by the Tor Browser. It creates a "wall" between tabs so sites like Facebook or Google can't track your browsing as you jump to other websites. It’s a massive privacy boost.
  • Dynamic Cookie Protection:network.cookie.cookieBehavior = 4This intelligently isolates third-party cookies, preventing them from following you across the web without breaking logins on legitimate sites.
Regarding speed: I agree with the AI Assistant that it’s best not to mess with cache or connection settings (like in post #3). Modern Firefox handles RAM dynamically, and forcing it usually leads to instability or crashes. uBlock Origin remains the #1 "speed" tweak you can have. 🛡️🧱🚀
 
First-Party Isolation (FPI):privacy.firstparty.isolate = trueThis is the same tech used by the Tor Browser. It creates a "wall" between tabs so sites like Facebook or Google can't track your browsing as you jump to other websites. It’s a massive privacy boost.
It is, but it also breaks some websites. Here are the details:
Dynamic Cookie Protection:network.cookie.cookieBehavior = 4This intelligently isolates third-party cookies, preventing them from following you across the web without breaking logins on legitimate sites.
For maximum protection, you should set ETP to Strict. That's all you need to do.
 
Not AFAIK from my experience.

Sorry, I don't rely on @Bot for anything but in this case his advice is reasonable. Nonetheless, I agree with this Firefox power user. Firefox Privacy or: How I Learned to Stop Hardening and Love Strict Tracking Protection
Strict Enhanced Tracking Protection (ETP) generally does not slow Firefox down. In many real-world cases it can do the opposite, because it prevents a lot of third-party scripts/trackers from loading and running.

That said, results depend on what sites you use and your hardware/network.

Does “Strict Tracking Protection” slow down Firefox?
  • Often faster (or feels faster): fewer trackers means fewer requests, less JavaScript, less CPU work, and less page clutter. This is especially noticeable on news sites and ad-heavy pages.
  • Sometimes neutral: on “clean” sites with little tracking, you may not notice any speed difference.
  • Occasionally slower or more broken: if a site relies on blocked scripts, it might keep retrying requests, show placeholders, or require you to allow something. That can feel like “slowness,” but it’s usually site breakage/retries rather than Firefox itself becoming slower.

If your goal is both privacy and smooth browsing, Strict ETP is one of the best “high gain / low drama” options compared to heavy about:config hardening.

Are my earlier recommendations “safe” to implement?
Most are safe in the sense that they do not reduce Firefox’s security, but some can reduce compatibility or convenience. Here’s the practical risk profile:

Generally low-risk (easy to revert, minimal breakage)
  • toolkit.telemetry.enabled = false and related telemetry/reporting prefs: mainly privacy/diagnostics related. Disabling telemetry can reduce Mozilla’s ability to diagnose issues on your install, but it’s not a security risk.
  • network.dns.disablePrefetch = true, network.prefetch-next = false, network.http.speculative-parallel-limit = 0: mostly privacy tweaks. They can make some navigation feel slightly less “snappy” in edge cases because you’re disabling speculative behavior, but they’re typically safe.

High privacy, but can cause site quirks
  • privacy.resistFingerprinting = true: strong anti-fingerprinting, but it can cause visible annoyances or site incompatibilities. Good if you specifically want that trade-off; not ideal if you want maximum compatibility.

Safe, but “feature-breaking” by design
  • media.peerconnection.enabled = false: improves privacy in some scenarios, but breaks browser-based WebRTC calling/meetings and some web apps. Only set it if you are sure you don’t need WebRTC.

DNS-over-HTTPS (DoH): not unsafe, but easy to misconfigure
  • network.trr.mode: whether this is a privacy win depends on your resolver choice and environment (home vs. work/school, parental controls, enterprise DNS, etc.). It can also cause “can’t reach site” issues if your network intercepts/blocks DoH. I would treat DoH as a deliberate choice, not a blanket “security tweak.”

About “cache everything to RAM” and disabling disk cache
This is one of those popular tweaks that sounds good but usually isn’t a clear win:
  • Firefox already uses RAM aggressively when it helps, and it will adapt based on memory pressure.
  • Disabling disk cache can hurt performance on re-visits and can increase network usage.
  • For SSD wear: modern SSDs handle typical browser cache writes fine; reducing writes is rarely necessary unless you have a very specific constraint.

Conclusion
Strict ETP is typically performance-neutral to performance-positive, and it’s one of the safest privacy improvements because it’s designed and tested for mainstream browsing. Most about:config privacy tweaks are “safe” in the security sense, but a few (especially privacy.resistFingerprinting and disabling WebRTC) can introduce compatibility trade-offs, so they should be enabled only if you explicitly want those trade-offs.
 
Again with the useless tweaks and changes, I just check clear data on browser exit, don't save passwords and change search to DDG. Nothing else is needed.

For a more locked down Firefox I use Mullvad browser, I really don't have endless hours to go through about.config line by line for 5% advantage.
 
Again with the useless tweaks and changes, I just check clear data on browser exit, don't save passwords and change search to DDG. Nothing else is needed.

For a more locked down Firefox I use Mullvad browser, I really don't have endless hours to go through about.config line by line for 5% advantage.
I started this thread to gather feedback from members so that I don't waste time. I really tried to like browsers that use Firefox, but each one has its own issues, and generally they don't add anything besides changing the Firefox configuration file. The main issue is that they can be a week or more behind in updating to the newest version of Firefox, so I believe that changing the Firefox configuration file will be the best course of action. 😉
 
But doesn't "Strict Tracking Protection" slow down Firefox? Additionally, are all Bot's recommendations safe to implement?
Not at all. In fact, it even speeds it up because a lot of tracking is blocked before uBlock Origin could react. Browser blocking has priority over extensions.

I wouldn't trust bot. I'll change about:config values only after searching the string on Google and seeing its upsides and downsides.
Indeed, I posted in Site Issues and Feedback and mentioned @Jack . MT is still a bit buggy.
It is really buggy. When I posted first post here, I couldn't see the post logged out, but I could see that I posted in this topic on the front page.
 
But doesn't "Strict Tracking Protection" slow down Firefox? Additionally, are all Bot's recommendations safe to implement?
fwiw earlier today before I saw this thread, chatGPT 5.2 Thinking suggested "Strict Tracking Protection" on a new firefox installation, and I am not seeing any slowdown (among just a few other tweaks) :geek:
 
Last edited:
I use Firefox inside of Sandboxie. Sandboxie puts a line around Firefox so you remember that you are inside of Sandboxie. The line takes away from part of the scrollbar so I wanted to widen the scrollbar.

widget.non-native-theme.scrollbar.size.override
I change this to 30.

widget.non-native-theme.scrollbar.style
I change this to 4

Acadia
 
Usually Wolf updates a day after the main Firefox update often faster, sometimes on the day, I honestly can't see the update times is a reason not to use it, if the odd site don't open in it & there are very few I use Brave, no telemetry with Wolf, Mullvad as mentioned is another solution, but myself I prefer Libre Wolf :)
 
Last edited:
I discovered that the recommendations made by the bot are nearly the default settings in Firefox. toolkit.telemetry.enabled = false is locked, and I have no idea why. Does this apply to every Firefox installation?

Screenshot 2026-03-05 at 22-10-37 Advanced Preferences.png
 

You may also like...