PhotoCraft the free, open-source photo editor
A practical starting point for PhotoCraft. Pick your platform, download the right official build, follow a short setup guide, then edit with keyboard habits that already feel familiar.
- Open sourceMIT / Apache-2.0
- NativeRust + GPU
- PSDLayered open and save
Duplicate a layer. Explore the complete shortcut guide.
Download PhotoCraft in 3 steps
Choose your platform below. If the operating system shows a warning, first confirm that the file came from the official GitHub release, then follow the platform-specific prompt.
Choose a download- 01
Choose your architecture for PhotoCraft
Most computers need
windows-x64.msi. Choose ARM64 for Snapdragon-based PCs, or the portable ZIP if you do not want an installer. - 02
Run the MSI
Double-click the file and follow the setup wizard. The project README states that the installer and executable are code-signed.
- 03
Test a copy of a PSD in PhotoCraft
Open a duplicate file first. PhotoCraft is early alpha, so do not overwrite your only production source file.
- 01
Download the Universal PhotoCraft DMG
The same package supports Apple silicon and Intel Macs. The official release is signed and notarized.
- 02
Move it to Applications
Open the DMG, drag PhotoCraft into Applications, then launch it there. macOS may perform an online notarization check on first launch.
- 03
Check your real workflow with PhotoCraft
Use duplicate files to test fonts, layer styles, PSD compatibility, and exports before moving production work.
- 01
Choose a PhotoCraft package format
AppImage is the general-purpose option. Use DEB for Debian or Ubuntu, RPM for Fedora or RHEL, or Flatpak for a sandboxed install.
- 02
Make the AppImage executable
chmod +x photocraft-0.6.0-linux-x86_64.AppImage - 03
Launch PhotoCraft
./photocraft-0.6.0-linux-x86_64.AppImageIf file drag-and-drop is unavailable on Wayland, use File → Open or copy and paste.
Recommended PhotoCraft builds at a glance.
Choose a common platform below for a direct official GitHub file, or open the dedicated download page for every package, checksum, and install command.
Need Windows ARM64, portable ZIP, DEB, RPM, Flatpak, Linux ARM64, or command-line tools? Open the complete download page.
What's the difference between PhotoCraft and Photoshop?
This comparison is meant to expose the tradeoffs, not choose for you. The PhotoCraft project describes v0.6.0 as early alpha.
Treat the table as a starting checklist rather than a universal verdict. Download both editors only when they fit your budget and device, then repeat the same small job in each one: open a layered file, adjust a mask, edit text, export the required format, close the document, and open it again. Record anything that changes. This simple trial reveals compatibility and workflow friction that a feature list cannot predict, while keeping your original project safely outside the experiment.
| Area | PhotoCraft v0.6.0 | Adobe Photoshop | Practical choice |
|---|---|---|---|
| License and cost | Open sourceMIT / Apache-2.0; free to use and study. The source can be inspected, forked, and adapted without waiting for a commercial roadmap. | SubscriptionProprietary software; the full desktop app requires a paid plan. That plan also pays for a mature support, update, and cloud-service ecosystem. | Start with PhotoCraft when budget, source access, or experimentation matters. Keep the subscription option when predictable vendor support is worth more than software freedom. |
| PSD workflow | SupportedOpens, edits, and saves layered PSD / PSB files. Because the project is early alpha, test advanced blending, text, masks, and effects with duplicate documents. | NativePSD is Photoshop's native format, so it remains the safer reference for unusual features, client handoffs, and round trips across established Adobe workflows. | Use PhotoCraft for controlled trials and everyday files, but keep Photoshop in the review loop when another person expects pixel-perfect or fully editable PSD delivery. |
| Layers and non-destructive editing | Layers, masks, adjustment layers, layer styles, smart objects, and filters cover many familiar editing patterns. Feature presence does not guarantee identical rendering in every imported file. | Photoshop offers deeper, more mature controls refined across long-running production workflows. Teams also benefit from shared conventions, training, and documented edge cases. | Build a small test set from your real work: portraits, mockups, composites, and exports. Compare the output before making either editor the default. |
| Generative AI | GapGenerative AI is listed by the project as a future direction, not a finished reason to switch today. Plan on conventional editing tools for current work. | MatureGenerative Fill, Expand, Harmonize, and other Firefly tools are integrated into the commercial workflow and receive ongoing service updates. | Choose Photoshop for time-sensitive AI production. Choose the open-source editor when transparent local tools matter more than assisted generation, then reassess as releases change. |
| Plugin ecosystem | PlannedPlugin compatibility remains a major acknowledged gap. A favorite retouching, export, or asset-management extension may have no equivalent yet. | MatureUXP, legacy plugins, and a broad marketplace support specialized work. Existing studios may already depend on those integrations for repeatable delivery. | List the plugins used in one normal week before switching. If a missing extension blocks a paid workflow, test the open-source app alongside the current stack instead. |
| Platforms | Windows, macOS, Linux, FreeBSD, and a self-hosted WebAssembly build are available. The download page separates installer, portable, package-manager, and developer choices. | The full desktop app focuses on Windows and macOS, with separate web and mobile experiences. Availability and feature depth can differ by device. | Linux and FreeBSD users have a clear reason to evaluate PhotoCraft. Windows and Mac users should choose based on workflow fit, not platform availability alone. |
| Offline use and accounts | Core tools work offline and do not require an account. That makes local testing simple and reduces dependence on sign-in or cloud availability. | Desktop editing can work offline, but installation, activation, subscription checks, and some connected services need a connection and an Adobe account. | Prefer PhotoCraft for an account-free local workflow. Prefer Photoshop when cloud services, shared libraries, and managed licensing are already part of the team's process. |
| Automation | StandoutUI, CLI, JSON control channel, and MCP share one command system. That architecture is interesting for scripted tasks and agent experiments. | Actions, scripting, plugins, and a mature third-party automation ecosystem cover many production needs. Existing examples and specialist tools lower adoption risk. | Explore PhotoCraft when you want to prototype CLI or agent-driven editing. Use Photoshop when a proven automation pipeline already saves time and reliably ships work. |
| Stability | Early alphaExpect rough edges, missing behavior, and compatibility issues. Save copies, preserve original files, and repeat important exports before trusting them. | Production-gradeA mature release process and broad professional use make it better suited to high-risk commercial delivery, though no editor is immune to defects. | Begin PhotoCraft with learning, personal projects, and non-critical work. Move higher-stakes jobs only after your own documents, hardware, and export formats pass repeatable checks. |
Explore the other Craft apps.
Open-source creative tools from the same ArtCraft family. Each row opens the project's official GitHub repository.