You can also enforce most of these settings in all profiles with a policy: https://github.com/mozilla/policy-templates
In Firefox Profilemakermozilla
policy-templates
Python2018–2026
mozilla / policy-templates
policy-templates
Policy Templates for Firefox
32Distinct people
32Mentions
1Explicit recommenders
1.3KGitHub stars
What to know before exploring
What it is
Policy Templates for Firefox
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
They very well could do this for a company that requires really strict privacy and security, but unfortunately in its current state Firefox doesn't have nearly the corporate…
4oo4 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:59:58 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year32 dated mentions
Observed mentions: 2018-06-21 03:24:05 UTC to 2026-10-13 18:49:05 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Firefox Policy Templates
NoteThese policies are in active development and may contain changes that do not work with current versions of Firefox.
Use the officially released versions if you are deploying changes.
This repository contains policy templates to support deploying and managing Firefox as an enterprise browser.
Firefox policies allow administrators to centrally manage browser behavior, enforce security requirements, configure features, or disable certain functionality.
Policies are commonly used in enterprise or managed environments such as businesses, schools, and public-sector organizations.
Policy documentation
WarningDocumentation for policy behavior and syntax is moving to Firefox Admin Docs.
The new docs repository is public and open to contributions, so if you want to make improvements, feel free to contribute at https://github.com/mozilla/enterprise-admin-reference.
See the GitHub Discussion for more information.
Read the full README on GitHubWhat Hacker News says
8 sources(Disclaimer: I work on the Firefox Application Update system)
> But let me opt out
It seems to me that you can opt out. You can use the "Check for updates but let you choose to install them" setting in `about:preferences`. Or you can use the exact policy currently under discussion: `DisableAppUpdate`. Or there is another policy called `ManualAppUpdateOnly` [0].
> (Mozilla, are you listening?)
Why yes, we are listening. We have heard many people request the ability to disable automatic updates, which is why we have the options that I mentioned above. If you feel that these options don't meet your needs, we would really appreciate you filing a bug [1]. We will get to it fastest if you put it in the correct component (which for this issue is `Toolkit::Application Update`).
> for the love of god please don't override my preferences back to au
Read the rest
tomatic updates when you decide to change the UI of preferences.
I'm guessing that you are referring to when we removed the "Never install updates" setting [2]? This wasn't fundamentally a UI change. We had several good reasons to remove the underlying pref. Naturally, that meant that the UI for that pref went away as well. I won't spend a lot of time getting into our reasoning here, but we would be happy to discuss it with you if you want to chat with us about it. You can find us in the `#install-update:mozilla.org` channel on https://chat.mozilla.org
[0] https://github.com/mozilla/policy-templates/#manualappupdate...
[1] https://bugzilla.mozilla.org/home
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1420514
I think you can also do it with an enterprise policy flag
https://github.com/mozilla/policy-templates/blob/master/READ...
In Google sets burial date for legacy Chrome Extensions, fears for ad-blockers growYou can create a policies.json file with these contents:
{
"policies": {
"DisableAppUpdate": true
}
}
Place it in the platform specific place:
"On Windows, create a directory called distribution where the EXE is located and place the file there. On Mac, the file goes into Firefox.app/Contents/Resources/distribution. On Linux, the file goes into firefox/distribution, where firefox is the installation directory for firefox, which varies by distribution or you can specify system-wide policy by placing the file in /etc/firefox/policies."
from https://github.com/mozilla/policy-templates/blob/master/READ...
EDIT: alternatively, you can install the ESR version for 91, use the userchrome link in the sibling comment, and forget about it for 18 months, wich is what I'm currently doing. And good thing too, apparently 92 broke some
Read the rest
UI again, because of course it did.
DoH is configurable with GP or just a policies.json file if you want: https://github.com/mozilla/policy-templates/blob/master/READ...
In Mozilla rolls out DoH to Canadian users of FirefoxThere's a windows GPO key[0] and a canary domain[1] you can NXDOMAIN (use-application-dns.net). Both of these only control the default (it won't override a user personally choosing the setting).
[0]: https://github.com/mozilla/policy-templates/blob/master/READ...
[1]: https://support.mozilla.org/en-US/kb/canary-domain-use-appli...
In Mozilla rolls out DoH to Canadian users of Firefox