Everything you need to create your first generated design.
AutoVariant works by matching CSV column headers to layer names inside your selected frame. When the names match, AutoVariant maps the fields automatically.
Select any frame on your Figma canvas. AutoVariant reads the text and image layers inside it — their names become the fields available for population from your CSV. The selected frame acts as the template: AutoVariant duplicates it once per CSV row.
TitleSubtitlePriceProduct ImageTitle,
Price,
Product Image,
or
CTA Button.
Any name will work, but consistent naming makes templates easier to maintain and understand.
Upload a CSV file. Row 1 is your column headers — these correspond to the layer names in your selected frame. When names match, AutoVariant maps the fields automatically. Each subsequent row becomes one generated output.
| Title | Subtitle | Price |
|---|---|---|
| Hoodie | New Collection | £49 |
| Tote Bag | Summer Drop | £29 |
| Cap | Limited Edition | £24 |
3 rows = 3 generated output frames. Column headers match the layer names from Step 01.
Before generating, configure how AutoVariant names and arranges your outputs. Both settings are optional, but they become incredibly powerful when generating dozens or hundreds of variants.
Naming Structure
Control how generated frames are named. Combine static text with CSV values to create organised, export-friendly file names automatically. Example output names:
Product-Hoodie-RedProduct-Tote-Bag-BlackProduct-Cap-BlueName=Value format when generating component variants. This mirrors Figma's variant naming structure and can dramatically speed up component creation workflows.
Layout
Set how many variants appear per row on the canvas and the gap between them.
Click Generate. AutoVariant duplicates the selected frame once per CSV row, populates each copy with that row's data, and places all frames on the canvas. Once complete, every output is a normal Figma frame — edit, export, or hand off as usual.
Check the layer is inside the selected frame, is visible, and is a supported text or image type.
Check that the correct layer has been selected for mapping. For component variants, AutoVariant may expect a specific property format such as Property=Value. Also verify that your CSV column contains data and that the intended layer is being targeted.
Check the CSV contains valid image data for that column and that the image layer was included during field mapping.
Review the Naming Structure settings in Step 03 — check the selected fields and separator match the format you expected.
Select your frame on the canvas before opening the plugin. The plugin needs the frame selected to know what to duplicate.
Verify the mapped layer is using the correct variant naming structure. Many component sets require values such as Property=Value to match the component's variant options.
AutoVariant works for any repeatable design where the layout stays fixed and the content changes — player cards are just one example.
Install AutoVariant free and generate your first 5 outputs — no account required.