editing

export_photos

Render and export photos with all their edits to a folder.

What it does

By default exports every keep photo (including previously exported ones, re-rendered). Pass photo_ids to export a specific set instead, or status to export a different group. dest_dir is created if needed; inside it, files are grouped into a subfolder named after the source shoot folder, and the result lists the exact file paths written. Rendering is CPU-bound and can take seconds per RAW file; the result reports exported and failed counts with per-photo errors.

Parameters

NameTypeRequired
dest_dir str required
photo_ids list[int] | None optional
status str optional

Asking for it

You do not call this by name. You say what you want, and the agent picks the tool:

Apply the warm film look to every keeper in this folder and export JPEGs at quality 92.

The rest of the editing tools

list_presets apply_preset apply_adjustments get_photo_edits

Workflows that use it

Where it runs

On your machine. imagic's MCP server is a local process that your AI client starts; the photos never leave your disk and nothing is uploaded. That is true of every tool in the reference, including this one.

To call it you need an MCP client connected to imagic. Setup takes about three minutes for Claude Code, Cursor, VS Code, Codex, Gemini CLI and ten others.

Give your AI the whole pipeline

export_photos is one of 18 tools in imagic Max. The free 7-day trial includes all of them.