# eroq plugins for Photoshop, Premiere Pro, After Effects, DaVinci Resolve, Figma and Blender — the beta > A product note on the creative-app plugins now in beta. What each one does inside its host, the shared Connect eroq sign-in, why they are all thin clients of the API, and what beta means for installs. Published 2026-09-27 · eroq.ai — canonical: https://eroq.ai/blog/plugins-beta-photoshop-premiere-resolve-figma-blender Generating in the studio and then downloading, importing and placing the file is a loop nobody enjoys, and it is the loop a plugin removes. Six plugins are now in beta at [/plugins](/plugins): **Photoshop**, **Premiere Pro** and **After Effects** (one panel), **DaVinci Resolve**, **Figma** and **Blender**. Each renders on eroq and puts the result where that app wants it — a layer, a bin, a fill, a plane. This is the product note: what each does, the one sign-in they share, the rule they are built on, and what beta means. ## One rule Every plugin is a **thin client of the public API**. Same models, same credit prices, same wallet as the studio, the [MCP server](/mcp) and the CLI. Nothing generates outside `/v1`; when a plugin needed something the API lacked, the API got it first. That is why prices are identical everywhere — 10 credits for a Krea 2 image, 45 for five seconds of [Seedance 2.0 Mini](/models/seedance-2-0-mini) — and why a render made in Blender is in your [Library](/studio/library) with its recipe like one made in the studio. It is also why they are small. No telemetry, no build step: what is in the plugin folder is what ships, zipped. ## One sign-in Plugins do not ask for a pasted key. Click **Connect eroq** and the same OAuth flow that Claude and ChatGPT use runs: the browser opens eroq.ai, you sign in, you click Allow, and the plugin gets its own key, named « *Host* on *machine* (connected) », visible and revocable under Developers → API keys. Two shapes, depending on what the host can do: - **Loopback** (Premiere/After Effects, DaVinci, Blender) — the plugin listens on your machine for the browser's redirect; Allow, and the tab says « eroq is connected — you can close this ». - **Copy-code** (Photoshop, Figma) — sandboxed hosts cannot listen, so eroq.ai shows a code with a Copy button after Allow; paste it into the plugin. A pasted key still works as a fallback (« Use an API key instead »). Reconnecting the same host-and-machine name replaces its previous key, so revoking is always one line in the dashboard. The [sign-in note](/blog/mcp-sign-in-oauth-no-api-key) has the mechanics. ## What each one does **[Photoshop](/plugins/photoshop)** — a UXP plugin. *Generate* renders a picture straight into the document as a new layer named after the prompt, in five frame formats. *Edit* sends the open document to eroq's instruction editor with a sentence — « make it golden hour », « swap the jacket for red leather » — and the result comes back as a layer aligned over the canvas, ready to mask. The [Photoshop guide](/blog/eroq-for-photoshop-layers-and-edits) walks both. Installs as a `.ccx` (double-click; Creative Cloud does the rest). Photoshop 2023 or later. **[Premiere Pro](/plugins/premiere-pro) and [After Effects](/plugins/after-effects)** — one CEP panel for both. Video, Image or Speech; pick the engine, the length and the frame; Generate; the file is imported into the open project when it lands, and kept in a local eroq folder. Video engines by name with their price and plan; voice-over from the roster or your clones. The [editors guide](/blog/eroq-for-davinci-resolve-and-premiere) covers the workflow. Premiere 2019 / After Effects 2019 or later. **[DaVinci Resolve](/plugins/davinci-resolve)** — a Python script under Workspace → Scripts, on the free edition and Studio. Renders land in an « eroq » bin of the Media Pool; tick *Append to timeline* and the clip is cut in at once. Needs Python 3 on the machine. **[Figma](/plugins/figma)** — a plugin for Figma desktop. Prompt a picture and it arrives as an image fill sized to its frame format; select a wireframe, a sketch or a mockup first and *Use selection as reference* sends it as the reference picture, so the render follows your layout. Video fills on Figma plans that support them; a link elsewhere. **[Blender](/plugins/blender)** — an add-on for 4.2 and later (5.x included). Prompt, or *Viewport snapshot* as the reference — rough blocking in, finished image out. A render becomes a reference image or a textured plane in one click; clips and voice lines land on the Video Sequencer at the playhead. Requests run in the background; Blender never freezes. ## What beta means Direct downloads, not the hosts' stores yet: the `.ccx` for Photoshop installs on double-click, the CEP panel installs as an unsigned extension with a one-time developer-mode switch the README walks through, Figma imports from its manifest in the desktop app, Blender installs from disk, Resolve runs an installer script. The Adobe Exchange, the Figma Community and extensions.blender.org listings follow their reviews. Beta also means the plugins change with the API. The panel's engine list comes from `/v1/models` and `/v1/engines` at runtime, so a new engine appears without an update, and a locked one says which plan opens it. ## What they share with everything else - **Async renders.** Images and video are jobs; the plugin polls and applies the result when it lands. The host's UI thread is never blocked on the network. - **Signed links.** Media URLs expire; every plugin downloads right away and keeps a local copy. - **The same policy.** Adults only, no minors, no real people without consent; the API enforces it and the plugin shows its message. - **Failed renders refund themselves.** ## FAQ ### Are the plugins free? Yes. They bill the studio's credit prices for what they render, nothing more. New accounts start with free credits. ### Do I need a different account per app? No — one eroq account, one wallet. Each app gets its own key under it, so you can revoke one without touching the others. ### Why is the Adobe panel unsigned? During the beta it is not on the Adobe Exchange yet; the README walks through the one-time developer-mode switch. Signing and the Exchange listing follow the review. ### Can I use them with a team workspace? Yes. Connect in the workspace you want to bill; the key is minted there, and workspace roles and credit caps apply to it like any key. Pick your app at [/plugins](/plugins) — every page has the download and the three steps.