Another method is called the AppImage, which is a unique format for distributing Linux applications in such a way that they don’t require installation and can be run without admin privileges. In other words, you download the AppImage for an application and run it. That’s it. Also: Twitter turns its back on open-source development Well, sort of. There’s another step to take before you can run the application, which is part of what I want to talk about. But first…

Why use AppImages?

This is the big question. And even after using AppImages for quite some time, the main answer I have for the question is that, in some cases, there isn’t an alternative. There are a few applications I’ve used over the years that only offer an AppImage option. The reason you might find this is that a developer or team of developers doesn’t want to have to develop their app for the numerous desktops available for Linux. With AppImages, the app should run (exactly as expected) regardless of what desktop environment or window manager is being used. This is a big plus for developers who need to deliver their products quickly and reliably. Also: Cool things you can do with a Linux desktop The primary goals for AppImages are simplicity, binary compatibility, distribution agnosticism, zero installation, zero root permission required, and portability. This is all achieved while leaving the operating system untouched. Sounds like a perfect system, correct? For the most part, it’s quite good. But there are downfalls. For example, you cannot upgrade an AppImage. Instead, you download a new image and run it in place of the old (hoping all of your configurations and data won’t be lost). The other downfall is that users often have to manage the executable permission for the AppImage. Although setting that permission is quite simple, it is another step. Now that you have an understanding of what AppImages are, let’s see exactly how they are used on Linux. I’m going to show you how by way of the Bitwarden AppImage.


The only thing you’ll need for this is a running instance of a Linux distribution. It doesn’t matter what distribution it is, only that it has a GUI. That’s it. Let’s get this AppImage running.

How to use an AppImage on Linux

Change execution permission from the command line

Another way of giving the file execution permission is from the command line. This is not quite as easy but it’s also not hard.  Also: How to use the Pop!_OS Tiling feature (and why you should) To give the file execution permission from the command line, open a terminal window and then change into the Downloads directory with: Next, give the file execution permissions with the command: And that’s all there is to using an AppImage on Linux. These types of applications are a viable option for anyone looking to run applications on Linux that aren’t found within the built-in package manager. The one caveat to running AppImages on your desktop is they often do not have the means to integrate with your desktop menu, docks, or panels. Because of this, either you have to launch the application from the file manager or some desktop environments will allow you to create a desktop file first (which is beyond the scope of this article). Some AppImages (such as the one for Bitwarden) do offer a desktop integrations option that will create a launcher for your menu. If you see an integration option on the first launch of the application, make sure to go ahead with that configuration to simplify things.