Start 8 min
Get a real build
The official page offers a launcher and a wall of installers. This bench is the decision in front of that wall: which file, whether the browser is enough, and what to do when the window never appears.
Take them in this order
Start with Which PhotoCraft file to download if you are about to click a button. Read PhotoCraft in the browser if you wanted to avoid an install. Read When PhotoCraft will not open only after a real build is on the machine and it still will not open. If the window opens and then closes, read When the window closes or the canvas is slow. The language of the menus inside the app is Change the language inside PhotoCraft.
The download is not the edit
Once it opens, the next useful page is A first session you can undo. If the reason you installed it was a PSD, go straight to Open and save a PSD without losing the original before you save over that file.
Pick the kind of install before the filename
Five ways onto a machine show up in the project’s install guide, and they do not leave you in the same place. The ArtCraft Launcher installs PhotoCraft, chooses the build for the system and the processor, checks that build against SHA-256 checksums before it installs, and tells you when a newer public release exists. Use it when you want one updater and you are willing to let it manage the copy. A standalone file from Which PhotoCraft file to download is the path when you want PhotoCraft only. On Windows that installer is for your account by default and does not need an administrator. Everyone on this computer, on the first page of the installer, is the choice that asks for one. The guide says you can keep only one installed copy, so a switch means uninstalling first.
The portable zip runs without installing and keeps settings in PhotoCraftData next to the program. That is the file for a USB stick or a machine where you cannot install. macOS is the universal disk image, dragged to Applications, signed and notarized, for Apple silicon and Intel. Linux splits by format and architecture: AppImage, Flatpak, deb, rpm, Arch package, and tarball, with aarch64 beside x86_64, and riscv64 for deb, rpm, and the tarball. The RISC-V tarball wants glibc 2.39 or newer, as on Ubuntu 24.04. FreeBSD is a tarball laid out like /usr/local, and the install guide also names a FreeBSD aarch64 archive. Building from source is a sixth path, Rust 1.90 or newer, and it is not a substitute for the installer when you only wanted the app.
The browser is PhotoCraft in the browser. The zip unpacks onto a web server. Replacing that hosted copy means replacing the whole folder and then a hard refresh, so the browser does not keep the previous files from its cache. The source-code archive on the same GitHub release is not any of these builds.
How an update arrives, and what it does not send
PhotoCraft checks for a new version when it starts and tells you when one is out. The install guide says only public release information is requested, and nothing about you or your documents is sent. Help, then Check for Updates, runs the check when you want it. Edit, then Preferences, then General, holds Automatically Check for Updates. On a Mac the preferences menu is PhotoCraft, then Settings. Turn the checkbox off when a machine should not phone out at launch. The launcher has its own update notice and applies the new PhotoCraft for you.
An installer, a DMG, a deb, an rpm, or an Arch package updates by installing the new version over the old one. An AppImage updates with AppImageUpdate, or by downloading the new file. A Flatpak, a tarball, and the portable zip update by replacing the old files with the new ones. Settings live outside the application folder, except for the portable zip, so those updates keep them. Your images are not part of the uninstall either. Windows removes PhotoCraft from Settings, then Apps. macOS moves the app from Applications to the Trash. Linux uses the package manager, flatpak uninstall ai.storyteller.photocraft, or deleting the AppImage or the unpacked tarball. The portable zip is removed by deleting its folder. Settings remain in PhotoCraft’s settings folder until you delete that folder yourself. The log path on When the window closes or the canvas is slow is the clue to where that folder is.
Files on the release page that are not the app
SHA256SUMS.txt is the checksum list, and on Linux the release also carries signature files ending in .asc, including one for the checksum list. The install guide’s check is to import release-signing-key.asc from the release and verify the checksum file with GnuPG. A checksum match means the bytes arrived intact. It does not review the alpha status. The same guide tells you to ignore the other extras: symbol zips for Windows debugging, OCI manifest and signature files for container images, and zsync files used to download only the changed parts of an AppImage.
The command-line zip is not the windowed editor. On macOS it is a separate download. Repeat one job on a folder of files says where photocraft-cli lands after a normal install. The web zip is the self-hosted editor. A 32-bit Windows name in the written install guide is not, by itself, proof that the release you opened still ships that build. When PhotoCraft will not open is the page when the file you did run refuses to open, including --safe-gpu, a second instance, and a custom settings folder. The language of the menus after a successful start is Change the language inside PhotoCraft.