PhotoCraft Download: Every Installer, Verified

A PhotoCraft download is the project’s own release package, not a store listing. The v0.10.0 release carries twenty-four assets plus a checksum file: three Windows MSIs and three portable zips, one universal macOS DMG, Linux AppImage, deb, rpm, Flatpak and tar.gz builds for x64 and arm64, a FreeBSD tarball, a macOS CLI zip and the web build. Each file is an official artifact built by the project’s release pipeline.

The PhotoCraft binaries are large because PhotoCraft is a native Rust application with a GPU compositor. The macOS DMG is about 92 MB, the Windows MSIs run from 65 to 71 MB, and the Linux AppImage sits around 75 to 79 MB. Portable zips are bigger than the MSIs because they carry their own runtime layout. None of that is bloat for its own sake: the editor ships with fonts, shaders and the code paths for 16-bit and 32-bit colour.

What you do not get is an auto-updater inside the PhotoCraft app. PhotoCraft does not phone home for updates, so a PhotoCraft download is a version you keep until you replace it. If you want to know how to download PhotoCraft without that trade, the answer is the launcher, not a newer build. The ArtCraft Launcher exists to automate that, and it uses the same release assets. If you want updates without checking a releases page, install the launcher and let it handle the download for you.

On Windows, choose by architecture first. The PhotoCraft x64 MSI is the normal choice, arm64 MSI is for Snapdragon-class machines, and x86 is there for older hardware. The portable zip is the same build without an installer, useful on a locked-down machine or a USB stick. A PhotoCraft Windows install should not require a store account, and it does not.

On macOS there is one PhotoCraft download: a universal DMG that covers Apple silicon and Intel. It is signed and notarised, which means Gatekeeper should accept it without the right-click workaround. If you are on an older macOS release, check the project’s minimum version before you start a 92 MB PhotoCraft download that will not launch.

On Linux, pick the PhotoCraft package by how you maintain the machine. Debian and Ubuntu users take the deb, Fedora and openSUSE users take the rpm, and anyone who wants isolation takes the Flatpak. The AppImage is the portable option, and the tar.gz is for people who build their own launchers. For a PhotoCraft Mac or Linux download, architecture matters as much as format: aarch64 builds exist for ARM servers and Apple-adjacent Linux machines, and riscv64 packages exist for the curious.

Every PhotoCraft release ships a SHA256SUMS.txt file of about 2.6 KB, and the PhotoCraft download is only as trustworthy as that file. Download it next to the package, then run certutil -hashfile on Windows, shasum -a 256 on macOS, or sha256sum on Linux against the file you downloaded. Compare the output with the matching line in the checksum file. If the two strings differ, delete the file and download again from the release page.

A matching PhotoCraft hash means the bytes are the bytes the project published. It does not mean the code is safe, and it does not mean the app is stable; it means nobody swapped the file between the release and your disk. That is a narrower promise than antivirus marketing suggests, and it is the one that matters for an open-source download.

Where you got the PhotoCraft checksum matters too. Take SHA256SUMS.txt from the same release page as the package, not from a repost, a forum thread or a download site that offers its own “verified” copy. A checksum served by the same third party that serves the binary proves nothing. The release page is the only source this guide treats as authoritative.

Run the PhotoCraft MSI and Windows Installer handles the rest: a Start menu entry, an entry in Apps and features, and a normal uninstall path. SmartScreen may still warn about an unfamiliar publisher on a project this young, so check the file’s signature and the hash before you click through. If you took the portable zip, unpack it anywhere and run the executable; nothing is written to the registry.

The PhotoCraft installer does not bundle plugins or AI models, because PhotoCraft has neither. It also does not register a default file association for PSD in every build, so if double-clicking a PSD still opens Photoshop, set the association by hand. That is a preference, not a failure: plenty of people keep Photoshop as the default and open PhotoCraft deliberately.

Uninstalling PhotoCraft is the standard Windows path. Your files are not deleted, because PhotoCraft never owns your PSDs; it opens them and writes new ones when you save. If you keep presets, export them first, since an uninstall removes the application data folder alongside the program. The ArtCraft Launcher automates the same install and the same uninstall if you would rather not run MSIs by hand.

