I have a love-hate relationship with exactly one page in my browser. It’s Firefox about:config, the hidden settings page where I can customize almost everything, and break almost everything.
My take up front: about:config is the best reason to use Firefox and the worst place to follow random internet advice. Both are true. This post covers the tweaks worth making, the ones that bite, and how to undo the damage.
What Firefox about:config Is
Type about:config into the address bar and press Enter. Firefox shows a page titled “Proceed with Caution” with a button that reads “Accept the Risk and Continue.” That’s the most honest button in software.
Behind it is a searchable list of preferences, or prefs. A pref is a named setting with a value: true or false, a number, or a piece of text. The normal Settings page shows the handful Mozilla thinks you need. This page shows the rest.
Mozilla’s own Configuration Editor guide says changes here “can have serious effects on your browser’s stability, security and performance.” Believe it.
Chrome has chrome://flags, but that’s a list of experiments Google is testing. about:config goes further and exposes nearly every setting the browser has.
Why I Love It
It treats me like an adult. If a behavior annoys me, I don’t need an extension or a feature request. I search for the pref and flip it. It’s the philosophy behind KDE Plasma, which I compared with GNOME: the software adapts to you.
These tweaks are safe, useful, and still real. Every pref in this table is live in Firefox as of October 2026.
| Preference | Set it to | What you get |
|---|---|---|
browser.tabs.closeWindowWithLastTab | false | Closing the last tab no longer closes the whole window |
browser.download.alwaysOpenPanel | false | The downloads panel stops popping open on every download |
browser.tabs.insertAfterCurrent | true | Every new tab opens next to the current one, not at the far end |
browser.urlbar.trimURLs | false | The address bar shows the full address, http:// included |
browser.compactmode.show | true | Brings back the Compact option for toolbar density |
toolkit.legacyUserProfileCustomizations.stylesheets | true | Lets Firefox load userChrome.css, a file of custom styles for the browser’s own interface |
My own setup is less hand-made than that table. I use Betterfox, a ready-made user.js. That’s a text file in your Firefox profile that applies a whole list of prefs every time the browser starts. I run it for performance.
It’s the opposite of a random tweak list. It’s maintained and documented, and its install steps start with a profile backup. It’s still someone else’s choices applied to your browser, so skim what it changes.
It’s also where control shows up first. Before February 2026, the usual advice for switching off Firefox’s AI features was a list of browser.ml prefs in about:config. Firefox 148 turned that into one switch in Settings called Block AI enhancements. The tinkerers got there early, and everyone else got the checkbox later.
Pro Tip: Tick Show only modified preferences next to the search box. You get a short list of everything you’ve ever changed, shown in bold, each with a Reset button. Screenshot that list before a big Firefox update.
Why I Hate It
No labels, no warnings
Each row is a name and a value. Nothing tells you what browser.sessionstore.max_serialize_back does, what the safe range is, or what else depends on it.
Pref names are case-sensitive. Search for one that doesn’t exist and Firefox offers to create it, then stores your made-up setting without complaint. A typo gets you a pref that does nothing, and no error to tell you so.
Some tweaks really do break things
The classic is privacy.resistFingerprinting. Fingerprinting is when sites identify you by your device’s quirks, like screen size and installed fonts, so switching on resistance sounds like free privacy. Mozilla’s Resist Fingerprinting page lists what comes with it:
- Times shown in the wrong time zone
- Sites that ignore your dark mode setting
- Pages that load in English whatever your language
- Gamepads that stop working
- Random lines across images you edit in the browser
Mozilla says it doesn’t recommend the pref for the average user. A comment in Firefox’s own source code calls it a “not-recommended footgun.” For most people, the fingerprinting protection in the regular Settings page is the right choice. If you want the full treatment, use a browser built for it, like Mullvad Browser from my privacy browsers post.
Then there’s layout.css.devPixelsPerPx, which scales the whole interface. A wrong value makes everything too tiny or too huge to use, including the about:config page you’d need to fix it.
The sneakiest damage shows up late. You flip a pref, forget about it, and three weeks later a site misbehaves. You blame the site.
Mozilla doesn’t support it, and prefs disappear
Mozilla’s page on advanced customization is blunt. It doesn’t officially support changing prefs in about:config, it recommends the page only for developers, and it can’t promise that an update won’t break your tweak.
That’s why so many “ultimate about:config tweaks” lists are placebo. network.http.pipelining starred in “speed up Firefox” guides for years. Mozilla removed pipelining in Firefox 54, back in 2017, and the guides are still out there.
A quick test: search for the pref. If Firefox only offers to create it, that’s a strong hint the tweak is dead. A few real hidden prefs do have to be created by hand, so check the date on the guide too.
How to Undo a Bad Tweak
- Reset the one pref. Open about:config, tick Show only modified preferences, and click Reset on the suspect.
- Reset all prefs. Type
about:supportin the address bar and open your profile folder from there. Quit Firefox, then renameprefs.jstoprefs.jsOLD. Do the same withuser.jsif you have one. That’s an optional file some people use to reapply their tweaks at every start. Bookmarks, history, and passwords live in other files. - Last resort: Refresh Firefox. The button is on the same
about:supportpage. It resets your settings and removes extensions and themes, and it keeps essentials like bookmarks and passwords.
If Firefox is too broken to open, Mozilla’s help site explains how to find the profile folder without it.
My Rules for about:config
- Change one pref at a time, and write down what you changed.
- Skip any tweak list older than a year.
- If Settings has a switch for it, use the switch.
- Leave anything starting with
security.alone unless you can explain what it does. - Never paste in someone else’s whole
user.jswithout reading it.
The Verdict
I’m keeping it. about:config lets me own my browser instead of renting it, and Chrome, Edge, and Safari have nothing like it.
I hate it for the same reason I love it: it trusts me completely, including when I’m wrong.
Treat it like the engine bay of your car. Open it when you know which part you’re after, change one thing, and close the hood.
Frequently Asked Questions
Is Firefox about:config safe to use?
Looking is safe. Changing things is at your own risk: Mozilla doesn’t officially support edits made there. Stick to prefs you understand and change one at a time.
How do I reset about:config to default?
Reset a single pref with its Reset button. To reset everything, quit Firefox and rename prefs.js in your profile folder, or use Refresh Firefox on the about:support page.
Why doesn’t an about:config tweak I found online work?
The pref was probably removed. Mozilla deletes prefs as Firefox changes, and old guides keep recommending them. If searching for the name only offers to create it, the tweak is likely dead.
Do about:config changes survive Firefox updates?
Usually. Your changes are saved in your profile, so they carry over. They stop working when Mozilla removes or renames the pref behind them.
