What operating systems does PhotoCraft support?
Current releases support Windows 10/11, macOS, Linux, FreeBSD, and Web through native packages or WebAssembly.
System requirements
PhotoCraft runs on Windows 10 and 11, macOS, Linux, FreeBSD, and the WebAssembly Web build. Official downloads are available for x64 and ARM64 systems across the major platforms, with additional Linux architectures in current releases. The project does not publish one universal minimum CPU, GPU, or RAM figure: large PSD/PSB files, high-bit-depth images, undo, smart filters, and scratch storage determine the practical requirement. Native builds use GPU compositing when a supported adapter is available and can recover through the CPU renderer, while the Web build is bounded by browser memory and does not support PDF import.

Use the desktop build for production, local files, PDF import, and hardware acceleration. Use the Web build for quick access where installation is impossible and the document fits browser memory. Compare Adobe Photoshop or GIMP when their published platform matrix or established ecosystem is a better fit.
| Editor | License | Platforms | Pricing | Platform and deployment | Best for |
|---|---|---|---|---|---|
| PhotoCraft Desktop | MIT OR Apache-2.0 | Windows, macOS, Linux, FreeBSD | Free | Native GPU compositing with CPU fallback and scratch-based memory management | Local production work, desktop input, PDF import, and the widest format support |
| PhotoCraft Web | MIT OR Apache-2.0 | WebAssembly in a browser | Free | No PDF import and no desktop GPU/tablet parity; practical file size depends on browser memory | Quick access when native installation is impossible and the required format is supported |
| Adobe Photoshop | Proprietary | Windows, macOS, iPad, Web | Subscription | Adobe publishes current system requirements and GPU compatibility for its own release | Users who need Adobe’s explicit hardware matrix, plug-ins, and production ecosystem |
| GIMP | GPL open source | Windows, macOS, Linux, BSD | Free | Mature general image editing with package-specific platform requirements | Users who need broad image manipulation and can use an existing GIMP installation |
Comparison reviewed 2026-11-13. Pricing and licensing can change; verify each vendor’s current terms before purchase.
PhotoCraft requires a supported 64-bit desktop operating system for native builds, a compatible graphics backend for best performance, and enough RAM plus scratch space for the actual document being edited.
The app is distributed for Windows 10 and 11, macOS on Apple silicon and Intel, Linux x86_64 and ARM64, FreeBSD, and Web. Windows also publishes x86 and ARM64 packages in current releases, while Linux includes additional architectures in selected release artifacts.
The project does not publish a single universal minimum RAM value. A small layered image can run comfortably where a very large PSB, many history states, smart filters, and 16/32-bit channels need substantially more working memory and scratch storage.
Yes. Current releases cover Windows, macOS, Linux, FreeBSD, and Web, with install formats that differ by platform.
Windows publishes MSI installers and portable ZIPs for x64, x86, and ARM64. macOS uses a universal DMG for Apple silicon and Intel plus a universal CLI archive. Linux publishes AppImage, Debian, RPM, Flatpak, and tarball packages across supported architectures. FreeBSD is distributed as a tarball laid out for `/usr/local`.
The Web build is a separate deployment choice. It shares the core engine but cannot provide desktop PDF import, native GPU parity across every browser, or the same memory headroom as a workstation application.
There is no published universal number. Size memory for the largest document and operation you intend to run, then verify scratch capacity before production work.
Decoded pixels, copy-on-write tiles, undo history, smart-object previews, filters, and export all consume memory. PSB documents and high-bit-depth layers increase the footprint further. The app uses bounded import paths and scratch storage, but it cannot make an undersized workstation equivalent to one with more headroom.
A practical test is to open a representative copy of the largest file, duplicate key layers, run the filters the workflow normally uses, undo and redo several times, and export the final result. Monitor available memory and scratch while doing so.
PhotoCraft records startup graphics state and attempts a safer backend or CPU renderer when a GPU process fails.
The app maintains a startup marker until the first frames render. A launch that finds a failed previous GPU attempt moves through a safer fallback: Vulkan to DX12 or CPU on Windows, Vulkan to GL or CPU on Linux, and Metal to CPU on macOS. A successful backend can be remembered; CPU recovery can remain for the session or become the preference.
Help › System Info shows the adapter, backend, driver, and fallback state. For one troubleshooting launch, `--safe-gpu` forces the CPU path. Do not install a new driver or change system settings before identifying which layer failed.
Source builds require stable Rust 1.95 or newer, the repository, and platform-specific desktop/windowing build dependencies.
On Linux, install xkbcommon, Wayland/X11, Mesa GL, and GTK development packages. On Windows, use the Rust MSVC toolchain with Visual Studio or Microsoft C++ Build Tools and the Desktop development with C++ workload. WebAssembly builds need the `wasm32-unknown-unknown` Rust target.
The desktop app, headless CLI, and Web target are separate packages under the same workspace. Following the documented build commands is more reliable than mixing dependencies from unrelated distribution packages.
The Web build uses browser memory, has no PDF import, and cannot guarantee desktop GPU, file-dialog, tablet, or operating-system integration parity.
WebAssembly is useful for quick access and simple editing, but very large layered documents can exceed practical browser memory. HEIC support is included in official native builds and depends on the deployed Web build configuration.
Use the native desktop build for large PSD/PSB files, RAW pipelines, PDF artboards, private client documents that should stay local, and hardware/tablet workflows that require desktop integration.
Confirm the official build, launch with the safe GPU path, inspect the PhotoCraft log, and test the same version on a known-good machine before changing unrelated system components.
Use the native desktop build for serious editing, PDF/RAW workflows, and larger files. Use Web only for quick access where native installation is impossible.
Current releases support Windows 10/11, macOS, Linux, FreeBSD, and Web through native packages or WebAssembly.
The project does not publish one universal RAM figure. Requirements depend on document dimensions, layers, bit depth, undo, filters, and export; test the largest representative file on the target machine.
A supported GPU enables native compositing, but the app has backend fallback and a CPU-renderer troubleshooting path on supported platforms. Performance and availability vary by driver.
Verify the build and architecture, try `--safe-gpu`, inspect the PhotoCraft log, and test a small document before changing drivers or system settings.
Yes. The documented desktop build requires Rust 1.95 or newer plus platform-specific windowing and compiler dependencies.
No. PDF import is available in the desktop build. The Web build has additional browser memory and platform-integration limits.
Download the desktop build, keep your source documents, and compare the layers and output against your current workflow.
We use primary vendor and project sources for product features, licensing, and platform claims. PhotoCraft-specific technical details come from its public repository and release documentation.