Handing Graflio Output to a Designer Who Works in Figma

Handing generated listing images to a designer usually goes badly, because what arrives is a folder of flat JPEGs and a request to "just move the headline". The whole point of layered output is that this conversation should not happen. But layered means different things in different files, and the format that makes a designer's life easy in Photoshop is the wrong one to send into Figma. This page is about which file to send, what the person on the other end actually receives, and where the handoff stops.

Three export formats, one correct answer for Figma

The Graflio studio exports PNG, SVG and layered PSD. They are not interchangeable, and the differences matter more for Figma than for any other destination.

Send the SVG. Figma imports SVG without a plugin, and Graflio's SVG writes headlines and callout labels as real text elements rather than converting them to outlined paths first. That distinction is the whole ballgame: Figma's well-documented failure mode with imported SVG is text arriving as one vector shape per letter, and that happens when the source file already outlined its type. Graflio's does not. Import one file and check before you plan a pipeline around it, because SVG import behaviour is sensitive to how the source was written and a five-minute test beats an assumption.

Why the fonts survive, which is not usually the case

The normal outcome of any design handoff is a font substitution dialog. Here it mostly does not happen, for a boring structural reason: the studio's typefaces come from the Google Fonts catalogue — Archivo, Bebas Neue, Fraunces, Montserrat, Poppins, Inter, Oswald, Playfair Display, Source Serif 4 and the rest — and Figma ships the Google Fonts library built in. A designer opening the imported file already has those families in the font picker without installing anything or asking you for a zip.

The exception is a brand kit using a licensed typeface that is not a Google font. That behaves like any other file: the designer installs it locally, or Figma substitutes. Nothing about the export changes that, and no tool can.

What the PSD is actually for

The PSD export writes every object on the canvas as its own named raster layer, numbered in stacking order with the layer name carrying the object's role and the first characters of its text — so a designer opens the file and sees "03 headline · Fits standard 60cm cabinets" rather than "Layer 3 copy 2". That naming is genuinely useful, and the layers are separable, so moving a callout or replacing a background is a normal Photoshop operation.

What it is not is live text. Each layer is pixels. Retyping a headline in Photoshop means deleting that layer and setting new type, not clicking into it. That is a real limitation and worth saying plainly, because "layered PSD" implies editable text to most designers and here it does not deliver it. For Figma specifically the PSD is doubly wrong: Figma has no native PSD import at all, so you would be routing a rasterised file through a third-party community plugin to reach a tool that would have taken the SVG directly.

What the handoff gives you, and what it costs

The anchoring row deserves a sentence. In the studio, a callout is pinned to coordinates on the product photograph, so it keeps pointing at the actual port or seam when the layout shifts. Export to SVG and that relationship is gone; what lands in Figma is a line and a label sitting where they sat. A designer will not notice until they move the product, and then it is on them to re-aim it. Nothing is broken, but the thing that made the callout reliable does not cross the boundary.

Cost, since this is usually a team decision

Figma's published pricing as of August 2026 runs a seat model: on Professional, a Full seat is $16 per month, a Dev seat $12 and a Collab seat $3. Organization is $55, $25 and $5 respectively, billed annually, and Enterprise is $90, $35 and $5. The Starter plan is free, and viewers who only view and comment do not consume a seat.

That last detail is the one that matters for this workflow. A seller who wants to see a design and leave comments does not need to buy anything; only the person doing the work needs a Full seat. If your reason for wanting Figma in the loop is review and approval rather than editing, the cost of adding Graflio output to a Figma file is a designer you already employ, and nothing else.

Who should do this, and who should not

Do it if you have a designer, an established component library, and output that has to sit inside a wider brand system — packaging, retail, a website, a deck. The Graflio set gives them a layout already argued from the listing, the reviews and the category, which removes the part of the job most designers find least rewarding, and the SVG gives them something they can actually work with rather than trace.

Do not do it if you are a seller without a designer, because Figma is a professional tool with a real learning curve and you will spend more time in it than the last 10% is worth; the studio is where the edits are cheap. And do not build a client production pipeline on it if you are an agency running several brands, because one brand kit per account means you will be swapping a single kit between clients rather than keeping one each. That is a limitation of the product today, not a workflow you can configure around.

Common questions

Which format should I send to a designer using Figma?

The SVG. It imports natively, carries real text elements, and its typefaces come from the Google Fonts catalogue that Figma already ships.

Can Figma open the layered PSD?

Not without a third-party plugin, and it is not worth it here. Graflio's PSD layers are named but rasterised, so you would gain nothing over the SVG.

Will my designer be able to retype the headline?

In Figma from the SVG, in most cases yes, because the text is written as text rather than outlined. Verify on one file before assuming it for a whole catalogue.

Is there a Figma plugin or a live sync?

No. There is no plugin, no authentication and no round trip as of August 2026. Changes made in Figma stay in Figma.

Can each client have their own brand kit?

No. Brand kits are one per account, with no seats and no per-client kits. An agency handling several brands switches one kit rather than maintaining several.