# Your selection as the reference — eroq for Figma and Blender > The two plugins that render from what you already have on screen. Figma sends your selection as the reference and returns an image fill; Blender snapshots the viewport and returns planes, references and sequencer strips. Published 2026-09-20 · eroq.ai — canonical: https://eroq.ai/blog/eroq-for-figma-and-blender-reference-workflows Most generation starts from a prompt. Designers and 3D artists start from something on screen — a wireframe, a blocked-out scene — and want the render to *follow* it. The Figma and Blender plugins are built around that one move: what you selected, or what the viewport shows, goes to eroq as the reference picture, and the result comes back where the app wants it. This guide is both installs and the reference workflow in each. ## Figma A plugin for the Figma desktop app, in beta, imported from its manifest. 1. Download the zip from the [Figma page](/plugins/figma) and unzip it. In Figma desktop: **Plugins → Development → Import plugin from manifest…**, pick `manifest.json`. 2. Run **eroq** and click **Connect eroq**. eroq.ai opens: sign in, click Allow, copy the code the page shows, paste it into the plugin. (Figma plugins run sandboxed and cannot listen for a redirect, hence the code.) 3. Write a prompt — tick **Use selection as reference** to start from what you selected — pick a frame format, Generate. The render arrives as an **image fill** on a frame sized to the format, named after the prompt. Not a file to place: a fill you can move, mask, crop and swap like any other. 10 credits on Krea 2. Video works too, as **video fills** on Figma plans that support them; on other plans the plugin hands you the clip's link. ### The reference move Select a wireframe of a hero section — grey boxes, a headline placeholder, a rectangle where the photo goes. Tick *Use selection as reference*, prompt « a product photo of a ceramic pour-over kettle on a linen cloth, morning light, editorial ». The selection is exported as a picture and sent as the reference; the render follows its layout — the kettle where the rectangle was, the light from the side the boxes suggested. Drop the fill into the rectangle and the mock-up is a comp. Works the same with a sketch (line art in, rendered scene out, composition kept), a product shot (« same product, studio white background »), or a previous render (« same scene at night »). What a reference holds: composition, placement, rough shapes, the overall palette. What it does not: exact pixels — it is a picture the engine follows, not a mask. For pixel-exact edits, the [Photoshop plugin](/blog/eroq-for-photoshop-layers-and-edits) returns an aligned layer. ## Blender An add-on for Blender 4.2 and later, 5.x included, on macOS, Windows and Linux. 1. Download the zip from the [Blender page](/plugins/blender). **Edit → Preferences → Get Extensions → Install from Disk…**, or drag the zip into Blender. 2. Open the sidebar (**N**) → **eroq**, click **Connect eroq**: the browser opens eroq.ai, sign in, Allow. The tab says it is connected. 3. Write a prompt, optionally tick **Viewport snapshot** as the reference, Generate. Results land as Blender objects, in one click each: - an image → a **reference image** in the scene, or a **textured plane**; - a clip or a voice line → a **strip on the Video Sequencer**, at the playhead. Requests run in the background; the viewport never freezes, and results apply when they arrive. ### The viewport move Block out a scene with primitives: a cube for the building, a plane for the street, a cylinder for the lamp post, the camera where you want it. Tick *Viewport snapshot*, prompt « a rain-soaked street at night, a lone streetlamp, neon signs on the building, cinematic, 35mm ». The snapshot goes as the reference; the render keeps your camera, your masses and your horizon, and paints the rest. Add it as a reference image behind the camera and you have a matte to model against — or as a plane and it is a backdrop. Then the clip: prompt « slow push-in » with the render as the start image on an engine that reads one, and the five-second clip lands on the Sequencer next to a voice line for the previz. 45 credits on [Seedance 2.0 Mini](/models/seedance-2-0-mini), 3 per 100 characters for the line. The [previz guide](/blog/ai-previz-for-indie-filmmakers) is the long version of this workflow. ## What both share - **Sign-in, not keys.** Each plugin gets a key named after the app and machine under Developers → API keys on eroq; revoke there to disconnect. A pasted key is the fallback. - **The studio's prices**, read live from the API — a new engine appears without a plugin update. - **The library.** Every render is in your eroq [Library](/studio/library) with its recipe, whether it was made in Figma, Blender or the studio. - **Async.** Images take seconds, clips one to five minutes; the plugin polls and applies. - **Beta installs.** Figma from the manifest, Blender from disk, until the Community and extensions.blender.org listings follow their reviews. ## FAQ ### Is the Figma plugin in the Figma Community? Not yet — during the beta you import it from its manifest in Figma desktop. ### Can the Figma plugin make videos? Yes, as video fills, on Figma plans that support video. On other plans the plugin gives you the clip's link instead. ### Does Blender freeze while rendering? No — requests run in the background and results are applied when they arrive; you keep working. ### Does the viewport snapshot leave my machine? It is sent to eroq as the reference picture, over HTTPS, and the render is saved to your library like any other. The `.blend` file itself is never sent. Download from the [Figma](/plugins/figma) or [Blender](/plugins/blender) page — the first reference render is on the free credits.