Feature Proposal: Built-in Version Update Manager for Blender

I would like to propose a built-in Version Update Manager for Blender.

Currently, when many users want to upgrade Blender to a newer version, they still have to manually visit the website, download the installer or portable package, install the new version, manage old versions, and check whether preferences, add-ons, and project compatibility remain stable.

For experienced users, this is manageable.

However, for beginners, students, educators, and artists who are not deeply technical, this creates unnecessary friction. Updating Blender can feel like a separate technical task rather than a natural part of using the software.

I think Blender would benefit greatly from a built-in update system such as:

Help → Version Update Manager

or

Edit → Preferences → Updates

Proposed functionality:

1. Show the currently installed Blender version.

2. Show available stable versions.

3. Show the latest LTS version.

4. Optionally show beta or experimental versions only if the user enables them.

5. Allow users to choose the exact version they want to install.

6. Show release notes before updating.

7. Warn users about possible add-on compatibility issues.

8. Allow side-by-side installation instead of forced replacement.

9. Offer safe preference migration.

10. Allow rollback to a previous version if needed.

Most importantly, this should not be forced auto-update.

Blender users often need version stability for production, education, research, and long-term projects. Therefore, the update system should be user-controlled.

The ideal flow could be:

Check for available versions → Select desired version → Download inside Blender → Install safely → Preserve or migrate settings → Restart Blender

Why this would be valuable:

• Beginners would be less afraid of updating.
• Students could stay aligned with tutorials and courses more easily.
• Educators could manage classroom versions more smoothly.
• Studios could reduce version-management overhead.
• Users would apply bug-fix and stability releases more reliably.
• Blender would feel more polished as a professional creative platform.
• Side-by-side installation would preserve Blender’s current flexibility.

A minimal first version could simply notify users of a new stable or LTS release, show release notes, and help them download/install the chosen version safely.

A more advanced version could later include add-on compatibility checks, rollback, beta channels, and institutional deployment options.

I believe this would be a major quality-of-life improvement for Blender’s growing global user base.

Blender is already an extraordinary tool. A safer and smoother update workflow would remove one of the most practical friction points for many users while preserving Blender’s philosophy of freedom and user control.