Can PhotoCraft open Photoshop ATN files?
Yes. It loads version 16 ATN action sets and shows mapped commands plus preserved unsupported steps.
Photoshop Actions guide
Yes, with explicit limits. PhotoCraft loads and saves version 16 Photoshop `.atn` action sets, maps many recorded events to native commands, and can play actions in the desktop UI, batch mode, CLI, and automation surfaces. A mapped event saves back as the same Action event. An unsupported event is preserved as a kept step; playback stops before an enabled kept step rather than silently skipping work. This makes PhotoCraft useful for testing and adapting existing Actions, but it is not a guarantee of complete Adobe Action, plug-in, or future-feature compatibility.

Photoshop remains the reference for complete Action behavior and Adobe ecosystem compatibility. PhotoCraft is a free route for testing and running supported ATN events with explicit kept-step failures. GIMP and Affinity automate native scripting or macros rather than providing general Photoshop ATN playback.
| Editor | License | Platforms | Pricing | Action compatibility | Best for |
|---|---|---|---|---|---|
| PhotoCraft | MIT OR Apache-2.0 | macOS, Windows, Linux, FreeBSD, Web | Free | Loads/saves ATN sets, maps many recorded events, preserves unsupported steps, and can batch-play actions | Testing supported Photoshop Actions locally with visible kept-step failures |
| Adobe Photoshop | Proprietary | Windows, macOS, iPad, Web | Subscription | Reference Action implementation with complete Adobe commands, plug-ins, Camera Raw, and ecosystem behavior | Actions that depend on Adobe-only commands, plug-ins, newer features, or guaranteed full playback |
| GIMP | GPL open source | Windows, macOS, Linux, BSD | Free | Script-Fu, Python, and GIMP plug-ins rather than native Photoshop ATN playback | Automation built specifically around GIMP scripting and its plug-in ecosystem |
| Affinity Photo | Proprietary | Windows, macOS, iPad | Free with a Canva account; optional Canva AI plan | Affinity macros automate Affinity-native commands; Photoshop Actions require conversion or recreation | A polished non-Adobe editor when the automation can be rebuilt as an Affinity macro |
Comparison reviewed 2026-11-13. Pricing and licensing can change; verify each vendor’s current terms before purchase.
Yes. PhotoCraft loads version 16 Photoshop ATN action sets through the Actions panel, automation commands, and batch processing.
The file is parsed into action sets, actions, and steps. Supported events become PhotoCraft commands; unsupported steps are retained as `actions.photoshopStep` records so the original action data is not destroyed.
Loading an Action is not the same as claiming every step runs. Read the imported kept-step indicators before pressing Play.
Select the target layer or document, choose the action, and press Play. Supported steps execute as native commands while enabled kept steps stop the run.
Actions create one history entry named after the action by default, with an option for per-step history. Step-by-step and pause modes are available in the UI; batch, CLI, and automation play at once.
A failure or Stop step keeps the completed prefix. This preserves recoverability and makes partial application visible instead of pretending the whole action succeeded.
Mapped coverage includes common adjustments, selections, layer operations, filters, smart objects, type/shape commands, batch steps, and many newer string-ID events.
Examples include Curves, Levels, Hue/Saturation, black-and-white, selective color, gradient map, layer and group creation, masks, smart objects, Gaussian and other filters, Camera Raw Filter, Select Subject, Content-Aware Fill, Perspective Warp, image size, crop, save/export, and supported batch forms.
The compatibility reference should be checked for the exact event. Some mapped events can still lose settings that PhotoCraft has not represented, while changed native forms may refuse export to the original ATN shape.
Unsupported enabled steps remain kept steps. Playback stops at that point and reports the step instead of skipping it silently.
A kept step with no document effect, such as a tool-selection record, is imported switched off so it does not unnecessarily block playback. Other kept steps must be reviewed, removed, or replaced with an equivalent PhotoCraft command.
Plug-in calls, unsupported future events, and incompatible dialog forms are common reasons for a kept step. PhotoCraft cannot execute an Adobe plug-in that is not part of its own engine.
Yes. PhotoCraft can save Action sets back in the ATN format, preserving supported mapped events and kept unsupported steps.
The file format support is separate from behavioral parity. A mapped command can save back as the corresponding event, while a changed native command that has no representable ATN form may be refused rather than written incorrectly.
Keep the original ATN source and test the saved Action in both PhotoCraft and Photoshop when cross-application use matters.
Yes. `photocraft batch --actions set.atn` applies a supported Action set across files, and automation can expose action playback through the same engine.
Batch jobs need more than a Play button: define input discovery, output naming, collision handling, error logs, progress, cancellation, and rollback. PhotoCraft’s batch surface supports folder behavior and failure reporting, but the workflow must still be tested with the exact Action.
Use a representative fixture set containing the largest files, unusual modes, missing assets, and expected failures. Keep the source files read-only and validate every output.
An Action normally creates one grouped history state. Step-by-step, pause, Stop, and message behavior are represented, with completed work retained when a run stops.
Nested plays share the outer Action history entry by default. A failed or Stop step keeps the steps already applied. Intervening edits or a document switch prevent a stale paused dialog from being applied to the wrong history state.
For unattended runs, Allow Continue controls whether a message step proceeds or fails under the engine’s rules. Interactive dialogs should be converted to deterministic behavior before batch use.
Test PhotoCraft when the Action uses supported native events and you want a free local workflow. Keep Photoshop when the Action depends on Adobe-only commands, plug-ins, or guaranteed complete playback.
Yes. It loads version 16 ATN action sets and shows mapped commands plus preserved unsupported steps.
No. PhotoCraft maps many events but not the complete Adobe feature or plug-in surface. An enabled unsupported step stops playback.
A kept step is an Action event PhotoCraft cannot map to a native command. It is preserved in the file and can stop playback instead of being silently skipped.
Yes, for representable Action sets. The original ATN and a Photoshop cross-check should be kept when interoperability matters.
PhotoCraft provides `photocraft batch --actions set.atn` and automation playback for supported Actions. Test file handling, errors, and output validation first.
No general Adobe plug-in compatibility is claimed. An Action that depends on an unavailable plug-in or Adobe-only command should remain in Photoshop until adapted.
Download the desktop build, keep your source documents, and compare the layers and output against your current workflow.
We use primary vendor and project sources for product features, licensing, and platform claims. PhotoCraft-specific technical details come from its public repository and release documentation.