Everyone loves receiving new updates for their Tesla. But do you know what the version numbers mean and why there are so many versions? We take a look at exactly what Tesla version numbers imply and how Tesla creates and branches their code.
What It Means
A recent Tesla update had version number 2021.32.201b7f33580a5f. Let’s take a look at how Tesla numbers their versions and what it means.
The first portion of the version number, 2021, is the year of the release. The second, 32, is the week number of the year. Since Tesla has a history of releasing a major update every four weeks, you’ll almost always see this number in increments of four. After the week number is the revision of the build.
The first build of a release usually does not have a revision and it’s simply known as 2021.32. This is the first build and is only rolled out to a very small portion of the Tesla fleet, if at all.
As Tesla gathers fleet data and learns about any issues, they’ll make improvements and fixes to the release. The next update will have a revision number, such as '.1'. Revision numbers go by incrementally, although not always by one. The number is often arbitrary, but it should reflect the amount of changes in the release. For example, going from 2021.32.1 to 2021.32.2 would often indicate a smaller change than jumping to 2021.32.20.
The revision number should be looked at as a single number and not as a decimal. For example, version 2021.32.2 is an earlier build of 2021.32.20.
Hash
The seemingly random numbers and letters you'll see at the end of a version number is a unique key called a hash that is used to identify that code. A hash is used every time new code is added to a code base and the ones we see in an update are used to identify that specific release.
Gradual Updates
Tesla will often start with a release such as 2021.32 and they’ll gradually roll it out to some vehicles, get data, make fixes and then roll out another release. By the time an update is in wide release, it likely has gone through various revisions and will have a higher revision number.
Tesla releases their updates gradually so that they can minimize any potential issues and keep everyone safe. If there are any major issues with a release, it likely only impacted a smaller portion of the fleet.
As anticipation builds for Tesla’s Robotaxi network debut in Austin, potentially just a few short weeks away, the National Highway Traffic Safety Administration (NHTSA) is turning its official eye onto Tesla. The ask? How will Tesla’s FSD handle the unpredictable realities of challenging weather?
The NHTSA Request
The NHTSA has sent a formal letter to Tesla, which was made public on May 12th, requesting detailed information about Tesla’s Robotaxi service. The NHTSA inquiry centers specifically on the safety and performance of FSD when faced with reduced visibility conditions like rain, fog, and sun glare. The request is tied to an ongoing NHTSA investigation, which was initiated in October 2023, examining Tesla’s FSD and Autopilot suite following incidents in poor visibility.
Tesla’s executives, including Elon Musk, have previously stated that the company is full steam ahead to launch Robotaxi in Austin this June. However, NHTSA’s pointed questions come even as Tesla has recently discussed its plans to work on region-specific and weather-specific FSD training.
Tesla’s executive leadership acknowledged the need to adapt the system to diverse environmental and weather conditions. Now, regulators want specifics on how Tesla intends to address environmental conditions and how that translates to operational safety for the fleet.
Request Breakdown
NHTSA’s letter outlines a need for detailed information from Tesla before the service launches and covers several key areas. We’ve broken this down into various sections below:
NHTSA is looking for the exact number of vehicles and models that will be part of the initial Austin fleet, and what the projected service availability times would be for said fleet. Tesla has previously said it’d launch with 10-20 Model Ys, but looks like NHTSA is looking for additional details.
Oversight
In terms of oversight, NHTSA is looking to confirm whether the Robotaxis will operate under real-time supervision of Tesla’s employees, either remotely or in-vehicle.
This is a question on our minds as well. A recent app update suggested that Tesla could have a driver in the vehicle, but it wasn’t clear whether this was referring to Tesla’s own fleet or customer-owned vehicles. The only thing we have heard officially from Tesla is that Tesla “may” use remote support, but that they were still looking into it.
Adverse Weather Capabilities
This is the meat and potatoes of the request - how will Tesla ensure safety during sun glare, fog, heavy rain, snow, or dust? What specific protocols are triggered if poor visibility is encountered mid-trip? Will the vehicle pull over or call home and cancel rides?
Sensor Technology
Surprisingly, NHTSA is looking for details regarding the vehicle the Robotaxi sensor suites and how Tesla intends to use those sensors to ensure safe operation under varied conditions. NHTSA has had previous submissions from Tesla in regard to its sensor suite and how it uses the technology, so it feels odd that they are requesting another batch - but this could be related to the use of the next generation of FSD (Unsupervised).
Compliance
Does Tesla’s FSD system adhere, either fully or partially, to established industry standards for autonomous driving? This likely refers to the NHTSA Automated Vehicles for Safety guidebook, which lays out the “L0 to L5” driver assistance vs automation system.
Future Expansion
Finally, NHTSA is looking for the timeline for enabling Robotaxi functionality on vehicles not directly owned or controlled by Tesla. Tesla has already come out and said that customer-owned vehicles wouldn’t be allowed on the robotaxi network until 2026, but obviously, NHTSA wants to hear directly from Tesla and likely has more specific questions covering a wide variety of potential issues.
These questions will likely have to be answered with considerable amounts of data and justification for the NHTSA. Once all that is done, Tesla will be in a better position to receive regulatory approval at a larger scale than just within the city of Austin or the state of Texa with the NHTSA’s backing.
Successfully addressing this letter will be the key for Unsupervised FSD moving forward, but Tesla hasn’t issued a public response to the agency’s letter, and likely won’t in a public manner. So we’ll have to wait and see how the launch of the Robotaxi network pans out next month.
After an 84-day wait since the last FSD update, Tesla has finally begun rolling out a new version of FSD V13 to its AI4-equipped vehicles. This new release, V13.2.9, is rolling out to all vehicles, including the Cybertruck.
Unfortunately, since it’s a minor point release (from V13.2.8), the release notes are the same, and Tesla hasn’t included a change log or changed what’s coming in the future.
Software Update 2025.14.6
The FSD update is rolling out with Tesla software update 2025.14.6. Interestingly, update 2025.14.6 is seeing a wider distribution and is also being made available to vehicles without FSD and outside North America. For those vehicles, this update just includes bug fixes.
There’s one fix in particular that’s expected to be included in this update, according to a message from Tesla Service. In earlier 2025.14 updates, there was a bug in some vehicles that prevented some vehicles from falling asleep properly due to a Telematics Control Unit (TCU) issue. This bug caused additional battery drain since some of the vehicle’s systems remained.
Tesla Service said they planned to include a bug fix in update 2025.14.6, but it hasn’t been confirmed whether the fix actually made it out in this release.
Early Access Users and More
FSD v13.2.9 was first rolled out to Tesla’s standard Early Access group, including well-known community members and content creators. It has also reached participants in the newer, Texas-based Early Access Program, suggesting that the update is relatively stable and may serve as a foundation for upcoming FSD releases.
Tesla could be intending to use the Texas Early Access Program to test various features, perhaps related to the upcoming Robotaxi network launch in Austin. While this is plausible, it is merely speculation, and we’ll be keeping a close eye on that group to see what exactly Tesla does.
HW3 Users
While Tesla has recently been including FSD updates for HW3 and HW4 in the same release, this update does not include any changes for HW3 users. HW3 vehicles that are receiving this update are staying on FSD V12.6.4, which means that whichever fixes this update includes they’re specific to FSD V13 or HW4.
Point Release - Not Much New
Being a point release, V13.2.9 isn’t expected to introduce any major new capabilities. Tesla hasn’t provided specific release notes detailing changes from V13.2.8.
Hopefully, Tesla has taken into account recent user feedback on V13.2.8 about lane centering and lane selection, and this update addresses some of those issues. However, early feedback is that those issues are still present.
There is always potential for a more substantial update in the near future, so keep your fingers crossed, but after such a long wait, we expected more to be included. It seems like Tesla may have felt the need to address a bug in this release instead of waiting for the next major release, which is expected to either be FSD V13.3 or FSD V14.
The fact that Software Update 2025.14.6 is going out wider than the Early Access audience suggests that Tesla is confident in this release and that it likely only includes very minor changes. We expect this update to continue going out over the coming days.
![Tesla Updates Lane Departure Avoidance, Likely Now Using FSD Stack [Video]](https://www.notateslaapp.com/img/containers/article_images/tesla-screen/lane-departure-warning.webp/bac626b9acadf88ee44775c5ee187c06/lane-departure-warning.jpg)
![Exclusive: A Look Inside the Tesla Diner [PHOTOS]](https://www.notateslaapp.com/img/containers/article_images/2025/diner-seats.jpg/b0b4cb51b80d1f29298c9ca6b9ad2ae8/diner-seats.jpg)