Open the DMG, drag PhotoCraft into Applications, and eject the disk image. The build is universal, signed and notarised, so the first launch should not need the Open Anyway dance. If macOS says the app is damaged, that usually means a quarantined download or an incomplete copy, not a broken release; check the hash and re-download before you change any security setting.

The PhotoCraft macOS build ships the same editor as Windows and Linux, with the same layers, masks and adjustment layers. The CLI zip on the release page is separate and only useful if you want to drive PhotoCraft from a script or an agent. Most people can ignore it, and a PhotoCraft download for normal use is the DMG.

Keep the DMG until the first save round-trips. Alpha software can fail on an unusual file, and having the installer beside you makes a reinstall a two-minute job rather than a re-download. That advice costs nothing and has saved more than one deadline.

Use the PhotoCraft deb on Debian and Ubuntu, the rpm on Fedora and openSUSE, and the Flatpak when you want the sandbox. The AppImage is the simplest portable route: make it executable and run it, with no package manager involved. The tar.gz is for people who prefer to place files by hand, and it is also the source of the Flatpak and AppImage builds.

Dependencies are the usual Linux variable. A minimal desktop may be missing a font package or a graphics library the GPU compositor expects, and the app will fail at launch rather than explain itself. Check the release notes and the repository issues before you conclude the build is broken; the same package usually works on a fuller desktop.

The FreeBSD tarball follows the same pattern with /usr/local as the target. If you are packaging PhotoCraft for a distribution, the tar.gz and the checksum file are what you want, and the licence allows redistribution as long as the notices travel with it and the ArtCraft marks do not.

There is a PhotoCraft download that installs nothing: the PhotoCraft web build. The v0.10.0 release includes an 11.4 MB zip of the WebAssembly build, and this site hosts the official copy so you can open it in a tab. The first load is about 11 MB, after which the editor runs locally in the browser and your PSD never leaves the machine.

The PhotoCraft web build is the same editor compiled for the browser, not a demo. In our Oct 18, 2026 test it opened a 1,200 × 800 PSD with six layers, showed the group and its children in the layers panel, and reported an RGB / 8-bit document at 100%. Saving downloads a copy of the file, because a web page cannot overwrite your original.

Use the web build to test compatibility before you commit to an install, or on a machine where you cannot install software at all. Use the desktop build when you need the signed installers, the CLI or native performance on large files, and read the ArtCraft Photoshop guide for the feature list behind the editor. Neither path is a PhotoCraft download that costs money; both are free, and both are the project’s own code.

The most common PhotoCraft download failure is a partial download. Large zips over a flaky connection can finish short, and the hash check is how you catch it. The second most common is the wrong architecture: an x64 MSI on an ARM Windows machine will run under emulation or fail outright, and the arm64 build is the right answer.

On macOS, a quarantined PhotoCraft DMG can produce a “damaged” warning that has nothing to do with the file. Check the hash first, then look at the quarantine attribute. On Linux, a missing library is more common than a corrupt package, and the terminal output usually names the library. On Windows, SmartScreen warnings are about publisher reputation, not malware, and the signature plus hash is the evidence to weigh.

If none of that explains it, read the PhotoCraft release notes for the version you downloaded. Alpha releases sometimes fix a packaging bug in the next build within a day, and the release notes say so plainly. Reporting a failure with the version, the platform and the exact file name is what makes the next fix possible.

Do not take a PhotoCraft download from a page that renames the file, wraps it in its own installer, or hides the repository. Those sites usually monetise the PhotoCraft download with bundled software or ads, and a renamed build is no longer the PhotoCraft package the checksum covers. The official path is short: GitHub Releases, getartcraft.com, or the launcher.

Be careful with “PhotoCraft for Mac” landing pages that offer a direct link without a version number. A download page that cannot say which release it serves is not tracking the project, and PhotoCraft ships often enough that a stale repost is a real risk. The same applies to APK-style repackages, to any site offering a “cracked” build of a free app, and to pages that promise a PhotoCraft installer for a platform the project does not ship.

If you only need to open a PSD once, you do not need a PhotoCraft download at all: the PSD viewer on this site opens layered files in the browser and exports PNG. If you want the full PhotoCraft editor, the PhotoCraft review covers what it can and cannot do before you spend the bandwidth on the PhotoCraft download.