Skip to content
Tux Tavern Panoramic Scene

How to Add an AppImage to the Linux Start Menu

Published

Want to add an AppImage to the Linux start menu and open it instead of finding it in Downloads each time? A small file called a .desktop entry can create that menu shortcut. This guide shows what the file does, how to make one for an AppImage, and how to add a shortcut to the desktop when your Linux desktop supports it.

The menu may be called Applications, Start Menu, app launcher, or something similar depending on your Linux desktop. The steps below work with the common FreeDesktop launcher format, but exact menus and trust prompts vary.

What is a desktop entry?

A desktop entry is a plain-text file ending in .desktop. It tells Linux the app’s display name, which file to run, and what icon to show. Application menus read these entries and turn them into clickable launchers. AppImages are downloaded files, so you need to tell your menu where the AppImage is stored.

This does not install the AppImage through your distribution’s package manager. It creates a shortcut to the file. Keep the AppImage in the same place after setting up the shortcut; if you move or rename it, the menu entry may stop working.

Before you start

  1. Download the AppImage from the application maker’s official website or official release page.
  2. Move it to a permanent folder in your home directory, for example Applications. You can create that folder from your file manager. Avoid putting it in Downloads if you plan to use the shortcut long-term.
  3. Make the AppImage executable. In your file manager, right-click it, choose Properties, open Permissions, and enable the execute option. It may be named Allow executing file as a program or Is executable. The AppImage quickstart lists common file-manager steps.

Find the full path to the AppImage

The menu shortcut needs the full path to the file. In a file manager, open the folder containing your AppImage and use the location bar or file Properties to find its location. A full path looks like /home/alex/Applications/Example.AppImage.

In the example below, replace alex with your Linux username and Example.AppImage with your exact filename. Keep the folder and filename simple, without spaces, while learning. The path in the example is only a sample.

Create the desktop entry

  1. Open a plain-text editor, such as Text Editor, Kate, or Mousepad. Do not use a word processor such as LibreOffice Writer.
  2. Copy the example below into a new blank document. Replace the name and AppImage path with yours.
  3. Save the file in your personal applications folder as Example-App.desktop. With the default XDG data location, the folder is /home/alex/.local/share/applications/. Replace alex with your username. If the applications folder is missing, create it. If your file picker hides folders that start with a dot, press Ctrl+H to show hidden files.
  4. In the Save dialog, check the file really ends in .desktop, not .desktop.txt.
[Desktop Entry]
Version=1.0
Type=Application
Name=Example App
Comment=Launch Example App
Exec="/home/alex/Applications/Example.AppImage"
Icon=application-x-executable
Terminal=false
Categories=Utility;

Name is what appears in the menu. Exec is the full path to your AppImage. In this example, Icon asks the desktop to use a general application icon; you can replace it with the full path to an image icon if you have one. Terminal=false is for a graphical app. If your AppImage is a command-line program, it may need different settings.

Use a full path in Exec; do not write ~/Applications/Example.AppImage there. The desktop entry standard does not treat that like a shell command with the usual home-folder shortcut. Keep the sample path simple or see the FreeDesktop Desktop Entry Specification for advanced path quoting.

Find it in the Linux start menu

  1. Close the text editor after saving the file.
  2. Open your application menu or launcher and search for the value you put after Name=—in this example, Example App.
  3. Select the result to start the AppImage.

Most desktops notice the new entry automatically. If it does not appear, check the filename ends with .desktop, confirm the file is inside ~/.local/share/applications/, and check the Exec path letter by letter. Then close and reopen the app menu, or sign out and back in.

Put a shortcut on the desktop

The application-menu entry and a desktop icon are related but separate. Many Linux desktops do not show desktop icons by default. If yours does, you can copy the same .desktop file to your Desktop folder. Your desktop may ask you to choose Allow Launching, Trust and Launch, or a similar option before the icon works. The wording depends on your desktop environment.

Remove the shortcut

To remove only the menu entry, delete the .desktop file you created from ~/.local/share/applications/. That does not delete the AppImage itself. Delete the AppImage separately only if you no longer need the program.

Is there an easier way?

Yes. If editing a text file feels like too much, use Gear Lever to integrate AppImages with a graphical interface, or try another AppImage integration tool supported by your distribution. For one app you use rarely, mark the AppImage executable and launch it from your file manager. The official AppImage desktop integration guide explains how desktop entries fit into AppImage integration.

Common problems

  • The menu entry does not appear: check that the saved file is named Example-App.desktop, not Example-App.desktop.txt.
  • Clicking the entry does nothing: confirm the AppImage is executable and that the Exec= path exactly matches where it is stored.
  • The icon is generic: the sample uses a generic icon. Add a path to a real PNG or SVG icon if you have one.
  • The app stopped launching after you moved it: update the Exec= line to the AppImage’s new full path.

A desktop entry is a small launcher, not a security check. Only run AppImages from sources you trust. When in doubt, use the software maker’s instructions or the AppImage documentation.

Documentation reviewed November 2, 2026. These steps were checked against the linked specifications; no application installation was performed during this restoration.

Sources and further reading

Prefer a graphical way to integrate AppImages? Read our Gear Lever review and beginner’s guide.

Leave a Reply

Your email address will not be published. Required fields are marked *