--- title: "Unity – Versions" url: "https://aalegre.net/docs/unity/unity-installation-process/unity-versions/" updated: "2025-12-14" category: "Unity - Installation Process" --- # Unity – Versions You can access all unity versions on the official [Download Archive](https://unity.com/releases/editor/archive) All new releases, major or minor, have its corresponding [patchnotes](https://unity.com/releases/editor/whats-new/#notes) & [bugtracking](https://issuetracker.unity3d.com/) ## 1.- Version Naming Each Unity version consists of three main parts: **RELEASE.MAJOR.MINOR**, which represent the release year, major release cycle, and specific updates. ### 1.1.- Release version The first number on the version naming #### Prior to 2024 Prior to 2024 unity used yearly releases and the first number indicated the year the version released. For example: **2023**.0.0f1 #### 2024 onwards To avoid strained & fragmented development, unity reverted to a classic versioning system 2024 onwards. It will start with Unity 6, and won’t upgrade to Unity 7 unless big changes are made to the engine. For example: **6000**.0.0f1 ### 1.2.- Major version The major release number refers to specific milestones or feature releases within that year. Unity releases several major updates each year to introduce new features, API changes, or major bug fixes. For example: - **2021.1.x**: The first major release of Unity in 2021. - **2021.2.x**: The second major release of 2021, often introducing bigger features. ### 1.3.- Minor version The minor version number reflects incremental changes like small bug fixes or minor improvements. These come after major releases. Unity uses a code system to differentiate minor versions: - **Alpha (`a`)**: Used for experimental versions that are still in early testing. - Example: `2022.1.0a5` (the 5th alpha release of Unity 2022.1) - **Beta (`b`)**: Beta versions are more stable than alpha, meant for wider testing but still not ready for production. - Example: `2022.1.0b2` (the 2nd beta version of Unity 2022.1) - **Final (`f`)**: These are stable, production-ready versions. Once Unity considers a version stable, it is given an `f` identifier. - Example: `2022.1.0f1` (the first stable version of Unity 2022.1) - **Patch (`p`)**: After a stable release, Unity sometimes issues patches to fix bugs or issues without introducing new features. - Example: `2021.2.5p3` (the third patch for Unity 2021.2.5) ## 2.- Version Stages Check the official documentation on [version stages](https://unity.com/releases/lts-vs-tech-stream) **INFO** It’s always recommended to use a **LTS**(Long Term Support) version ### 2.1.- LTS – Long Term Support LTS versions are stable, supported versions ideal for production use. LTS releases are typically updated with bug fixes but do not receive new features. They are released after all major updates for a particular year have been finalized. For example: - **2020.3 LTS**: This version represents a final, stable release for Unity 2020, with long-term support for bug fixes but no new features. ### 2.2.- Tech Stream / Preview Tech Stream / Preview versions are semi-stable versions, mainly used for testing new technologies. Unity discourages using this versions for final product releases. In these versions there are almost no new features added, only refinement & usability updates. ### 2.3.- Beta Beta / Alpha versions are unstable versions, unity is developing new and mostly untested features. ## 3.- Example of a Full Version **2021.2.5f1** - **2021**: Released in the year 2021. - **.2**: The second major release of the year. - **.5**: The 5th minor update (e.g., bug fixes, improvements). - **f1**: The first stable (final) release of this particular version. ## 4.- Compatibility between versions It’s always recommended to **work on the same unity version**, from the start of the project to its finish. This means always mantaining even the minor versions. If you start your project with 2022.3.45f1 you end your project with 2022.3.45f1. **Downgrading is never recommended**. Upgrading only when necessary to receive new optimizations/features/bugfixes. ### 4.1.- Change in Release #### Upgrading Upgrading releases is difficult. When changes break projects from release to release Unity gives out upgrade paths & documentation to fix them. You have to upgrade packages & fix scenes & prefabs manually. #### Downgrading Downgrading releases is not possible and will break your project’s assets & configuration ### 4.2.- Change in major version #### Upgrading Usually painless. When changes break projects from release to release Unity gives out upgrade paths & documentation to fix them. You have to upgrade packages manually, sometimes assets & scenes can be fixed with Unity provided tools. #### Downgrading Most of the times does not work. You have to downgrade packages & fix scenes & prefabs manually. ### 4.3.- Change in minor version #### Upgrading Usually painless. Unity does not give upgrade paths & documentation. No package upgrading needed. #### Downgrading Not recommended, but strangely breaks projects. Sometimes you have to downgrade packages & fix scenes & prefabs manually. ## 5.- Extra resources - [Unity – Installation](https://aalegre.net/docs/unity/unity-getting-started/unity-installation/) - [Unity – Installation Modules](https://aalegre.net/docs/unity/unity-installation-process/unity-installation-modules/)