If you need to run a version of Blender on Linux that isn't in your Linux distribution repository, it can be cumbersome to set up and run, especially for rolling distributions where the system version of Python can change. While Blender's website offers downloads for portable versions of Blender for Linux in a tarball, extracting these tarballs somewhere and maintaining a path hierarchy is also cumbersome and suboptimal. This repository contains two small bash scripts that download these same portable tarball releases of Blender LTS for Linux and convert them into an AppImage.
Using these AppImages is as easy as extracting the zip somewhere and double-clicking it. There is no need to add a custom repository or run a shell script with root privileges. You can even download and run two different AppImage versions of Blender at the same time.
For more information on how AppImages work, visit https://appimage.org/
AppImage builds are created using a GitHub workflow and are available on the Releases page.
Download and extract the zip, then double-click on the extracted AppImage to run.
The release title specifies the date the AppImage is built rather than the version of Blender.
If you can't open an AppImage make sure libfuse.so.2
is installed in your system.
If you can't or won't install libfuse.so.2 you can extract the AppImage
with the parameter --appimage-extract.
More information at
https://docs.appimage.org/user-guide/troubleshooting/fuse.html.
You will need a Linux machine to build an AppImage
On a terminal run the following to make sure scripts dependencies are installed
which cat echo md5sum sed sha256sum tar wget zip > /dev/nullThe command will exit without printing anything if all dependencies are satisfied. If this is not the case, refer to your distribution documentation to determine what packages to install.
Run the manifest script in a terminal
./manifest.shIf the dialog command is installed then a checkbox list will be displayed,
if not; a selection list similar to this will appear:
0: blender-2.79b-linux-glibc219-i686
1: blender-2.79b-linux-glibc219-x86_64
2: blender-2.83.20-linux-x64
3: blender-2.93.18-linux-x64
4: blender-3.3.21-linux-x64
5: blender-3.6.16-linux-x64
6: blender-4.2.2-linux-x64
Select options by numbers separated by space or a letter:
Type the number(s) of the Blender version(s) to make an AppImage of and press enter.
For example, typing 0 6 5 to the list above will build an AppImage
of blender-2.79b-linux-glibc219-i686, blender-4.2.2-linux-x64
and blender-3.6.16-linux-x64 in that order.
If you already know which number(s) of the AppImages
you want to build, you can pass them as parameter(s)
like ./manifest.sh 0 6 5 to skip the menu.
The AppImage will be created and stored in a zip automatically. Storing an AppImage in a zip archive will preserve the files executable permission. This will make deployment more streamlined and feel more familiar to macOS and Windows users.
Due to the sheer number of releases Blender has
manifest.sh will only list the latest version in each LTS release
as listing every build ever would be impractical.
To create an AppImage of a Blender version
not listed by manifest.sh (such as experimental or archived Blender releases),
provide the URL for the hash checksum and the source tarball
directly to mkAppImg.sh.
Example:
./mkAppImg.sh https://download.blender.org/release/Blender2.79/release279.md5 https://download.blender.org/release/Blender2.79/blender-2.79-linux-glibc219-x86_64.tar.bz2./mkAppImg.sh https://download.blender.org/release/Blender5.0/blender-5.0.0.sha256 https://download.blender.org/release/Blender5.0/blender-5.0.0-linux-x64.tar.xzYou can also use this method to access an alternative mirror
if the default download.blender.org is not accessible or missing a file.
Example:
./mkAppImg.sh https://download.blender.org/release/Blender4.5/blender-4.5.5.sha256 https://ftp.halifax.rwth-aachen.de/blender/release/Blender4.2/blender-4.5.5-linux-x64.tar.xz