Linux installation

PhotoCraft for Linux — AppImage, Flatpak, DEB, RPM and tarball

Match the CPU architecture first, then use a package format suited to your distribution.

Choose a format and architecture

Download links below point directly to the official v0.7.0 GitHub release, checked on 2026-10-11. Newer releases may be available after this date; read the latest release notes (opens a new tab) before installing.

FormatChoose it forx86_64 · Intel/AMDaarch64 · ARM64
AppImageA single executable app package.AppImage (opens a new tab) (72.6 MB)AppImage (opens a new tab) (69.5 MB)
DEBDebian, Ubuntu and compatible distributions.DEB (opens a new tab) (77.4 MB)DEB (opens a new tab) (74.8 MB)
RPMFedora, RHEL and compatible distributions.RPM (opens a new tab) (76.9 MB)RPM (opens a new tab) (74.1 MB)
FlatpakA local bundle in a Flatpak setup.Flatpak (opens a new tab) (57.4 MB)Flatpak (opens a new tab) (53.6 MB)
tar.gzManage extracted binaries yourself.Tarball (opens a new tab) (76.3 MB)Tarball (opens a new tab) (72.8 MB)

Use uname -m to inspect your machine’s architecture. x86_64 is 64-bit Intel/AMD; aarch64 is ARM64. Other architectures and dependency details belong to the exact release (opens a new tab) and upstream packaging documentation (opens a new tab). A .zsync attachment supports AppImage updating; it is not the application.

Install using your normal Linux tools

First verify the file. For AppImage, permit execution in file properties and launch the downloaded file. For DEB or RPM, use your distribution’s software installer or package manager so it can resolve dependencies. A tarball gives you extracted binaries to manage yourself.

For the local Flatpak bundle, the README provides:

flatpak install --user photocraft-0.7.0-linux-x86_64.flatpak
flatpak run ai.storyteller.photocraft

Replace the first filename with the aarch64 bundle on ARM64. Review the installation prompt; a missing runtime can require an additional download. This command example is upstream guidance, not a build or installation test by this site.

Official sources: PhotoCraft README (opens a new tab) · Packaging documentation (opens a new tab).

Separate launch failures from document problems

Keep the distribution version, architecture, graphics driver, display session and package filename in your notes. AppImage and tarball users still need compatible system libraries and drivers; choosing a portable format does not remove those requirements.

If the app starts but dragging a file into it fails on Wayland, try File → Open. The official README documents that drag-and-drop limitation. A failed drop does not establish that the document format is unsupported.

If the window does not appear, retain the error text and search the official issues (opens a new tab) before changing graphics settings. After installation, test open, save and export with a small practice image; keep your original file separate.

Official sources: PhotoCraft README (opens a new tab) · Issue tracker (opens a new tab).