PhotoCraft

Open-source, local image editor built in Rust with layered PSD/PSB editing, GPU rendering, a command-driven CLI, JSON control channel and MCP server.

Developer ToolsOpen sourceSelf-hosted
Visit official website

Published Updated

CategoryDeveloper Tools
AccessSelf-hosted
PricingOpen source
APIAvailable
Overview

What is PhotoCraft?

PhotoCraft is an open-source, clean-room image editor written in Rust. It combines a native desktop interface with a shared command engine for layered PSD and PSB editing, masks, adjustment layers, smart objects, editable text, vector shapes, filters and color-managed workflows. The project reads and writes common raster and interchange formats alongside Adobe documents.

Read the full overview

Its architecture separates the document model, command registry and renderers from the interface. A CPU compositor provides a reference path while a GPU compositor built with wgpu targets Metal, Vulkan, DirectX 12 and WebGPU. Sparse image tiles and copy-on-write storage are intended to keep undo history and large-document edits manageable.

The same commands drive the desktop application, CLI, JSON control channel and MCP server. Developers can therefore inspect, transform and export assets without scripting mouse clicks. PhotoCraft remains early alpha: its maintainers do not present it as a complete replacement for mature professional Photoshop workflows. Read the ITHub technical analysis of PhotoCraft for the tested compatibility claims, architecture and current gaps.

Why teams use it

Key capabilities

  • Layered PSD and PSB workflowsOpen, edit and save documents containing groups, masks, adjustments, smart objects, effects, editable type and vector shapes. The project publishes corpus-based round-trip results, but production files still need direct testing.
  • Native CPU and GPU compositingA reference CPU renderer and a wgpu acceleration path make output comparison possible while supporting current native graphics backends.
  • CLI and batch executionRun the same registered editing commands outside the interface to convert folders, validate assets or create repeatable export pipelines.
  • MCP and local controlExpose explicit image operations to compatible agents through MCP or drive an authenticated local desktop session through the JSON control channel.
  • Broad format and color supportWork with PSD, PSB, PNG, JPEG, TIFF, WebP, SVG, OpenEXR and AVIF plus RGB, grayscale, CMYK and Lab documents at multiple bit depths.
  • Cross-platform packagesUse published builds for Windows, macOS, Linux and FreeBSD, or compile the engine to WebAssembly for supported experiments.
Core areas

PSD compatibility testing

Build a representative corpus, reopen and save each document, then compare both the rendered composite and editable layer structure. Keep originals for files that depend on plug-ins, unusual fonts or undocumented Adobe behavior.

Programmable creative pipelines

Use named commands for asset conversion, product screenshots, repeatable filter recipes and export validation. Pin the PhotoCraft release and compare outputs before updating an automated pipeline.

Local, inspectable editing

Keep document processing on the workstation and inspect the implementation when provenance, privacy or reproducibility matters. Resource-heavy documents should still be measured on the hardware that will run them.

Positioning

PhotoCraft is best evaluated as a local image engine with a capable editing interface and unusually strong automation surfaces. It fits Rust developers, open-source contributors, privacy-sensitive creative teams and engineers who need a scriptable PSD workflow.

It is not yet a drop-in migration target for studios that depend on proprietary Photoshop plug-ins, exact typography, mature generative features or established prepress processes. A sensible rollout starts with a folder of difficult production documents and a documented acceptance test, while retaining an established editor for unsupported cases.

Compared with browser-only editors, PhotoCraft emphasizes native execution and local control. Compared with mature commercial suites, it offers inspectable code and automation but carries the compatibility and support risk of a fast-moving early project.

Why it matters

Creative automation often relies on fragile interface macros or a collection of format-specific converters. PhotoCraft exposes document operations as commands shared by its UI, CLI and agent interfaces. That gives developers one testable surface for interactive edits and unattended jobs.

The project also treats PSD compatibility as something that can be measured with public corpora and renderer comparisons. Those results are project-published rather than a guarantee, but the available tests give engineering teams a better starting point than a general claim of file support.

Evaluate it where local processing, repeatability and source access outweigh ecosystem maturity. Validate document fidelity, fonts, color management, memory use and export output before placing it in a production path.

Deployment & technical details

Technical details

Access
Self-hosted
Source model
Open source
Founded
2026
Pricing model
Open source
API
Available
Published release
Latest GitHub release checked October 9, 2026 v0.5.0 ↗ (checked )
Source check
Primary source ↗ checked
Check with the publisher

Official resources

Before you shortlist

What to verify for your environment

Profile audiences: Developers.

  • Confirm current features, licensing and support terms with the publisher.
  • Validate deployment, data location, access control, backup and recovery requirements.
  • Test integrations, export paths and a representative operational workflow before committing.
Community experience

Reviews of PhotoCraft

No published reviews yet.

Loading review form…