PhotoCraft for Mac: Universal DMG Download & Setup

Download the PhotoCraft Mac DMG

For the native app, download photocraft-0.12.0-macos-universal.dmg directly from the official storytold/photocraft release. This is the universal macOS disk image for PhotoCraft v0.12.0, distinct from ArtCraft Launcher. The release and filename were checked on 2026-10-22.

Use the matching release notes and SHA256 list. Check the published operating-system requirements before installing; a universal architecture label is not a guarantee of support for every macOS version.

Install and verify the file

For a local file, shasum -a 256 filename prints its SHA256; replace filename with the actual download path. Compare it with the entry for the same filename in that release's checksum list. Open the DMG and follow the installation instructions provided with the release, then launch the installed app. Check the stated signing and notarization status for that release rather than treating every build as identical.

If macOS reports an unknown publisher or cannot verify the app, stop and investigate the file and source. Do not disable system protections to follow this guide. A checksum verifies agreement with the published file, not a security certification. More detail is in the safety guide.

PhotoCraft or ArtCraft Launcher for Mac?

To manage several Crafting Apps, the separate download is artcraft-launcher-0.6.1-macos-universal.dmg, ArtCraft Launcher v0.6.1. It is not the PhotoCraft DMG above. Use its own release notes and own checksums instead of comparing files across products.

The download overview explains the app, launcher and browser choices. Their version numbers are independent.

How to update PhotoCraft on a Mac

Save your documents and quit PhotoCraft first. For a directly installed app, download the newer macOS package from upstream, verify it and follow that release's replacement instructions. Keep document backups and test a copy before removing a previous working version. For a Launcher-managed app, use the launcher's documented update flow; the launcher itself has a separate update mechanism. The update guide explains the cases.

Use the browser editor without a Mac download

Open the PhotoCraft browser workspace to try local image editing without installing. The hosted WebAssembly release remains v0.12.0 even when desktop downloads change. It has no browser autosave or crash recovery, so save before refreshing or switching renderers. Start with the usage guide and verify your own documents and exports before replacing a professional workflow.

Separate processor support from system requirements

A universal Mac package can contain code for more than one processor architecture. That label does not establish the minimum macOS version or that a specific plugin, graphics path or external device is supported. Check About This Mac for your hardware and macOS version, then compare those details with the chosen release's requirements. Keep the product and version in your installation notes.

This guide links upstream packages and describes checks you can perform. It does not claim a completed installation test on every Intel or Apple Silicon Mac. The verified browser workflow is a separate environment using the pinned web release. Installing a native application does not replace the JavaScript or WebAssembly files served by this website.

Inspect the application before first launch

The downloaded DMG is a container for the distribution, not the same thing as a saved document. Mount it and follow the included instructions for the application. If the release directs you to copy an app into Applications, finish that copy before treating the mounted disk image as a permanent installation location. Keep your images in a separate working folder.

For a trusted downloaded application, macOS provides signature and security assessment tools. codesign --verify --deep --strict --verbose=2 /path/to/Application.app checks a signature, and spctl --assess --type execute --verbose /path/to/Application.app asks for a security assessment. Replace the example with the actual path. These commands report information; they do not prove every aspect of an application's safety or override a warning.

If a result differs from what the release documentation says, stop and collect the exact output. Do not remove quarantine attributes or switch off Gatekeeper just to follow this article. A changed security state, different release or wrong product deserves investigation. The safety guide explains why a matching checksum alone cannot resolve every warning.

Check downloads and keyboard focus separately

A browser Save command can open Save Page rather than save the current image document. In the web editor, cancel that dialog and use the application's File menu. Command-key shortcuts depend on focus being inside the canvas; they are not a substitute for checking the downloaded file. The shortcut reference describes the pinned browser defaults and possible conflicts.

For both native and browser workflows, locate the saved image or working document in Finder, open a copy and confirm the intended edit. A preview thumbnail is not sufficient for a complicated handoff. Check dimensions, appearance and the editing features you need. Keep a separate reference export when exchanging a PSD with someone using another application.

Removing an app and keeping a recovery route

Quit the application before following its documented uninstall process. Removing an application bundle should not require deleting your original documents. Keep copies outside the application or mounted image and verify them before cleaning up downloads. Preferences and related data can live elsewhere, so do not claim that moving an app to Trash removes every associated record.

For a failed upgrade, retain the previous known-good package where licensing and your normal software process permit, together with documents saved before the upgrade. Reopen copies when comparing versions. A newly saved document can have its own compatibility changes, so replacing the app is not automatically a complete rollback. Record the exact version that produced each important output.

What to include when asking for help

Provide your macOS version, processor family, product, release tag and filename. Distinguish a failed download, a security warning, a startup failure and an editing defect. Include a sanitized screenshot or error message, not a private image or a full directory listing. Send website link errors to the maintainer and reproducible application defects through the upstream channels in the community guide.