Editor & import
Bring the design
you already have.
Import your Figma file. Frames arrive as templates with type, layout and gradients intact. Mark what changes. Start producing.
Your Figma file
northwind-brand.fig
4 frames · 2.1 MB
Type, layout and gradients arrive intact. Nothing is rebuilt.
4 templates, ready to render
Launch day
1080 × 1350
northwind_instagram_1080x1350
Launch day
1080 × 1920
northwind_story_1080x1920
Launch day
1200 × 627
northwind_linkedin_1200x627
Launch day
1280 × 720
northwind_thumbnail_1280x720
Each frame gets a stable addressing key. That string is what you pass to the API — and renaming or resizing the frame does not change it.
Why this matters more than any feature
Rebuilding is why people stay on tools they’ve outgrown.
Every other tool in this category asks you to rebuild your designs in their editor first. That is the real reason migrations don’t happen — not price, not features. Rebuilding forty client templates by hand is a fortnight nobody will authorise, and the rebuilt version is never quite the same.
Import removes the fortnight, and it removes the drift: what arrives is your design, not somebody’s interpretation of it.
A real editor
Not a form builder.
Templates are authored in a full design environment — the same engine that renders your output.
- Type with genuine control: family, weight, size, letterspacing, line height, and styled ranges within a single text block
- Gradients you drag on the canvas — linear and radial, on fills, on shapes and on text
- Frames, auto-nesting, z-order, rulers and snapping
- Many frames per project, each its own output size
Your designer will not feel downgraded — which matters, because they are the one who has to build the template.
Launch day
Slots
Marking slots
Select a layer. Say what may change.
texta stringheadline, quote, price, nameimagea URL or a library assetphoto, screenshot, logocolora hex valueaccent, background, campaign colourfonta family nameper-client or per-campaign typebooleantrue / falseshow or hide a badge, banner or overlayAnything you don’t mark cannot be changed by anyone — not a teammate, not the API, not an agent. That’s the brand safety, and it’s structural rather than procedural.
Image slots can be folder-bound. Bind one to an asset folder and only assets from that folder can fill it. Anything else is rejected with a clear error rather than rendered.
Publish
Editing a template can’t break production.
Publishing snapshots the frame to an immutable version. The API only ever renders published snapshots — never your live draft — so you can redesign in the open without changing what production is producing until you say so.
Each published frame gets a stable addressing key, {project}_{frame}. Renaming or resizing the frame doesn’t change it, so your integrations keep working.
Launch day
1080×1350
Launch day
1080×1920
Launch day
1080×1080
Launch day
PRODUCT1280×720
Each one composed for its shape — not the same image cropped four ways.
Illustrator files
There’s a route, and we won’t pretend it’s one click.
Open the .ai in Figma, use Save local copy, and import the resulting .fig. Two extra steps — but still no rebuild, which is the part that actually costs you a fortnight.
Questions
- Can I import a Figma file?
- Yes. Import a .fig and its frames arrive as templates with type, layout and gradients intact. You do not rebuild anything, which is the usual reason migrations never happen.
- How do I turn a Figma design into an API?
- Import the file, mark the layers that should change as typed slots, then publish. Each published frame gets a stable addressing key you pass to the render API.
- Can I use Illustrator files?
- Indirectly: open the .ai in Figma, use Save local copy, and import the resulting .fig. Two extra steps, but still no rebuild.
- What happens if I edit a template that is live?
- Nothing, until you publish. The API only ever renders published snapshots, never your draft — so you can redesign in the open without changing what production is producing.