What "Firefox Train" Means on WhatTrainIsItNow.com

Updated

A "Firefox train" is Mozilla's term for the scheduled release cadence that moves each Firefox version through three development channels — Nightly, Beta, and Release — on fixed dates. WhatTrainIsItNow.com is a lightweight dashboard that shows which version currently occupies each channel, plus the next merge day and ship date. It's useful if you want to know what's shipping next, when a version moves from Beta to Release, or which ESR line is current, without digging through Mozilla's wiki pages.

The three channels and how a version moves

Each Firefox version boards the train as a Nightly build, then moves one channel forward at each merge day:

  • Nightly — the newest code, where a version starts. Features land here first and may still be removed.
  • Beta — the version has been stabilized and is being tested by a wider audience before release.
  • Release — the version ships to general users.

When Nightly moves to Beta, a new version number starts on Nightly. When Beta moves to Release, the previous Release version is retired. So at any moment, three consecutive version numbers are in flight at once.

The site's current snapshot shows this clearly:

Channel Version shown
Nightly 160
Beta 159
Release 158
ESR 153 / 115

The page also lists the next merge day (October 22) and the ship date for Firefox 159 (October 27, "in 6 days"), which is the Beta-to-Release step for that version.

Reading the numbers

The version numbers are sequential, and the gap between them is always two: if Release is 158, Beta is 159 and Nightly is 160. This lets you sanity-check the page — if the numbers don't line up that way, the snapshot is stale or mid-merge. The "in 6 days" countdown is relative to when the page was generated, so treat it as a rough indicator rather than a live clock.

What ESR means on the train

ESR (Extended Support Release) is a separate track that does not follow the same rapid cadence. It's a version pinned for organizations that need a longer support window and slower change. On the site it appears as its own line — currently "153 / 115" — meaning an ESR branch based on Firefox 153 alongside the older 115 ESR line. ESR versions do not advance with every merge day; they receive security and stability fixes on their own schedule.

If you're deciding which channel to follow: Nightly is for testing and early feedback, Beta for pre-release verification, Release for normal use, and ESR for environments that value stability over new features.

How to use the site for a practical question

Say you need to know whether a fix you're tracking will reach regular users soon. Check which channel it landed in, then count the merge days:

  1. Open the site and note the version in the channel where the fix exists.
  2. If it's in Nightly, it needs two merge days to reach Release (Nightly → Beta → Release).
  3. If it's in Beta, it needs one merge day.
  4. Cross-check the listed "Next merge day" and ship date to estimate timing.

The site also links to bug landings and crash data per channel ("Bug landings and crashes — In Nightly / In Beta / In Release"), which is the place to confirm whether a specific change is actually present in a given build.

Common points of confusion

  • "Train" is not a product. It's the release process, not a separate Firefox edition.
  • The countdown is a snapshot. "Ships on October 27 (in 6 days)" reflects the page's generation time; verify against the calendar if the date matters.
  • ESR numbers don't fit the 158/159/160 pattern. The ESR line is intentionally offset and should be read on its own.
  • Merge day and ship day are different events. Merge day moves a version to the next channel; ship day is when the Release build goes out. The page lists both, and they're usually a few days apart.