We're looking for a user researcher to understand the needs of developers and designers. Is this you or someone you know? Check out the post: https://mzl.la/2IGzdXS

Thunderbird Binaries Redirect 1

Described below are three types of generally available Thunderbird packages - Releases, Early Preview Releases, and Nightly Builds (including trunk development builds) - and their downloaded locations.  Additionally, ad-hoc packages called try builds are made available on an as-needed basis to allow for testing of certain patches, and are typically announced in related bug reports.


Thunderbird releases have been extensively tested and are made available for anyone to download and use it.

Thunderbird releases can be downloaded from http://www.mozillamessaging.com/

Early Preview Releases

Whilst writing new versions of Thunderbird, developers release preview versions, known as Alphas and Betas. These builds are made to get feedback from testers and extension developers.

Note: While Alpha and Beta builds have had some testing, they should be considered preview only and should not be used in a production environment. Please read the release notes before downloading.

Preview Releases are available from http://www.mozillamessaging.com/thunderbird/early_releases/

Nightly Builds

Nightly builds are cutting-edge builds. They are built every 24-hours by the tinderboxes from the very latest source code. There are various sorts of nightly builds available for download. If you wish to download nightly builds to help us test for the next release, please read the testing page for where we need help.

Warning: Whilst developers try to ensure that nightly builds are stable, it is possible that errors can get into nightly builds that can destroy your data or harm it. They should only be used for testing purposes.
If you wish to use a nightly build on your main profile, you should make sure you back up your profile.

Nightly builds from the comm-central 1.9.2 branch

Builds from the comm-1.9.2 branch are called Thunderbird 3.1* builds. This series is the current development focus and builds from this branch will at one point become the Thunderbird 3.1 final release. The "comm-" in the branch name refers to the comm-central repository from which this branch originates. The "1.9.2" in the branch name indicates that these Thunderbird builds are based on the Gecko 1.9.2 platform.  Learn more about 3.1 at https://wiki.mozilla.org/Thunderbird:Thunderbird3.1

Latest English comm-central-1.9.2 branch builds are available at: http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-1.9.2/
Latest localized comm-central-1.9.2 branch builds are available at: http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-1.9.2-l10n/

Nightly builds from the comm-central trunk

The trunk is the central source code that is used for continuous and ongoing development. Trunk builds contain the very latest bleeding-edge changes and updates. The trunk currently refers to Thunderbird built with Gecko 2.0. Patches landing here will go into Thunderbird 3.3*.

Latest English trunk builds are available at: http://ftp.mozilla.org/pub/thunderbird/nightly/latest-comm-central/
Latest localized trunk builds are available at: http://ftp.mozilla.org/pub/thunderbird/nightly/latest-comm-central-l10n/

Frequently asked questions

What is the trunk?

The trunk is the central source code that is used for continuous and ongoing development. Trunk builds contain the very latest bleeding-edge changes and updates. However, the trunk can also be very unstable at times, so it's good to ask around before using trunk builds.

What is a branch?

Branches are "forks" in the code, split from the trunk and destined to become end-user releases. At conception, a branch contains everything that the trunk contains, but from that point onwards, only certain fixes or changes will be accepted. Therefore, over time, the branch becomes more stable.

Why branch? Wouldn't it be better to have everyone working towards a release?

Many developers prefer to work on areas of the code which are too risky to change when approaching a release. Some of their changes may also take months to test and implement correctly. Their changes will be made to the trunk so that they don't delay the release and will be picked up in future branches.

Distinguishing between different nightly builds

The main way you can determine if you are using a trunk or branch build is to click the "Help" menu and choose "About". You should see a string that looks something like this:

comm-central-1.9.2 branch:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20100308 Lanikai/3.1b1pre


Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a1pre) Gecko/20090826 Shredder/3.1a1pre

The part that you want to note is the Gecko revision number (rv) and the Thunderbird version string. These correspond to which build you are using. It works something like this:

rv:1.7.x and Thunderbird 1.0.x = Gecko 1.7 (Thunderbird 1.0) Branch.
rv:1.8.0.x and Thunderbird 1.5.0.x = Gecko 1.8.0 (Thunderbird 1.5) Branch.
rv:1.8.1.x and Thunderbird 2.0.0.x = Gecko 1.8.1 (Thunderbird 2) Branch.
rv:1.9.1.x and Thunderbird (or Shredder) 3.0.x = Gecko 1.9.1 (Thunderbird 3.0) Branch.
rv:1.9.2.x and Thunderbird (or Lanikai) 3.1.x = Gecko 1.9.2 (Thunderbird 3.1) Branch.
rv:2.0.0.x and Thunderbird (or Shredder/Miramar) 3.3a1pre and on = Gecko 2.0.0 (towards Thunderbird 3.3)

Document Tags and Contributors

Contributors to this page: chrisdavidmills
Last updated by: chrisdavidmills,