PhotoCraft GitHub: source code, releases & licenses

Find the PhotoCraft GitHub repository

The PhotoCraft GitHub repository is storytold/photocraft, maintained by the ArtCraft team and community. Start with the README to understand the editor, then check release notes and issues for the version you intend to use. The repository contains the Rust source, browser packaging and documentation.

Use GitHub releases for upstream build assets and version notes. To report a bug, include the PhotoCraft version, operating system, browser and a small reproducible example. Avoid attaching private documents to a public issue.

Permissive code, separate asset terms

PhotoCraft code is dual-licensed under MIT or Apache-2.0 at your option. Bundled fonts, icons and other third-party material have their own licenses. ArtCraft branding has separate trademark terms. This independent resource site does not claim official ownership.

The PhotoCraft ArtCraft guide explains the team and app family. For questions about Adobe, read the PhotoCraft and Adobe Photoshop comparison.

The exact browser build hosted here

This site serves the unmodified official v0.12.0 HTML, JavaScript and WASM release. The zip SHA256 is c2451e19bfd448de780d01a2dfc233924223a0020370af432c58c0c5ee9ec21e. Provenance, licenses and notices are linked below. The package is pinned for reproducibility, not automatically updated.

Identify the artifact, not just the project name

The browser application served here is a particular release package, not a live checkout of the upstream default branch. Record the repository owner, release tag and artifact filename when comparing it with another site or a desktop download. PhotoCraft's newer native packages have their own version history. A newer release page does not silently update the files hosted under this site's fixed vendor directory.

Start with the provenance JSON linked above. It identifies the release source and expected artifacts. The surrounding website code and localized guides are separate from the editor's HTML, JavaScript and WebAssembly. This distinction lets you report a broken website link without assuming that upstream changed the engine, and lets a software report name the application version actually being tested.

Inspect the retained license material

The editor is distributed under the upstream MIT OR Apache-2.0 licensing, with additional notices for third-party material. Read the actual license files and NOTICE rather than relying on the phrase “open source” as a complete redistribution policy. Licensing of code does not automatically grant every right to a brand name, image, font or unrelated application bearing the same name.

This website retains attribution and does not present itself as ArtCraft or Adobe. If you redistribute software, keep the relevant notices and comply with the license you use. If you publish your own editing examples, check your rights to the images as well. This guide explains where to inspect the source material; it is not a claim that every possible reuse has been legally reviewed.

Verify a downloaded hosted asset

Choose the exact HTML, JavaScript or WASM file identified in provenance. Download it without editing and compute its SHA256 using a trusted local tool. Compare the full digest with the matching artifact's expected digest. Do not compare a compressed transport body with the uncompressed file's digest: browsers and download tools may handle transfer compression differently. Compare the same representation on both sides.

A matching checksum shows agreement with the referenced bytes. It does not prove the absence of bugs or establish the security of every future upstream release. If a comparison fails, first check filename, version and whether the tool decoded compression. Preserve the result and ask the maintainer about a discrepancy instead of substituting a hash from an unrelated file or release.

Reproduce the small browser workflow

Use the synthetic PNG, edited PNG, saved PSD and reopened output linked from the PSD support guide. The test record reports the version, dimensions and observed pixel comparison for that input. The accompanying screenshots document the actual canvas. A screenshot by itself does not validate the exported file, which is why the sample includes both visible evidence and downloadable outputs.

The check exercises import, a brush change, PNG export and a simple PSD save/reopen. It does not open the file in Photoshop or test complex professional designs. When you cite this evidence, carry those limits with it. An honest small reproduction is more useful than turning one passing fixture into an overall compatibility score with no method behind it.

Distinguish code reading from runtime evidence

Source can establish that a command or parser implementation exists, but runtime behavior can depend on build options, browser support, graphics and the input. Documentation can describe an intended capability without proving that your particular document survives an exchange. Use explicit labels for what was read, what was executed and what remains unverified.

For a behavior that matters to your task, create a safe input, perform the operation and inspect the actual saved output. Include the software version and environment. If you cannot run the receiving application, say that its reopening behavior is unverified. Do not replace a missing runtime check with a stronger claim merely because the source repository contains a related module.

Send a precise provenance or licensing question

For a suspected artifact mismatch, include the page URL, vendor path, expected digest, observed digest and how the file was obtained. For attribution concerns, identify the relevant material and the license or rights information you believe is missing. Avoid including tokens, private browser data or unrelated request logs. The website contact handles the hosted copy and guides; upstream channels handle project development.

Keep your own task record with the release and input you used. That makes later comparisons possible even when upstream desktop links change. The source links are a starting point for independent checking, while our editorial policy explains how the website uses them alongside first-party workflow tests and clearly stated limitations.

The release also ships photocraft-cli, whose MCP server lets AI clients drive the same engine; the Photocraft MCP guide covers setup and security.