Download the PHP package spacecatninja/ai-image-editor without Composer

AI Image Editor for Craft CMS

Edit and generate image assets in the Craft CMS control panel using natural language, powered by AI.

Open any image asset and tell the editor what you want in plain words — "make the background white", "remove the coffee cup", "make it look like golden hour" — then iterate in a chat-style loop until it's right and save the result, either as a new asset or back over the original. Need an image that doesn't exist yet? Describe it and generate one from scratch. No fixed one-click filters, no round-trips to a desktop editor, no leaving Craft.

Requirements

• Craft CMS 5.0+
• PHP 8.2+
• An API key for at least one supported provider — Google Gemini, OpenAI, Black Forest Labs (FLUX), or xAI (Grok). Bring your own key; requests go directly from your server to the provider.

Installation

To install the plugin, either install it from the Plugin Store, or follow these instructions:

1. Install with Composer via composer require spacecatninja/ai-image-editor from your project directory.
2. Install the plugin in the Craft Control Panel under Settings → Plugins, or from the command line via php craft plugin/install ai-image-editor.
3. For the plugin work, you need to configure at least one driver and verify the connection with php craft ai-image-editor/test-connection. But first, read on!

Highlights

• Natural-language editing, inside the control panel. Free-form instructions in a chat-style composer — not a fixed set of one-click filters. Editors never leave Craft, and never round-trip through a desktop image editor.
• Generate images from scratch, too. Beyond editing existing assets, describe an image in words and the plugin creates it as a new asset — straight from an asset index or an asset-selection modal.
• Iterate cheaply, finalize sharp. Turns run as fast, low-resolution drafts while you refine the look; the full-resolution version is rendered only once you accept, with a side-by-side draft/final comparison so nothing changes behind your back.
• Bring your own AI provider. Four drivers ship in the box — Gemini, OpenAI, FLUX, and Grok — chosen in config and switchable per session. Requests go directly from your server to the provider with your own API key, and other plugins can register more drivers.
• Built to stay faithful. A "Precise edits" mode, multi-turn provider chaining, and automatic aspect-ratio pinning combine to change only what you asked for and stop quality from drifting across successive edits.
• Feels like part of Craft. Reuses the native image-editor interface and its two save actions — replace the original in place, or save as a new sibling asset — respects your volume permissions, auto-detects focal points, and names generated files from an AI description of what's in them.
• Ready for content-disclosure rules. An optional field flags every AI-edited or -generated asset so you can meet AI-labeling regulations, and it pairs with Imager X when you need a watermark burned into the pixels.
• Cloud- and cluster-friendly. Works unchanged on Craft Cloud and on load-balanced or ephemeral filesystems — working images live in Craft's temporary filesystem, never a hardcoded local path.
• Configured as code. No settings screen to click through: everything lives in config/ai-image-editor.php, so it's versioned and multi-environment by default.
• Extensible. Before/after events on every edit and save let you observe, adjust, or veto them, and you can register custom drivers for other providers.

How it works

• Edits during the chat loop are performed at the configured working resolution (default 1K). These are the draft versions: cheap and fast, good enough to judge whether an edit is right.
• When you accept the result, the last accepted draft is regenerated once at the final resolution (default 2K) before it's saved as an asset. (Drivers with a single resolution tier, like OpenAI, skip this and save the draft directly.)
• Note: the finalize step is a generative regeneration, not a pixel-preserving upscale. The editor shows a draft/final comparison so you can catch drift, and lets you save the draft instead if the final version isn't faithful.
• Like the native image editor, there are two save actions: Save replaces the original asset's file (the asset and its relations stay intact, requires the "Replace files" volume permission), and Save as a new asset creates a sibling asset in the same folder (requires the "Save assets" volume permission).
• Intermediate results are never Craft assets. They live in Craft's temporary filesystem and are purged when a session is finalized, discarded, or abandoned (see Craft Cloud and ephemeral filesystems).
• In both cases the file is named {original-basename}-edit-{timestamp}.{ext}. If the original already has an edit suffix, it's replaced rather than stacked, so re-editing doesn't compound it.
• As part of saving, the image's focal point is detected and set on the asset before it's created, so transforms anchor to the subject from the first render. Assets that already have a focal point keep it. Disable with 'autoFocalPoint' => false.
• If you set aiGeneratedField to the handle of a lightswitch field on your asset volumes, that field is switched on for every asset the plugin edits or generates (including replaced originals), giving you a durable, queryable flag to mark AI-touched images. See Marking AI-generated content.

