Start · Download 10 min

Which PhotoCraft file to download

PhotoCraft is free and the builds are public. The hard part is the filename. The v0.23.1 assets on the official page are the set this table was checked against.

Option 1 · Recommended on the official page

Get PhotoCraft with the Launcher.

ArtCraft Launcher installs PhotoCraft, chooses the build for the computer, and updates it later. The official page currently points at launcher 0.19.2.

  • Every Crafting App
  • One-click updates
  • Verified downloads

Option 2 · Standalone

Just PhotoCraft? Download it standalone.

These files install PhotoCraft on its own. They are the v0.23.1 assets the official page linked on 21 November 2026. The written chooser is under the buttons.

Linux

Flatpak (x86_64)

Sandboxed. Install with flatpak install --user.

Download

photocraft-0.23.1-linux-x86_64.flatpak

Other files

FreeBSD

FreeBSD (x86_64)

The v0.23.1 product page says plain binaries for FreeBSD 15.1.

Download

photocraft-0.23.1-freebsd-x86_64.tar.gz

Package repositories (Flatpak, APT, and RPM)

Web

photocraft-web-0.23.1.zip

The web zip is the editor to host yourself. It is not the ArtCraft Studio app, and double-clicking the zip does not install PhotoCraft.

Release v0.23.1 SHA-256 checksums Release notes All releases

If a button no longer exists, open every release and use the asset list there.

Build from source

Run it today.

The product page asks for Rust 1.90 or newer. Install it with rustup, then run: rustup

git clone https://github.com/storytold/photocraft.git
cd photocraft
cargo run --release -p photocraft

View source on GitHub

Match the computer, then the package

Open the latest GitHub release or the downloads on the official PhotoCraft page. Both should point at the same project files. The product page also recommends the ArtCraft Launcher, from the launcher releases, when you want it to pick the build and later updates.

The names below are the pattern. Replace the version with the one on the release you opened. On 21 November 2026 the product page linked v0.23.1 and did not link a 32-bit Windows installer. The browser row points at PhotoCraft in the browser, which is a different choice from the desktop files.

Official filename pattern, checked against the v0.23.1 assets
Your computerTake this fileLeave this file
Most Windows 10 and 11 PCsphotocraft-<ver>-windows-x64.msiThe ARM64 build, and any 32-bit file from an older blog
Windows without an installer, or a USB stickphotocraft-<ver>-windows-x64-portable.zipThe Source code zip on the same release
Windows on ARM, such as a Snapdragon laptopphotocraft-<ver>-windows-arm64.msi or the ARM64 portable zipThe x64 MSI, unless you know the machine emulates it
Mac, Apple silicon or Intelphotocraft-<ver>-macos-universal.dmgA Windows MSI, or the CLI zip if you wanted the app
Linux on a typical PCThe x86_64 AppImage, Flatpak, deb, rpm, or tar.gzThe aarch64 build, unless the machine is ARM
Linux on ARM, Arch, or RISC-VThe matching aarch64 package, the .pkg.tar.zst, or the riscv64 archiveA package whose name does not include your architecture
FreeBSD x86_64 (v0.23.1 page: 15.1)photocraft-<ver>-freebsd-x86_64.tar.gzA Linux AppImage
A browser, nothing to installUse the web build described in the browser guidephotocraft-web-<ver>.zip if you only wanted to double-click it

Check the file you actually downloaded

Every release includes SHA256SUMS.txt next to the installers. Compare your download with the line for that exact filename. A match means the bytes arrived intact. It does not review the license or the alpha status for you.

On Windows, certutil -hashfile <file> SHA256 prints the hash. On macOS, shasum -a 256 <file>. On Linux, sha256sum <file>. The README describes the macOS app and CLI as signed and notarized, and the Windows installers and executables as code-signed. A signature is still worth a look in the system dialog, and the checksum is the check you can do yourself.

Stay on the project files

