How to Upgrade to Blender 2.9 on Linux

Upgrading to Blender 2.9 on Linux sounds simple: download Blender, open Blender, make art, become a 3D wizard. In real life, Linux adds a few flavors to the soup. Are you using Ubuntu, Fedora, Debian, Arch, Linux Mint, Pop!_OS, openSUSE, or something delightfully obscure that was installed at 2 a.m. after three cups of coffee? Are you upgrading from Blender 2.8, replacing an older repository package, or installing Blender 2.90 side by side with a newer version?

The good news is that Blender is one of the friendliest major creative tools on Linux. Blender 2.90, often casually called Blender 2.9, was a major step after the 2.8 series. It improved modeling, sculpting, EEVEE, Cycles, UV editing, animation, importing and exporting, and general usability. If you need Blender 2.90 for a tutorial, an older project, an add-on, a production pipeline, or simply because you like that era of Blender, Linux gives you several ways to get there.

This guide explains the safest and most practical ways to upgrade to Blender 2.9 on Linux, including the official tar.xz archive method, Snap, Flatpak, package managers, desktop launchers, backups, add-ons, troubleshooting, and real-world workflow tips. No wizard hat required, though it does improve terminal confidence by at least 14%.

Before You Upgrade: Know What “Blender 2.9” Means

When people say “Blender 2.9,” they usually mean Blender 2.90, the first release in the 2.9x cycle. The most practical Blender 2.90 release to install is usually Blender 2.90.1 because it was a corrective release that fixed stability issues after 2.90.0. If you are following an older tutorial that says “install Blender 2.9,” Blender 2.90.1 is a smart target.

However, Blender has moved far beyond the 2.9 series. Modern Snap, Flatpak, and distribution repositories generally offer newer Blender versions. That is excellent if you want the latest features, but not ideal if your goal is specifically Blender 2.90. For that reason, the official archived tarball is usually the cleanest way to install Blender 2.9 on Linux today.

Why Upgrade to Blender 2.9 on Linux?

Blender 2.90 polished many of the changes introduced in Blender 2.8. If Blender 2.8 was the dramatic makeover episode, Blender 2.90 was the follow-up where everything started behaving more like a professional production tool.

Better Modeling Tools

Blender 2.90 introduced useful modeling improvements such as smarter extrusion behavior, better bevel workflows, UV improvements, and geometry editing refinements. For hard-surface artists, these changes made Blender feel more predictable and less like a puzzle box with a sense of humor.

Improved Sculpting

The 2.9 series brought important sculpting improvements, including better support for multiresolution workflows and pose brush updates. Artists working on characters, creatures, props, and high-detail meshes gained more flexibility.

Rendering and Viewport Enhancements

Blender 2.90 improved EEVEE motion blur and Cycles rendering features, including viewport denoising improvements. If your older Blender build feels slow, noisy, or limited, upgrading to Blender 2.9 can make daily work smoother.

Pipeline and File Compatibility

Many users install Blender 2.90 because a course, studio project, add-on, or archived .blend file was created around that version. Newer Blender versions are powerful, but old production files sometimes behave best in the version they were built for. A side-by-side Blender 2.90 install can save you from compatibility headaches.

Step 1: Check Your Current Blender Version

Open a terminal and run:

If Blender is installed through your system package manager, this command may show the repository version. If the terminal says the command is not found, Blender may not be installed globally, or you may be running it from a downloaded folder.

You can also open Blender and choose:

Write down your current version before changing anything. This is boring advice, but boring advice is often what saves your Sunday afternoon.

Step 2: Back Up Your Blender Settings

Before upgrading, back up your Blender configuration folder. Blender stores user preferences, add-ons, startup files, and other settings under your home directory. On many Linux systems, the folder is:

Back it up with:

This creates a dated backup. If an add-on misbehaves or a preference file gets cranky, you can restore your previous setup. This is especially useful when moving between Blender 2.8, 2.90, and newer versions.

Best Method: Install Blender 2.90.1 from the Official Archive

The official archive method is the most reliable option when you specifically need Blender 2.9 on Linux. It does not depend on your distribution’s package repository, does not replace your system Blender unless you choose to, and can run side by side with other Blender versions.

1. Create a Software Folder

Choose a clean location for manually installed apps. A common choice is:

You can also use /opt or /usr/local, but those locations usually require administrator permissions. For most users, ~/software is easier and safer.

2. Download Blender 2.90.1

Download the Linux 64-bit tar.xz archive for Blender 2.90.1 from Blender’s official release archive. You can use your browser or use wget in the terminal:

If your system does not have wget, install it with your package manager or download the file manually in your browser.

3. Verify the Download When Possible