Generating new images

Besides editing existing assets, the plugin can create images from scratch. A Generate button appears next to the upload button on asset indexes (for users who can save assets in the volume) and inside asset selection modals. It opens the same editor without a source image: describe what you want, iterate in drafts, and accept to save. Generated assets land in the folder that was selected in the index, named after an AI description of the image (e.g. golden-retriever-on-a-beach.png), falling back to the first prompt. Since there is no original, only "Save as a new asset" is offered.

Reducing content drift

Generative editing can change more than you asked for. The plugin does several things to keep edits faithful:

• The "Precise edits" toggle in the editor (on by default) appends content-preservation instructions to every prompt, telling the model to change only what was requested. Turn it off for deliberately creative edits, or tune the wording with the preserveInstructions setting.
• On providers that support it (currently Gemini, via interaction chaining), consecutive edits reuse the provider's multi-turn state instead of re-uploading the previous result, so quality loss doesn't compound across turns. The stateless drivers (OpenAI, FLUX, Grok) re-send the current working image each turn instead.
• The output aspect ratio is pinned to the source image's, preventing recomposition. For deliberate ratio changes ("crop this to a square"), pick a ratio in the editor's aspect ratio dropdown instead of relying on the prompt, the default "Match original" follows the current working image.

If simple edits still drift, you can change to more advanced models or adjust the fidelity knobs per driver (Gemini's 'thinkingLevel', OpenAI's quality, FLUX's safetyTolerance, to name a few).

Drivers

Four drivers ship with the plugin, selected with the driver setting:

• gemini: Google's Gemini image models. Model aliases nano-banana-pro (gemini-3-pro-image) and nano-banana-2 (gemini-3.1-flash-image), resolution tiers up to 4K, 10 aspect ratios, and multi-turn interaction chaining for low-drift iteration.
• openai: OpenAI's GPT Image models (gpt-image-2, gpt-image-1.5, gpt-image-1-mini). Output tops out around 1.5K, so a single 1K tier is exposed and accepting a result saves directly without a regeneration step. Three aspect ratios (1:1, 3:2, 2:3). The "Precise edits" toggle maps to the API's input_fidelity parameter in addition to prompt instructions. Turns are stateless (no chaining).
• flux: Black Forest Labs' FLUX.2 models (flux-2-pro, flux-2-flex), which do both editing and text-to-image generation at up to ~4MP, so 1K and 2K tiers are exposed. Stateless turns. The API is asynchronous (the plugin submits, polls, and downloads the result behind the usual spinner). FLUX has no vision model, so set analysisDriver to gemini or openai if you want focal point detection and descriptive filenames.
• grok: xAI's Grok Imagine models (grok-imagine-image, grok-imagine-image-quality), doing both editing and text-to-image generation at 1K and 2K. Stateless turns. Grok has its own vision model (grok-4.5), so it handles the analysis tasks in-provider, no analysisDriver needed. The output format is chosen by the API, so no format tier is offered.

The gemini, openai and grok drivers also handle the analysis tasks (focal point detection, descriptive filenames) with their provider's vision models, configurable via each driver's analysisModel key. flux has no vision model, so it relies on analysisDriver (below).

Additional drivers can be registered by other plugins through the EVENT_REGISTER_EDIT_DRIVERS event (see Extending). They read their own configuration from driverConfig[handle], so a third-party driver gets typed-free settings without touching the core config, and the simplest ones can extend spacecatninja\aiimageeditor\drivers\BaseEditDriver to inherit config reading, credentials, prompt building, and the analysis wrappers.

Configuration

There is no control panel settings screen. All configuration is done in config/ai-image-editor.php, using Craft's standard multi-environment config format:

Root settings

The root of the config holds the driver selectors and cross-cutting settings; each driver's own settings live in its driverConfig block (below).

Quick actions (presets)

Presets are one-click chips shown above the composer for common edits. Each entry needs a label and a prompt; precise is optional and overrides the "Precise edits" toggle for that action (use true for faithful edits like background removal, leave it off for creative restyles). Clicking a chip runs a normal edit turn with that prompt, and leaves any text you've typed untouched.

Per-driver settings (driverConfig)

driverConfig is keyed by driver handle. Only the keys you set override that driver's defaults, so a block with just apiKey is enough to get started. Any driver, bundled or third-party, reads its config from here. The overridable root settings can also be set here to override their global value for a single driver (see the last three rows).

After configuring, verify the setup from the command line:

Splitting analysis from editing

Analysis (focal point detection, descriptive filenames) needs a vision-language model, which not every image-editing provider has. By default it runs on the same provider as editing, but the analysisDriver setting decouples them: set driver to an edit-only provider and analysisDriver to one with a vision model, and analysis still works. For example, the FLUX driver has no vision model, so pair it with Gemini:

When analysisDriver names a different provider, remember it needs its own API key in its driverConfig block. php craft ai-image-editor/test-connection verifies both providers.

Marking AI-generated content

A growing number of jurisdictions require content that was generated or manipulated by AI to be disclosed as such. The EU AI Act's transparency obligations (Article 50), China's labeling rules for AI-generated content, and a wave of US state laws (such as California's AI Transparency Act) are all examples, with more on the way. What must be marked, how, and from when varies by jurisdiction and by how the image is used — so treat the field below as a building block, not legal advice. Whether and how you need to disclose is your responsibility to determine, ideally with counsel; the plugin does not make your site compliant on its own.

The aiGeneratedField setting gives you that building block. Point it at the handle of a lightswitch (boolean) field in your asset volumes' field layouts, and the plugin switches it on for every asset it edits or generates — including originals replaced in place via Save. Because it's an ordinary Craft field, the flag is durable, queryable, and yours to act on however the rules require, for example:

• Show a visible disclosure next to the image on the front end — a caption, badge, or "Generated with AI" label — by checking the field in your templates.
• Filter or report on AI-touched assets, e.g. an element index source or a query like craft.assets.isAiGenerated(true) for audits (using your field's handle).
• Feed provenance/metadata pipelines your own code drives on save (IPTC fields, C2PA manifests, alt-text notes, and so on).

The plugin only ever flips the field on; how it's surfaced, exported, enforced, or combined with other signals is entirely up to you.

Burning in a visible watermark. When you need a watermark composited into the pixels rather than a separate on-page label, Imager X can add one as part of a transform via its watermark parameter — a watermark image plus width/height, and optional position, opacity, and blendMode. Drive it off the aiGeneratedField flag so only AI-generated assets are marked (assuming the field's handle is isAiGenerated):

Imager X watermarking runs on the local GD/Imagick transformer.

Craft Cloud and ephemeral filesystems

An edit session spans several requests (each turn, finalize, and save is a separate request), so the working images have to survive between them. The plugin keeps them in Craft's temporary filesystem (craft\fs\Temp), resolved through the container — so on Craft Cloud they're stored in the environment's private, object-storage-backed temp area, and on a load-balanced setup they're shared across instances. Nothing is written to a hardcoded local path, and this storage is not an asset volume filesystem, so a volume re-index never picks up the transient files.

These files are genuinely temporary: they're removed as soon as a session is finalized, discarded, or purged (purgeSessionsAfterHours, default 48). If the platform's temp storage is reclaimed sooner, the worst case is a "start a new session" message on the next turn — no data is lost, since finished results are saved as normal Craft assets.

Privacy

Images and prompts are sent to the AI provider(s) you configure — the edit driver, plus the analysis driver when you've set a separate one — for processing. Make sure this is acceptable for your project's data-handling obligations before enabling the plugin. The editor shows a note naming the provider(s) at the point of use.

Extending

Additional providers can register edit drivers through the EVENT_REGISTER_EDIT_DRIVERS event:

Drivers implement spacecatninja\aiimageeditor\drivers\EditDriverInterface.

Lifecycle events

Four events let you observe, adjust, or veto edits and saves:

EditEvent carries the session, the request (mutable), the result (on the after event), and isValid. SaveEvent carries the session, the asset, a replace flag, and isValid. Set isValid = false in a "before" handler to cancel.

Permissions

The plugin registers two user permissions under an "AI Image Editor" group, assignable per user group:

• ai-image-editor:edit — open the editor on an existing image and run edits.
• ai-image-editor:generate — generate brand new images.

These gate the editor's entry points and endpoints; the volume permissions (saveAssets, replaceFiles) still gate the actual save. Reference the handles from SessionsController::PERMISSION_EDIT / PERMISSION_GENERATE.

Support

Found a bug or have a feature request? Open an issue on the issue tracker. For anything else, email [email protected].

License

This is commercial software. See LICENSE.md. A license can be purchased through the Craft Plugin Store.

Brought to you by SPACECATNINJA