Do not take a PhotoCraft download from a software blog that rehosts the installer. Do not run the Source code archive as if it were the app. Building from source is a separate path: the repository shows git clone, then cargo run --release -p photocraft, and the product page has asked for Rust 1.90 or newer.

  • Launcher, if you want one updater for the Craft apps.
  • Standalone MSI, DMG, AppImage, Flatpak, deb, or rpm, if you want PhotoCraft only.
  • Portable zip, if you cannot install.
  • Then A first session you can undo, on a copy of a file.

What to do with the file after it matches

The table above picks the filename. The install guide says what that file does next. On Windows the MSI installs for your account and does not need an administrator, unless you choose Everyone on this computer on the first page. You can keep only one installed copy, so moving between those two choices means uninstalling first. The installers and programs are code-signed. The portable zip does not install. It keeps settings in a PhotoCraftData folder beside the program, which is also the way to carry it on a USB stick. On a Mac, open the universal disk image and drag PhotoCraft to Applications. That build runs on Apple silicon and Intel, and it is signed and notarized. The command-line tool is a separate macOS zip, covered with the other automation paths in Repeat one job on a folder of files.

On Linux, the AppImage runs without a package install. The first launch adds a menu entry under your local applications folder. Set PHOTOCRAFT_NO_DESKTOP_INTEGRATION to 1 if you want to skip that. The Flatpak installs with flatpak install --user and the file you downloaded. It needs the freedesktop runtime, and the flatpak command offers to install that runtime. You start it with flatpak run ai.storyteller.photocraft. A deb or rpm installs with the usual package tools. An Arch package installs with sudo pacman -U and the file. A tarball unpacks wherever you want it. Every one of those formats also has an aarch64 build. RISC-V has a deb, an rpm, and a tarball, and that tarball wants glibc 2.39 or newer, as on Ubuntu 24.04. Package repositories maintained for Flatpak, APT, and RPM are listed on the Linux downloads page. A Gentoo overlay published by the community, not by the PhotoCraft team, is snakebyte-overlay, package media-gfx/photocraft-bin.

FreeBSD uses the x86_64 tarball, or the aarch64 tarball on ARM. The install guide lays it out like /usr/local. Install the libraries it names, then unpack with strip-components into that prefix. The library line in that guide is pkg install of libxkbcommon, wayland, libX11, libXcursor, libXrandr, libXi, libxcb, mesa-libs, vulkan-loader, gtk3, fontconfig, freetype2, and alsa-lib. The v0.23.1 product page text says FreeBSD 15.1. The steps, the 32-bit Windows names included, are on Install and update. The v0.23.1 assets linked from the product page did not include a 32-bit Windows file, even though that guide still prints photocraft-<ver>-windows-x86.msi and a portable zip beside it. Trust the asset list on the release you opened.

Check it, then decide how it will update

SHA256SUMS.txt sits next to the installers. On Linux the release also includes .asc signatures, including one for the checksum list. Import release-signing-key.asc from the release, then verify SHA256SUMS.txt.asc against SHA256SUMS.txt with GnuPG. A match means the bytes arrived. It does not review the license or the early-alpha warning. Leave the symbol zips, the OCI image files, and the zsync files. They are debug symbols, container images, and the pieces AppImageUpdate uses. They are not the editor.

PhotoCraft checks for a new version at startup. 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 that check when you ask. Edit, then Preferences, then General, holds Automatically Check for Updates. On a Mac that dialog is PhotoCraft, then Settings. The launcher applies updates for you and checks the checksum before it installs. An installer, DMG, deb, rpm, or Arch package updates by installing the new version over the old one. An AppImage updates through AppImageUpdate, or by replacing the file. A Flatpak, a tarball, and the portable zip update by replacing the old copy. Settings are kept outside the app folder, except on the portable zip, where they live in PhotoCraftData. After the first successful window, the edit to try is A first session you can undo. If the window never appears, stay on When PhotoCraft will not open.