Photoshop alternatives, compared for real editing work

Most “best alternative” lists optimize for the widest feature count. That is not the same as the best daily editing experience. A former Photoshop user should test selection tools, layer styles, type editing, color management, smart objects, and PSD round trips before deciding.

PhotoCraft implements those workflows in Rust and exposes the same command engine through its desktop interface, CLI, JSON control channel, and MCP server. It is available on macOS, Windows, Linux, FreeBSD, and Web, while GIMP and Krita have different interface models and Photopea requires a browser.

• PhotoCraft: MIT OR Apache-2.0, native compositor, familiar layers-and-tools model, and layered PSD read/write.
• GIMP: long-established GPL editor with broad image-manipulation coverage and a different interface and scripting model.
• Krita: painting-first GPL application with strong brush and illustration tools rather than a Photoshop panel-for-panel clone.

A PSD can contain groups, masks, smart objects, type, adjustment layers, layer styles, shapes, patterns, and metadata. “Supports PSD” is therefore too broad to be useful. Test a representative file and inspect whether the features you edit survive an open-save-open cycle.

PhotoCraft’s current upstream corpus re-saves with matching renders for 307 of 309 psd-tools test files and 169 of 170 mixed ag-psd/psd-tools files. That is a strong engineering signal, not a guarantee for every document. The project explicitly notes that re-saved files are not byte-identical because image resources, layer records, and the composite are rewritten.

Photopea’s main advantage is immediacy: open a tab and edit without installing software. That is valuable on managed machines or when you need occasional access. It is less suitable when you want the entire workflow to stay local or when the editing session is limited by browser resources.

PhotoCraft’s desktop builds use a native wgpu compositor across Metal, Vulkan, DX12, and WebGPU backends. Its open-source code also allows teams to inspect the implementation, build it themselves, and control deployment.

• Open and re-save your most complex PSD or PSB file, then compare the visible composite and editable layers.
• Check the color model and bit depth: RGB, CMYK, Lab, Grayscale, and 8/16/32-bit documents behave differently across editors.
• Verify font substitution, smart filters, masks, clipping paths, and layer effects before replacing an established pipeline.
• Run a complete project on the alternative while keeping Photoshop available for rollback.

Offline operation is a document-control question, not only a connectivity question. A creative team may need to know where source files are stored, whether a service receives uploaded images, which account or license check is required, and whether the editing application remains available during an outage.

PhotoCraft’s desktop builds run the document engine locally. Its source code and release artifacts can be retained for rollback, and the shared command engine is available without a cloud document service. That does not replace the rest of a team’s security review, but it gives organizations a more inspectable base than a closed browser editor.

A pilot also exposes workflow costs that product pages rarely mention: shortcut retraining, asset-library migration, batch-script changes, font licensing, and how technical support responds to a blocked file. A small trial produces better evidence than asking a team to switch on the first day.

• Choose five files that cover layers, masks, type, smart objects, adjustment layers, CMYK or high-depth color, and the largest document size in production.
• Record the software, fonts, color profiles, input devices, and export settings required to reproduce the work.
• Compare rendered output and the editable layer state after a round trip through each candidate editor.
• Assign one owner for release updates and one documented rollback version before removing the current application.

Do not switch a team because a comparison table says one product “wins.” Run a controlled file and workflow test. The right answer is the editor that preserves your files, supports your required output, and leaves the least friction in repeated daily work.