PhotoCraftPhotoCraft

Photoshop Actions guide

Can PhotoCraft run Photoshop Actions?

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.

By the ArtCraft maintainers12 min read
Physical layer cards moving through a precise automated transformation line toward a finished image stack
Action compatibility is event-by-event. A file can load successfully and still stop when it reaches an event PhotoCraft has not mapped.
01 / Comparison

Which application should run your Photoshop Action?

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.

Which application should run your Photoshop Action?
EditorLicensePlatformsPricingAction compatibilityBest for
PhotoCraftMIT OR Apache-2.0macOS, Windows, Linux, FreeBSD, WebFreeLoads/saves ATN sets, maps many recorded events, preserves unsupported steps, and can batch-play actionsTesting supported Photoshop Actions locally with visible kept-step failures
Adobe PhotoshopProprietaryWindows, macOS, iPad, WebSubscriptionReference Action implementation with complete Adobe commands, plug-ins, Camera Raw, and ecosystem behaviorActions that depend on Adobe-only commands, plug-ins, newer features, or guaranteed full playback
GIMPGPL open sourceWindows, macOS, Linux, BSDFreeScript-Fu, Python, and GIMP plug-ins rather than native Photoshop ATN playbackAutomation built specifically around GIMP scripting and its plug-in ecosystem
Affinity PhotoProprietaryWindows, macOS, iPadFree with a Canva account; optional Canva AI planAffinity macros automate Affinity-native commands; Photoshop Actions require conversion or recreationA 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.

02 / Direct answer

Key takeaways

  • PhotoCraft loads and saves ATN action sets through its Actions panel and automation interfaces.
  • Many common adjustment, selection, filter, layer, smart-object, and export events map to native commands.
  • Unmapped enabled steps stop playback so work is never silently omitted.
  • Batch and CLI playback are available after testing the exact action and representative files.
  • Keep Photoshop for Actions that depend on Adobe-only commands, plug-ins, or guaranteed newer features.
03 / Photoshop Actions guide

Can PhotoCraft load Photoshop Actions?

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.

  • Load ATN through the Actions panel.
  • Load through automation/agent commands.
  • Use an action set with `photocraft batch --actions set.atn`.
  • Review unsupported kept steps before playback.
04 / Photoshop Actions guide

How do you play an imported Action in PhotoCraft?

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.

  • Inspect the target layer, selection, and document mode first.
  • Read tooltips/descriptions for kept steps.
  • Test on a duplicate of a representative source file.
  • Use the history prefix and undo to recover from a stopped run.
05 / Photoshop Actions guide

Which Photoshop Action events does PhotoCraft map?

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.

  • Adjustment and color commands.
  • Selections, masks, and layer organization.
  • Filters, smart objects, and recorded transform steps.
  • Type, shape, export, and supported automation events.
06 / Photoshop Actions guide

What happens to unsupported Action steps?

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.

  • Kept step remains visible in the action.
  • Enabled kept step stops playback.
  • Save Actions writes the kept step back unchanged.
  • The exact missing event should drive the remediation decision.
07 / Photoshop Actions guide

Can PhotoCraft save edits back to an ATN file?

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.

08 / Photoshop Actions guide

Can PhotoCraft run Actions in Batch or from the CLI?

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.

  • Pin a PhotoCraft version and action set.
  • Test all mode and layer prerequisites.
  • Capture per-file failures and kept-step stops.
  • Write to a new destination with resumable naming.
  • Validate output before unattended use.
09 / Photoshop Actions guide

How does PhotoCraft handle Action history and Stop steps?

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.

10 / Photoshop Actions guide

Should you replace Photoshop to run Actions?

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.

FAQ

Questions people ask before switching

Can PhotoCraft open Photoshop ATN files?

Yes. It loads version 16 ATN action sets and shows mapped commands plus preserved unsupported steps.

Will every Photoshop Action run perfectly in PhotoCraft?

No. PhotoCraft maps many events but not the complete Adobe feature or plug-in surface. An enabled unsupported step stops playback.

What is a kept Photoshop step?

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.

Can PhotoCraft save Actions back to ATN?

Yes, for representable Action sets. The original ATN and a Photoshop cross-check should be kept when interoperability matters.

Can I batch-process files with a Photoshop Action?

PhotoCraft provides `photocraft batch --actions set.atn` and automation playback for supported Actions. Test file handling, errors, and output validation first.

Does PhotoCraft support Adobe plug-ins used by Actions?

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.

Open source · Free

Try PhotoCraft on your own files.

Download the desktop build, keep your source documents, and compare the layers and output against your current workflow.

Sources and further reading

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.

  1. PhotoCraft source code and documentation
  2. PhotoCraft v0.23.1 release, formats, and checksums
  3. PhotoCraft Photoshop Action compatibility reference
  4. Adobe Photoshop official product page