Verification helps confirm that the file downloaded correctly. Blender provides checksum files for releases. If you download the SHA256 file, you can compare it with the archive:

Compare the output with the checksum listed for blender-2.90.1-linux64.tar.xz. If the numbers match, your download is good. If they do not match, delete the file and download it again.

4. Extract the Archive

Extract the file with:

You should now have a folder named something like:

5. Run Blender 2.90

Start Blender from the extracted folder:

If Blender opens, congratulations. You have upgraded to Blender 2.9 on Linux without asking your package manager to perform interpretive dance.

Create a Desktop Launcher for Blender 2.9

Running Blender from the terminal works, but most people prefer a menu entry. You can create a desktop launcher in your local applications folder.

Create a new file:

Paste this content, adjusting the paths if your folder is different:

Replace YOUR-USERNAME with your actual Linux username. Save the file, then make it executable:

Log out and back in if the launcher does not appear immediately. On many desktop environments, it will show up in the application menu under Graphics.

Optional: Add Blender 2.9 to Your PATH

If you want to launch Blender 2.90 from the terminal using a custom command, create a symbolic link:

Now try:

If your system says the command is not found, make sure ~/.local/bin is in your PATH.

Can You Upgrade to Blender 2.9 with APT?

On Ubuntu, Debian, Linux Mint, and other Debian-based distributions, you may be tempted to run:

This installs the Blender version available in your distribution repositories. That version may be older or newer than Blender 2.90, depending on your distribution release. On modern systems, it is unlikely to install Blender 2.90 specifically.

If your exact goal is “I need Blender 2.90,” APT is not the best route. Use the official archive method instead. If your goal is simply “I want Blender installed,” APT is convenient and integrates well with system updates.

Can You Use Snap to Install Blender 2.9?

Snap is a universal Linux package format supported by Canonical and widely used on Ubuntu-based systems. The Blender Snap is published by the Blender Foundation and can be installed with:

This is convenient for getting a current Blender release, and Snap handles updates automatically. However, Snap generally tracks current channels, not old Blender 2.90 builds. If you need Blender 2.9 exactly, Snap is not the most dependable method. If you simply want a maintained Blender package with easy updates, Snap is a reasonable choice.

Can You Use Flatpak to Install Blender 2.9?

Flatpak is another popular universal package format. On many distributions, you can install Blender from Flathub with:

Flatpak is excellent for users who want a desktop-friendly Blender installation without depending on a distribution repository. Like Snap, though, Flathub typically serves current builds. For a specific archived version such as Blender 2.90.1, the official tar.xz archive remains the cleaner solution.

Can You Upgrade on Arch, Manjaro, or Fedora?

Rolling-release systems such as Arch and Manjaro usually provide newer Blender versions quickly. Fedora also maintains Blender packages in its repositories. You can install Blender through package managers like pacman or dnf:

or:

These commands are great for installing the repository version. They are not ideal for installing Blender 2.90 specifically. If Blender 2.90 is required, use the archived Blender tarball and run it side by side with the repository version.

How to Keep Blender 2.9 Side by Side with Newer Versions

One of the best things about Blender on Linux is that the official archive does not need a traditional installation process. You can keep several versions in separate folders:

This is useful when older add-ons require older APIs, tutorials were recorded in specific versions, or clients send files built in a particular Blender release. Instead of forcing every project through one version, you can open each project with the Blender version that makes the most sense.

Transfer Preferences Carefully

When Blender 2.90 starts for the first time, it may offer to import settings from a previous version. This can save time, but it can also bring old problems with it. If you had a messy 2.8 setup filled with experimental add-ons, migrating everything may turn your shiny upgrade into a haunted garage sale.

A safer approach is to import only what you truly need: keymaps, themes, startup files, and trusted add-ons. If something breaks, start Blender with factory settings and re-enable add-ons one by one.

Check Add-On Compatibility

Blender add-ons depend on Blender’s Python API. Some add-ons built for Blender 2.79 or early 2.8 versions may not behave correctly in Blender 2.90. Before upgrading a production project, make a list of essential add-ons and test them in Blender 2.90.

Look for these common issues:

• Add-ons failing to enable in Preferences.
• Missing panels or buttons.
• Scripts throwing Python errors in the console.
• Old import/export tools behaving differently.
• Rendering add-ons needing updated dependencies.

If an add-on is mission-critical, test it before opening your most important project file. Your future self will send you a thank-you card.

Open Old Projects Safely

Before opening an important .blend file in Blender 2.90, duplicate the file:

Open the copy first. Save it under a new name after confirming that materials, rigs, simulations, constraints, and render settings behave correctly. Blender is generally good with compatibility, but major version jumps can still change workflows.

Troubleshooting Blender 2.9 on Linux

Blender Does Not Launch

