How to Use the Mozilla Preference Knife to Tweak Browser SettingsThe “Mozilla Preference Knife” is a figurative name often used to describe tools and techniques for locating, inspecting, and modifying Firefox’s internal preferences. These preferences control everything from visual behavior to privacy features and experimental flags. This guide explains where preferences live, how to safely change them, practical examples of useful tweaks, troubleshooting, and best practices for maintaining a stable browser.
What are Firefox preferences?
Firefox stores configuration options called preferences. They determine browser behavior and can be set at several levels:
- User preferences — set by the user and stored in your profile (user.js or prefs.js).
- Default preferences — shipped with the browser and used unless overridden.
- Locked or enterprise preferences — enforced by organization policies.
Preferences use names like browser.urlbar.autocomplete.enabled or network.dns.disablePrefetch and accept values of types: boolean, integer, or string.
Where to find and edit preferences (the “knife” toolkit)
There are multiple ways to view and change Firefox preferences — the tools that form the “Preference Knife”:
- about:config (primary tool)
- Enter about:config in the address bar and accept the risk prompt.
- Use the search box to find a preference by name or fragment.
- Double-click a preference to toggle booleans or edit values; right-click for more options (reset, copy name).
- user.js and prefs.js (profile files)
- Your profile folder contains prefs.js (active runtime preferences) and can include user.js (user overrides applied at startup).
- To persist manual changes across sessions, create or edit user.js with lines like:
user_pref("browser.urlbar.autocomplete.enabled", false); user_pref("network.http.referer.spoofSource", true); - Never edit prefs.js while Firefox is running; changes will be overwritten.
- Enterprise policies (policies.json)
- Administrators can enforce preferences via policies.json in the distribution folder or by using Group Policy on Windows. These can lock settings so users cannot change them.
- Extensions and about:profiles
- Some extensions expose preference-like settings; about:profiles helps locate the active profile folder for file edits.
Safety first — best practices before editing
- Backup your profile folder (especially prefs.js and bookmarks) before making many changes.
- Make one change at a time and restart Firefox if needed to observe effects.
- For temporary experimentation, change values via about:config rather than editing files.
- Use user.js only if you want persistent overrides; otherwise prefer about:config.
- Avoid changing unknown preferences without research; some can break features or security.
Useful preference tweaks (examples)
Below are practical tweaks categorized by purpose. For each, the preference name and recommended value are shown. Use about:config to change them or add to user.js for persistence.
Privacy & tracking
- browser.urlbar.suggest.searches — false (turn off search suggestions in the address bar)
- network.dns.disablePrefetch — true (disable DNS prefetching to reduce unsolicited DNS lookups)
- privacy.firstparty.isolate — true (enables strict first-party isolation to reduce cross-site tracking)
Performance
- image.mem.decode_on_draw — true (may improve responsiveness when loading many images)
- browser.tabs.animate — false (disable tab animations to reduce CPU/GPU use)
- extensions.webextensions.restrictedDomains — (leave default unless testing specific extension sandboxing)
UI & usability
- browser.urlbar.trimURLs — false (show full URLs in the address bar)
- browser.tabs.closeWindowWithLastTab — false (prevent window closing when last tab is closed)
- layout.spellcheckDefault — 2 (enable spellcheck in multi-line and single-line inputs)
Developer & experimental
- devtools.chrome.enabled — true (allow developer tools to inspect browser UI)
- browser.cache.disk.enable — false (disable disk cache for development testing)
- dom.webnotifications.enabled — false (disable web notifications globally)
Security
- security.ssl.require_safe_negotiation — true (reject unsafe TLS/SSL handshakes)
- privacy.resistFingerprinting — true (enable anti-fingerprinting measures)
Notes: Some preferences may be renamed or removed between Firefox versions; verify before applying.
Advanced techniques
- Combining user.js with scripts: power users maintain a version-controlled user.js that they apply across profiles or machines.
- Finding hidden flags: search about:config for keywords, or consult Mozilla bugzilla / documentation to learn what a pref controls.
- Conditional preferences: use policies.json to enforce settings on specific installations in enterprises.
- Temporary experiments: use a dedicated profile created via about:profiles for testing so your main profile remains unchanged.
Troubleshooting
Problem: Browser crashes or wonky behavior after changes
- Start Firefox in Troubleshoot Mode (Help → Troubleshoot Mode) to see if extensions or modified prefs are causing issues.
- Reset a specific pref in about:config (right-click → Reset) or remove entries from user.js and restart.
- If Firefox won’t start, restore prefs.js from a backup or create a clean profile and migrate bookmarks.
Problem: Preference keeps resetting
- Check for user.js or enterprise policies overriding your change.
- Some preferences are controlled by extensions; disable extensions to test.
Problem: I can’t find a preference name
- Names can change; search partial strings in about:config or look up the setting in Mozilla’s support pages or source code.
When not to use the Preference Knife
- Avoid changing preferences to “fix” webpages that are broken; site issues are often best fixed by reports to site owners or use of extensions designed for that purpose.
- Don’t disable security-related prefs unless you clearly understand the risk.
- For sharing preferences across many users, prefer managed policies over personal manual edits.
Example workflow: safely enabling a privacy tweak
- Backup profile.
- Open about:config and search for privacy.firstparty.isolate.
- If found, double-click to set to true. If not found, add it via right-click → New → Boolean → name → true.
- Restart the browser and visit a few sites to confirm behavior.
- If satisfied, add user_pref(“privacy.firstparty.isolate”, true); to user.js to persist the choice.
Further resources
- about:config help pages in Mozilla Support.
- Mozilla developer docs and preference lists.
- Community forums and Bugzilla for in-depth discussions of specific preferences.
Summary
- The “Mozilla Preference Knife” is about knowing where preferences live and using the right tools (about:config, user.js, policies) carefully. Back up, change one thing at a time, and prefer documented prefs to avoid surprises.
Leave a Reply