How Firefox Releases Work: A Practical Guide

Firefox releases follow a predictable, six-week cycle that moves code from development to millions of users. This guide explains the entire pipeline—from nightly builds to the final public release—so you understand what happens at each stage, how to get pre-release versions, and how to update your own installation.

What You’ll Need

A computer running Windows, macOS, or Linux
An existing Firefox installation (any version) or the ability to download one
A stable internet connection for downloads and updates
Optional: a Mozilla account if you want to use Firefox Sync to keep settings across versions

Step-by-Step

Understand the four main channels. Firefox development uses four parallel branches: Nightly (updated daily, newest features, least stable), Developer Edition (updated weekly, more stable than Nightly, aimed at web developers), Beta (updated every 4 weeks, features are frozen, only bug fixes and polish), and Release (the stable version most people use, updated every 4 weeks). Each channel is a separate installable build, so you can run them side by side.
Know the timeline. A single feature starts in Nightly, where it stays for roughly 12 weeks. After that, it moves to Beta for 4 weeks of stabilization, then lands in the Release channel. This means the entire journey from first code to public release takes about 16 weeks, or roughly three release cycles. The release calendar is public and lists exact dates for each merge and release.
Track the merge points. Every four weeks, the code from Nightly is merged into Beta, and the code from Beta is merged into Release. These merge days are the backbone of the schedule. After a merge, the older branch gets a new version number. For example, when Firefox 128 moves from Beta to Release, Nightly becomes version 130, and Beta becomes version 129.
Download a pre-release version if you want early access. Go to the official Firefox download page and scroll to the “Pre-release versions” section. Choose Nightly for the absolute latest features (expect crashes and broken functionality), Developer Edition for a more stable development environment, or Beta for a near-final experience. Each downloads as a separate installer and creates its own profile, so your stable Firefox remains untouched.
Update your current Firefox. For the Release channel, updates happen automatically in the background. To check manually, open Firefox, click the menu button (three horizontal lines in the top-right corner), go to Help → About Firefox. A dialog opens and immediately checks for updates. If one is available, it downloads and prompts you to restart. You can also set the update policy in Settings → General → Firefox Updates to choose between automatic or manual installation.
Understand versioning. Firefox uses a three-part version number like 128.0.1. The first number is the major version (increments every 4 weeks), the second is minor (usually 0, occasionally 1 for a feature point release), and the third is the patch level (increments for security or stability fixes between major releases). If you see 128.0.2, that means two emergency fixes were applied to the 128.0 release.
Watch for ESR (Extended Support Release). For organizations that need long-term stability, Mozilla publishes an ESR version every 12 months. It receives major updates once a year and security fixes throughout. If you manage many machines, ESR is the channel to use. You can download it from the same pre-release page, labeled as ESR.
Check your current version. Type about:support in the address bar and press Enter. The first line under “Application Basics” shows your version number and whether you are on the Release, Beta, Nightly, or ESR channel. This is the fastest way to confirm which branch you are running.
Report bugs if you test pre-release builds. If you find a crash or a broken feature in Nightly or Beta, use the built-in reporter: go to Menu → Help → Report a Problem. This sends a diagnostic report to Mozilla. For detailed bug tracking, you can file a report on Bugzilla, but the built-in tool is enough for most users.
Downgrade if a release breaks something critical. If an update causes problems, you can install the previous version from the Firefox archive. Download the older installer, uninstall the current version (your profile and bookmarks remain), then install the older one. Note that downgrading may reset some internal database files, but your bookmarks, passwords, and settings are preserved in the profile folder.

Common Mistakes

Running multiple channels without separate profiles. Firefox automatically creates a separate profile for each channel, but if you manually launch the wrong executable, you might overwrite data. Always use the desktop shortcuts created by each installer.
Assuming Beta is stable enough for daily work. Beta is close to final but can still have significant bugs. Do not use it for critical tasks unless you are comfortable troubleshooting.
Forgetting that Nightly updates daily. A feature that worked yesterday may be broken today. That is expected. Do not report it as a regression without checking the known issues list.
Ignoring the “About Firefox” dialog. Many users think updates are automatic and never check. If you have disabled automatic updates or are on a managed network, you might be months behind without realizing it.
Using the same profile for Beta and Release. If you deliberately point Beta at your Release profile, you risk profile corruption. Keep them separate.

Tips

Bookmark the Firefox Release Calendar page to see exact dates for upcoming merges and releases.
If you are a web developer, run Developer Edition alongside your standard Firefox. It includes additional debugging tools and is updated weekly.
Use the about:config preference app.update.interval to control how often Firefox checks for updates (default is 86400 seconds, or once a day). Lower it to 3600 for more frequent checks.
For enterprise deployment, use the ESR channel and manage updates via Group Policy or a configuration file. This avoids surprise feature changes.
When a major version is released, wait 3–5 days before updating if you rely on critical extensions. This gives time for add-on developers to update compatibility.

Troubleshooting

Update fails with an error. First, restart Firefox and try again. If it persists, download the full installer from the official site and run it over your existing installation. This repairs the update mechanism.
Firefox says it is up to date but you know a newer version exists. Your channel might be set to ESR. Check about:support and look at the “Update Channel” line. If it says ESR, you are on the extended support branch and will not receive the latest major version.
After an update, your extensions are disabled. This happens when a major version changes and add-ons need re-verification. Go to Add-ons Manager, look for the “Find updates” button, and update each extension. If one is abandoned, you may need to find an alternative.
Nightly crashes on startup. Navigate to about:profiles and create a new profile, then launch Nightly with that profile. If it works, the issue is a corrupted profile, not the build. You can also try refreshing Firefox via about:support → “Refresh Firefox”.
You cannot downgrade because the profile is newer. Firefox stores data in a format that newer versions can read but older ones may not. Back up your profile folder (located in %APPDATA%\Mozilla\Firefox\Profiles on Windows, ~/Library/Application Support/Firefox/Profiles on macOS, and ~/.mozilla/firefox on Linux) before downgrading. If problems occur, restore the backup.
Updates are blocked by your network. Managed networks or antivirus software can block update servers. Temporarily disable the firewall or add aus5.mozilla.org to the allowlist. If you are on a corporate network, contact your IT administrator.

Frequently Asked Questions

Q: How often is Firefox updated?
A: Major releases come every 4 weeks. Security and stability patches (like 128.0.1) can come at any time, usually within days of a reported critical issue.

Q: Can I use Nightly as my main browser?
A: Technically yes, but it is not recommended. Nightly is for testing and can break frequently. If you do use it, keep a backup profile and expect occasional data loss.

Q: What is the difference between Beta and Developer Edition?
A: Both are based on the same code, but Developer Edition has additional developer tools enabled by default, a different theme, and is updated on a slightly different schedule. It also has a separate profile so it can run alongside Beta.

Q: Will my bookmarks and passwords transfer between channels?
A: No, each channel has its own profile. You can manually copy your profile folder, but it is safer to use Firefox Sync with a Mozilla account to sync bookmarks, passwords, and settings across all channels.

Q: How do I know which channel I am on?
A: Type about:support in the address bar. The “Update Channel” field shows “release”, “beta”, “nightly”, or “esr”.

Q: Is it safe to skip several versions and update directly?
A: Yes. Firefox supports updates from any version to the latest. The updater handles all intermediate steps automatically. If you are very old (more than a year behind), you may need to download the full installer manually.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →