Tesla software · Version numbers

How to read a Tesla version number

What each part of 2026.38.5.11 means, why FSD cars run different builds, and why your neighbour’s Tesla got the update first.

Editorial review 30 October 2026 · first published 29 October 2026 · Tesla documentation and dated tracker reports; observation dates are retained

Short answer

A Tesla version reads year.branch.revision, sometimes with one more number: 2026.38.5.11 is the 2026 software, branch 38, build 5, fix 11. Revisions are whole numbers, so .20 is newer than .2. FSD cars often sit on their own builds, and Tesla rolls each build out in stages by region, model and hardware. Two identical cars can therefore show different numbers without anything being wrong.

Four parts, four meanings

YearThe year of the software, not of your car.

Branch (week)Roughly the week of the year the branch started. New major branches have come about every four weeks.

RevisionBuilds on that branch. A whole number: .20 is newer than .2.

Sub-revisionLater fixes on that build. When only the last part changes, expect fixes rather than new features.

The first build of a new branch usually has no revision (2026.38) and goes to very few cars. Widely installed builds tend to carry higher revisions because they have been through more rounds of fixes.

Why two cars on “2026.38” are not the same

Branch 2026.38 as trackers listed it by 30 October 2026. Red: everyday builds. Blue: FSD builds for North America and Australia. Amber: the separate 2026.39.6 build with FSD v14.2.2.6.

Cars that use FSD are typically placed on a separate track: they get FSD builds sooner and wait longer for new everyday features until the two are merged. In 2026, for example, the summer features reached European FSD cars only with 2026.27.100.1.

Why your neighbour gets it first

Staged on purposeTesla sends each build to a small group first, fixes what shows up, then widens the rollout.
Decided per carOrder depends on factors such as region, model and hardware. Tesla’s manual says it decides how, when and where to send each release.
Not on requestTesla does not update software on request. Advanced in the update settings gets builds when they are available for your car, but it is not the early-access programme.

Good to know

Trackers report that a check from the car finds a new build at most once every 24 hours, so opening the Software screen repeatedly does not speed things up.

Read the notes before you install

Since 2023.26, a link next to the update progress bar opens the release notes of the pending update, even while it is still downloading; the Tesla app shows them too. After installing, they stay under Controls › Software › Release Notes. Tesla says the release notes take precedence over the owner’s manual when the two differ.

What a number tells you, and what it does not

The number tells you	It does not tell you
Which branch and build you run	Which features your hardware supports
Whether a build on the same branch is newer	What is approved in your country
Whether an FSD version is included (from the notes)	When your car will get the next one

Questions

Is 2026.38.20 newer than 2026.38.3?

Yes. Each part is a whole number, so 20 is higher than 3.

Can my car skip a version?

Yes. Tesla decides which build your car gets next. Many cars on 2026.32.7 are moving straight to a 2026.38 build.

Does .100 mean Europe?

Often, but not always. European FSD builds were listed as 2026.27.100.1 and 2026.33.100 in 2026, then 2026.39.6 arrived with the same FSD version. Read the notes, not the suffix.

Sources

Tesla documentation

Tracker reports and press

Summaries in our own words, not Tesla’s release notes. Features depend on model, hardware, market and software version; the notes in your car take precedence. Release dates are when public trackers first listed a build, and their country data are samples. Handlefree is independent and not affiliated with Tesla, Inc.