Run Blender from the terminal:

The terminal may show missing libraries, graphics driver errors, or permission issues. This output is much more useful than double-clicking the icon and watching nothing happen, which is the desktop equivalent of being ghosted.

Permission Denied

If the Blender file is not executable, run:

Graphics Problems

Blender relies heavily on OpenGL. If the interface glitches, update your GPU drivers through your distribution’s recommended driver tool. NVIDIA users should generally use the official proprietary driver offered by their distribution. AMD and Intel users usually rely on Mesa drivers, which are updated through system packages.

Desktop Icon Does Not Work

Check the Exec path in your desktop file. It must point directly to the Blender executable. Avoid using ~ inside desktop files because many desktop environments do not expand it correctly. Use the full path instead.

Blender Opens the Wrong Version

If typing blender opens another version, your system PATH is finding the repository version first. Use your custom command, such as:

or launch Blender from the extracted folder directly.

Should You Remove the Old Blender Version?

You do not have to remove your old Blender version. In fact, keeping multiple versions is often smarter. If you installed Blender through APT, DNF, Pacman, Snap, or Flatpak, that version can remain installed while Blender 2.90 lives in ~/software.

If you truly want to remove a repository version, use the matching package manager. For example:

For Snap:

For Flatpak:

Only remove old versions after confirming that Blender 2.90 opens your projects correctly.

Practical Experience: What It’s Like Upgrading to Blender 2.9 on Linux

Upgrading to Blender 2.9 on Linux is usually smoother than people expect, especially if you use the official archive instead of wrestling with package repositories. The first thing most users notice is that Blender does not behave like a typical Linux application. You do not always need to install it system-wide. You can download it, extract it, and run it. That simplicity feels strange at first, but it is one of Blender’s biggest strengths.

In real use, the best experience comes from treating Blender versions like separate tools rather than one single system package. Keep Blender 2.90 in its own folder. Keep your newer Blender version in another folder. Create separate launchers with clear names: “Blender 2.90,” “Blender 3.6 LTS,” “Blender Current,” and so on. This avoids the classic problem where you open a file in the wrong version, save it, and then wonder why your older pipeline suddenly looks at you like you insulted its ancestors.

Another practical lesson is to test add-ons before assuming everything works. Blender 2.90 sits in an interesting place in Blender history. It is modern enough to feel familiar to 2.8 users, but old enough that some newer add-ons may no longer target it. If your workflow depends on add-ons for UV tools, asset libraries, architectural modeling, rigging, or import/export formats, install those add-ons one at a time. Open Blender after each change. If something breaks, you know the culprit. This is much better than enabling twenty add-ons at once and then conducting a detective investigation worthy of a streaming miniseries.

File management also matters. When upgrading, never test with your only copy of a project. Duplicate the .blend file, open the copy in Blender 2.90, check materials, cameras, lights, modifiers, constraints, simulations, and render settings, then save the file with a version label. A filename like robot_scene_blender290_test.blend may not win a poetry award, but it will prevent confusion later.

On Linux desktops, the most common annoyance is not Blender itself but the launcher. If your menu icon fails, the issue is usually a wrong path in the .desktop file. Use full paths instead of shortcuts. Make sure the executable path points to the actual blender file inside the extracted folder. Also check that the icon path is valid. Once the launcher is fixed, Blender 2.90 feels just like a normal installed application.

Performance depends heavily on graphics drivers. If Blender opens but the viewport acts strange, update your GPU drivers before blaming Blender. NVIDIA users should check the recommended proprietary driver for their distribution. AMD and Intel users should keep Mesa packages current. A stable graphics stack makes more difference than most beginners realize.

The biggest takeaway from upgrading to Blender 2.9 on Linux is this: do not overcomplicate it. The official archive method is clean, reversible, and friendly to side-by-side workflows. Package managers are excellent for current Blender releases, but archived versions are best handled manually. Back up your settings, extract Blender into a dedicated folder, create a launcher, test your add-ons, and keep project copies. That workflow is boring in the best possible way. And in 3D production, boring setup means fewer surprises when you are rendering at midnight.

Conclusion

Upgrading to Blender 2.9 on Linux is easiest when you use the official Blender 2.90.1 archive. Package managers, Snap, and Flatpak are useful for current Blender releases, but they are not the best choice when you need one specific historical version. The archive method gives you control, keeps your system clean, and lets Blender 2.90 run side by side with other versions.

Before upgrading, check your current version, back up your configuration, download the official tar.xz file, verify it when possible, extract it to a dedicated folder, and create a desktop launcher. Then test your add-ons and project files carefully. Blender is powerful, but a calm upgrade process is even more powerful. It keeps your art flowing, your files safe, and your Linux desktop slightly less dramatic.