Exporting

Learn how to export your work from Figpea, whether you need to export individual layers as assets or share entire projects with others. This guide covers all export options and best practices for different scenarios.

Layer Export

Per-layer export is the first section of the inspector's Export tab, and it is always open — select a layer and the preview and its export rows are already in front of you, with nothing to expand. Set a row's scale, suffix and format, then press the Export button. A row is configured on the layer itself, so its settings come back with it when you return to that layer or change the selection.

Below the export controls in that same tab are the handoff panels and the CSS block — see Export Tab: Handoff and CSS.

Figpea inspector panel with the Export tab active, its labels reading Design, Prototype and Export, and directly beneath the strip the always-open export section with the layer preview above its export row.

Animated demonstration in the inspector's Export tab: setting a row's scale to 2x, typing the @2x suffix, choosing WebP, then moving the pointer to the Export button to download the asset.

The settled end state of that demo: the layer's export row configured at 2x with the @2x suffix and WebP selected, and the Export button beneath it in the inspector's Export tab.

The inspector's Export tab on an SVG row: Profile set to Figpea Round-Trip SVG, with the prototype interactions, fonts, dimensions, precision, minify and accessibility options stacked below the row.

Supported Formats

  • PNG: Perfect for images with transparency
  • JPEG: Ideal for photographs
  • WebP: Modern format with superior compression
  • SVG: Vector format for scalable graphics — Pro, at every scale, for a single asset or every artboard on the current sheet (see SVG Export Options)

Page background in an export

Exporting a page brings the page's own background with it. If the page has a background color set in the inspector's Page section, that color is the ground of the exported image and the image's alpha is opaque — the page is not exported floating on transparency or on a black plate. Set the page's fill type to None and the page paints no ground of its own — the export shows the sheet's ground there if the sheet has one (below), and is transparent if it does not, which is what you want when the page is a component meant to sit on a background you have not chosen yet.

The sheet's ground sits under the page's. A sheet can carry a background colour of its own — the block above the layer list, see Sheets — and an export of an artboard on that sheet carries it as the ground, behind everything in the exported area. Where the page also has a background set, the page's colour fills the page's box and the sheet's colour stays behind it. With the sheet's type set to None, or with no background set at all, nothing changes: what was transparent in an export is still transparent.

The sheet's Background block with a soft sage green fill set, beside the PNG exported from an artboard on that sheet: the artboard's transparent margin has come out in the sheet's colour.

A background color is not a substitute for a rectangle when you need one: a rectangle is a layer you can move, mask and animate, and a page background is the ground behind everything on the page. See Page Sizes & Presets to set it.

Learn more: Export Layers in Figpea

Export Settings

Scale Options

  • 1x export of PNG, JPEG, or WebP is free on every plan
  • SVG export is Pro at every scale, 1x included
  • Any other scale of PNG, JPEG or WebP — preset (0.25x, 0.5x, 0.75x, 1.5x, 2x, 3x, 4x) or custom — is a Pro feature
  • High-quality scaling with proper antialiasing

Format-Specific Options

  1. PNG Settings:

    • Transparency support
    • Web optimization
    • Color profile handling
    • Compression level
  2. JPEG Settings:

    • Quality level (0-100)
    • Progressive loading
    • Color profile
    • Metadata options
  3. WebP Settings:

    • Quality adjustment
    • Lossless option
    • Alpha channel support
    • Metadata preservation
  4. SVG Options (per row, under the SVG content options — full reference: SVG Export Options). These options ride the SVG lane, which is Pro — the same entitlement as SVG export itself (extract.svg):

    • Dimensions — Fixed (width + height + viewBox, the default) or Responsive (viewBox only, sized by CSS)
    • Precision — decimals printed on every geometric number in the file: path data, transforms, geometry attributes and filter regions (default 3, range 0–10). Opacity and gradient stops are the one exception at 0: they keep two decimals and never round to 0, because an integer reading of a fraction erases the element
    • Minify — compact markup on (default) or indented, human-readable markup off
    • Accessibility — an optional title, desc and aria-label on the root element
    • Ignore overlapping layers — on (default) exports the selection only; off also includes layers whose bounds intersect it
    • Images — Embedded (base64 in the file, the default), Linked (separate files, downloaded as a .zip) or Omit, with Resampling choosing source resolution or the export's own size
    • Optimization — None, Safe (default: comments, metadata and unreferenced definitions removed, geometry untouched) or Aggressive (also simplifies path data; capped at Safe under the Round-Trip profile)

Variable-width strokes (added via the Variable Width tool in Path Edit Widget) export to SVG as a filled outline whose document framing includes the full widened extent — the exported SVG matches the on-canvas tapered render without clipping. Diagonal gradients on non-square layers are the exception: they export at a different band angle than the canvas render — see Gradient Editing.

SVG Export Profiles

The profile picks the content model; the output options decide how the file is written and how much of it is written — dimensions, markup style and accessibility metadata shape the root element and its formatting, precision shortens every number the file prints, while Ignore overlapping layers, Images with Resampling, and Optimization decide which content reaches the file and how it is carried. See SVG Export Options.

Figpea offers three export profiles for SVG output, tailored to different development and design workflows:

  • Plain SVG (Default): Clean, production-ready SVG markup with zero vendor attributes or internal metadata. Ideal for web developers and production codebases.
  • Figma-Tuned SVG: Optimized for importing into Figma without plugins (preserves editable text and layer/group naming).
  • Figpea Round-Trip SVG: Embeds a versioned data-figpea-* data channel on elements and the root <svg> tag to preserve Figpea-specific layout properties (strokePosition, locked, mask kind, clipContent, isolated, overrideChildrenStyle, and a shape's declared kind with its parametric geometry — a rect's corner radius, an ellipse's radii, a polygon's side count — so a reopened shape is the same shape and stays editable) and prototype interactions (triggers, actions, and target page references) across re-imports.

Figpea's Export section with an SVG row's Profile set to Figpea Round-Trip SVG, above the Prototype interactions, Fonts, Dimensions, Precision, Minify and Accessibility rows.

The Authority Rule

Visual SVG markup (transform, geometry, fill) is always authoritative. If an exported SVG is modified in an external vector tool (Illustrator, Inkscape), the visual edits win on re-import into Figpea.

Optimizer Durability

The data-figpea-* data channel attributes survive standard SVGO optimization passes, allowing you to compress and minify your exported SVGs without losing layer metadata. They likewise survive Figpea's own Minify export option, which only removes XML comments and whitespace between elements — so a minified Round-Trip export still re-imports with its metadata intact. They also survive the Optimization row at every setting: under the Round-Trip profile, Optimization is capped at Safe, and Safe never touches geometry or an element's own attributes.

Animated WebP showing a layer with an inside-positioned border exported as a Figpea Round-Trip SVG, then reimported into Figpea with the stroke position restored

Inspector panel after reimport showing the Border Position control set back to Inside, confirming the stroke position survived the SVG round trip

The same rounded 200×48 button after being exported with the Figpea Round-Trip SVG profile and reopened: the canvas shows its rounded corners and the inspector's Shape section reports corner radius 24, with the fill and drop shadow intact.

Prototype Interaction Preservation

When exporting with the Figpea Round-Trip SVG profile, Figpea serializes declared prototype interactions (ILayerBase.interactions) into the root document's data-figpea-schema payload, with element reference markers (data-figpea-interaction-ref) mapped to source layers and resolved in-document targets.

  • In-Document Resolution: Interactions whose target layer lies within the exported subtree are fully restored on re-import, mapping target ids to newly-minted layer IDs.
  • Cross-Document Preservation: Interactions pointing to target pages outside the exported subtree have their target identifiers preserved verbatim as opaque references (destinationOpaque), ensuring forward compatibility with future multi-page export formats without data loss.
  • Export Diagnostics: If an export contains interactions whose targets fall outside the exported subtree, Figpea surfaces a non-blocking diagnostic warning in the Export panel and report, notifying you that the export is partial.
  • Optimizer & Browser Safety: Interaction data is stored exclusively in inert data-* attributes (data-figpea-schema, data-figpea-interaction-ref) and never emits executable scripts (<script>) or animation markup (SMIL), ensuring SVGO compatibility and secure rendering in any browser as static artwork.

SVG Export panel showing Prototype interactions option and unresolved targets warning

Animated WebP showing prototype interactions round-trip from export to re-import

Still frame of the re-imported prototype flow with restored interactions in Figpea

SVG Font Handling

Figpea allows you to choose how text is handled when exporting to SVG:

  • None (Default): Exports standard CSS font-family references without embedding font data, naming the font family and a numeric weight on each text run rather than the face name the file carried.
  • Embed @font-face: Embeds base64 font binaries in an inline <style> block, keeping text selectable and editable. Note: Embedding commercial fonts in exported files may violate font EULA.
  • Convert to Outlines: Converts text to vector <path> geometry for universal rendering without font dependencies. When paired with the Figpea Round-Trip SVG profile, an embedded data-figpea-text payload allows Figpea to restore an editable text layer on re-import.
  • Subset fonts (Default: on): with Embed @font-face selected, embeds only the glyphs this export uses; a font Figpea cannot trim is embedded in full. Turn it off to embed each used font whole. See Fonts and file size.

SVG Export Font Handling options in the Export popover

Animated WebP showing a text layer exported with outline conversion and round-trip profile, then re-imported into Figpea as an editable text layer

Still frame of the re-imported text layer in Figpea

Frequently Asked Questions

Does exporting an SVG from Figpea include proprietary metadata? By default, No. Plain SVG exports are clean and free of vendor attributes. You can opt in to Figpea Round-Trip SVG when you want to preserve stroke positioning, layer lock states, and shape metadata across re-imports.

Can I preserve prototype interactions when exporting to SVG? Yes. When using the Figpea Round-Trip SVG profile with interactions enabled, Figpea preserves triggers, actions, and target references in the exported SVG data channel for seamless round-tripping.

Can I export an SVG that scales to its container? Yes — set the row's Dimensions to Responsive. The export keeps the viewBox and omits width/height, so CSS sizes it and it scales with its container. See SVG Export Options.

Can I export an SVG with its images as separate files? Yes — set the row's Images to Linked. The export then downloads as a .zip holding the .svg plus its image files, because an SVG cannot carry externally referenced images inside one file. Keep the archive's folder layout intact when you ship it. See SVG Export Options.

Can I embed fonts or convert text to outlines in SVG exports? Yes. You can choose to embed @font-face base64 font binaries to keep text selectable, or convert text to vector paths for universal portability. When using outline mode with the Figpea Round-Trip SVG profile, your text remains fully editable on re-import. With Embed @font-face selected and Subset fonts on (the default), each embedded font is trimmed to the glyphs the export uses.

What ground does an exported page land on? Its own background color, when it has one set in the inspector's Page section — opaque, not transparent and not black. With the page's fill type set to None it lands on the sheet's own background when the sheet has one, and exports transparent when it does not. See Sheets.

Batch Export

Export multiple layers simultaneously:

  1. Selection Methods:

    • Select multiple layers
    • Use layer groups
    • Filter by type
    • Select all visible
  2. Configuration:

    • Apply settings to all
    • Individual adjustments
    • Naming conventions
    • Output organization
  3. Output Management:

    • Choose destination
    • Create subfolders
    • Maintain hierarchy
    • Automatic organization

Project Export

Share your project in different formats:

Export Project

What an export covers

Export covers the sheet you are on. Open the dialog and it lists that sheet's top-level artboards — the same ones on the canvas — and pressing Export contains those, not another sheet's.

The Figpea Export dialog on a project with three sheets, its Artboards list showing only the two artboards of the Cover sheet.

Animated demonstration: the Export dialog open on the Cover sheet listing two artboards, then the Detail sheet made active, the dialog reopened, and its Artboards list showing only Detail's single artboard.

The settled end state of that demonstration: the Export dialog reopened while the Detail sheet is active, its Artboards list showing only Detail's artboard.

One format is the exception. Figpea (.fp) is the project file, so it carries every sheet, and a design split across sheets still travels as one file you can reopen — see Figpea Format (.fp) below.

A sheet is the unit you work in — see Sheets.

Learn more: Export Project in Figpea

While an export runs

Choose a format and click Export: the running export shows its progress inside this window — a live card in the bottom-left of the action row, left of Export and Close, carrying the task name and a progress bar. The window stays put until the export settles: Export and Close are both disabled while it runs, and Escape or a click outside will not dismiss it, so an export cannot be interrupted by accident. When it finishes the card clears and the window is dismissible again; if it fails, the failure is reported in the window as usual. For PDF, Illustrator (.ai) and PSD, the window's own status line ("Exporting…" then the settled result) still shows alongside the card.

The Figpea Export Project window mid-export: a progress card in the bottom-left of the action row, showing the running export's task name and a progress bar, with Export and Close both disabled.

Can I close the Export Project window while an export is running? No. Close stays disabled and Escape or a click outside will not dismiss the window until the export settles — so a long export can't be ended by a stray keystroke or a click. It takes a moment, the progress card clears, and Close works normally again.

Figpea Format (.fp)

The recommended format for maintaining editability:

A .fp is the whole project: every sheet is in it, so nothing is lost to the scope above.

  1. Project Naming & Unique Defaults:

    • Every from-scratch design is automatically assigned a distinguishable default name (e.g., Untitled 1, Untitled 2), ensuring your .fp exports never collide as generic New Project.fp files.
    • You can rename your project at any time directly in the top-left corner of the editor by clicking the title chip or using the agent API (figpea.session.renameProject({ name })).
    • When you open an existing file (such as a PSD, XD, or Figma file), Figpea preserves its source name for your exports.

    Animated demonstration of clicking Figpea's project-title chip, typing "Mobile Checkout Flow" to replace the default "Untitled 1" name, and pressing Enter to commit the rename.

    Figpea's project-title chip showing the renamed project "Mobile Checkout Flow" in the top-left corner of the editor, ready to export as Mobile Checkout Flow.fp.

  2. Benefits:

    • Opens as editable layers: a real layer tree, not flattened artwork
    • No re-parse: your project is read from the .fp itself, so the PSD, XD or Figma importer never runs again
    • One local file: opening it uploads nothing, your design never leaves your machine, and no account is needed to open it
    • Single file to share: commit it, mail it, or keep it on a shared drive

    You can check a .fp round trip with export.project using verifyGeometry, which reports a geometry mismatch and names the layers involved. The check compares geometry only; text content and images are outside what it checks, so give those a look by eye.

  3. Use Cases:

    • Work in progress
    • Team sharing
    • Version control
    • Project backup

ZIP Export (Pro)

Package all assets into a single ZIP file:

  1. Contents:

    • Individual layer files
    • Asset collections
    • Project structure
    • Documentation
  2. Configuration:

    • Choose formats
    • Set quality levels
    • Select scales
    • Organize output

PDF Export (Pro)

Create documentation-ready PDF files:

  1. Features:

    • Multi-page support
    • Vector quality
    • Universal compatibility
    • Print-ready output
  2. Settings:

    • Page size
    • Quality level
    • Compression
    • Metadata
  3. Page order: Open Export → PDF and the right side of the wide dialog shows every artboard of the current sheet as a thumbnail grid under Pages — drag to reorder, with a live X of Y selected count. Each cell carries a checkbox chip (top-left) and a grip chip (top-right); drag any cell to a new slot — a dashed full-cell placeholder marks the landing position — and page numbers re-assign from 1. Clicking the checkbox chip only checks or unchecks; it never starts a drag.

    The Figpea Export to PDF dialog showing the page thumbnail grid, sort buttons, and page numbers.

    Sort A→Z orders pages by name, A first; Sort Z→A reverses it. Sorting is case-insensitive and stable, so tied names keep their current order, and you can still drag cells by hand afterwards. On touch devices and narrow screens, the ‹ › steppers beside each page number are the move path — one tap moves one slot, and the stepper at either end of the range is disabled.

    Reordering and excluding affect only this export: the sheet's artboard order is untouched, and reopening the dialog resets to document order. Unchecking a page dims its thumbnail, labels it N · Excluded, and keeps its slot while leaving it out of the exported file — the export holds selected pages only — and re-checking restores the page in place. The sort buttons are disabled with fewer than two pages.

    Keyboard: tab into the grid once, move focus with ←/→ (one slot), ↑/↓ (a row), or Home/End for first/last; hold Ctrl/⌘ with an arrow to move the focused page, and press Space/Enter to include or exclude it — the dialog announces each move and sort.

Figma Migration Kit (Pro)

Move a project into Figma without a plugin:

  1. Contents:

    • One Figma-tuned SVG per top-level artboard — text stays editable, and named layers and groups keep their names
    • assets/ — the original embedded images plus @1x/@2x reference renders
    • fonts.md — every font used, flagged if missing locally, with the closest Google Fonts match
    • copy-deck.md — every text string, grouped by artboard
    • README.md — the import guide
  2. What it is not: the kit emits new Figma-tuned output you import into Figma; Figpea never writes back into an existing .fig file. It is not a pixel-perfect conversion either — complex gradients, blend modes, effects, and prototype behavior may need touch-up on the Figma side.

Contact Sheet PDF (Pro)

One review-ready PDF of the current sheet's artboards:

  1. Contents:

    • A cover page with the project name, stats, and font manifest
    • One titled page per artboard, in document order
  2. Use Cases:

    • Print review and stakeholder sign-off
    • An archive snapshot of what the file contained

Flow Poster (Pro)

A one-page map of your prototype:

  1. Contents:

    • One node per artboard on the current sheet (thumbnail + name)
    • One edge per parsed prototype transition
  2. Output Formats:

    • SVG (default), or a PNG or PDF render of that same SVG

Illustrator (.ai) Export (Pro)

Figpea writes a PDF-compatible .ai file: portable pages any PDF reader renders, plus Figpea's own editing copy so Figpea reopens the same file exactly. Illustrator sees the pages, Figpea sees everything.

The Export Project dialog with the format list open and the Illustrator (.ai) entry selected.

Illustrator opens the portable pages. It does not get Figpea-grade editability — Figpea does not write Adobe's private editing data, so a layer that stays live in Figpea arrives in Illustrator as plain page artwork. Figpea reopening its own .ai export restores layers, artboards, and editing: names, visibility, artboard rects, paths, text, and images round-trip; anything the file cannot carry exactly is approximated and reported.

The editor with an exported .ai file reopened: the canvas artwork beside the layers panel carrying the document's own layer names.

Approximations are each reported as a warning. After the export the dialog lists what was approximated and on which layer — a gradient or pattern fill carried as solid black, an exotic construct carried as a named placeholder — and the same warnings read back on report.diagnostics(). A clean export shows the confirmation with no warnings list.

The Export Project dialog after an .ai export, listing two approximation warnings that each name their layer.

Illustrator (.ai) export is part of Figpea Pro — it rides the same claim as PDF export. See Plans for the current split. To open .ai files — including your own exports — see Opening Files.

Can Figpea export to Illustrator (.ai)? Yes. Open Export Project, pick Illustrator (.ai), and click Export — the file downloads as <project>.ai. It is part of Figpea Pro.

Will Illustrator open Figpea's .ai file with editable layers? Illustrator opens the portable pages. Figpea-grade editing does not transfer: live text, layers, and effects arrive as plain page artwork, because Figpea does not write Adobe's private editing data.

Does Figpea's .ai export reopen exactly in Figpea? Yes. Figpea reopening its own .ai export restores layers, artboards, and editing — names, visibility, artboard rects, paths, text, and images. That is the exactness the format promises: what Illustrator sees (pages) and what Figpea keeps (everything) are two views of one file.

What happens when something can't be exported exactly? The export still succeeds, and each approximation is reported as a warning naming the layer — in the dialog after the export, and on report.diagnostics().

Asset Harvest (Pro)

Extract every embedded image and icon-sized vector graphic from your design file into an organized, platform-ready asset bundle:

The Figpea Asset Harvest modal displaying detected embedded images and vector icons with Web, iOS, and Android platform preset options.

  1. Contents:

    • Embedded images: all bitmap graphics extracted at native resolution or scaled per preset
    • Vector icons: icon-sized vector groups (≤128px on longest side, containing no text or bitmap layers) exported as clean SVGs
    • Platform presets:
      • Web: PNG + WebP at 1× and 2× (name.png, [email protected], name.webp, [email protected]), plus SVGs for vector icons (flat structure)
      • iOS: PNG at 1×, 2×, and 3× (name.png, [email protected], [email protected]), plus SVGs for vector icons (flat layout, Xcode-friendly @2x/@3x naming)
      • Android: PNG assets organized into density folders (drawable-mdpi through drawable-xxxhdpi), with lowercased [a-z0-9_] resource names
  2. Use Cases:

    • Handing developer-ready icons and images to an iOS, Android, or web engineering team without manually renaming or resizing each file
    • Pulling every embedded image and icon-sized vector group out of an XD, PSD, or .fig file for reuse elsewhere
    • Producing flat, Xcode-friendly @2x/@3x-named image sets for iOS, or an Android density-folder set, without a separate export plugin
  3. Free vs Pro boundary:

    • Free: opening the Asset Harvest gallery, inspecting detected images and icons, and selecting a platform preset is free — no account required
    • Pro: exporting the generated ZIP asset bundle requires Figpea Pro or a Rescue Pass

Which of these formats your account can export is on Plans.

SVG Export (Pro)

Pick SVG in Export Project and choose how the selected artboards leave Figpea — every artboard on the sheet you are on (What an export covers), as one file per artboard in a ZIP or as one combined SVG. One file per artboard, in a ZIP, is the default: each file is named from its artboard, a duplicate takes a numeric suffix, and the archive follows the order you set. One combined file puts every selected artboard in a single SVG, laid out in a grid you configure.

SVG export is part of Figpea Pro — for a single asset and for a whole project alike. See Plans.

The Figpea Export Project dialog with the format list open and the SVG entry selected, beside the options column for an SVG export.

The Figpea Export Project dialog with SVG selected: the format list on the left, the sheet's five artboards as numbered tiles above the Layout, Include backgrounds, Include page titles and other option rows.

  1. One file per artboard, in one archive — the default
    • Each file is SVG markup produced by Figpea's own encoder
    • Each SVG is named from its artboard's name; a duplicate takes a numeric suffix (Home.svg, Home_2.svg)

A downloaded ZIP opened to show one SVG file per artboard, each named after its artboard.

  1. One combined file
    • Layout is a two-way switch: Files (ZIP) is the default, and Combined (one SVG) produces a single .svg named after the project, not a ZIP

The Figpea Export Project dialog on SVG with Combined (one SVG) selected: the Layout switch, the Columns and Spacing rows and the two include checkboxes.

  • Columns is Auto by default — it fits the artboards into the squarest grid it can — or a number from 1 to 6
  • Spacing is the gap between cells in px, and it is the sheet's own margin too; 24 is the default, and 0 removes both
  • Include backgrounds is off by default: on, each artboard's own page colour is painted into its cell; off, the cells are transparent and whatever you drop the file on shows through
  • Include page titles is off by default: on, each artboard gets its own <title> — its accessible name and hover tooltip. That element is not the Title field, which stays the document's one title
  • The grid follows the order you set in the artboard list, left to right and top to bottom
  • Links between artboards is on by default, and it is a combined-layout option only — a ZIP of separate files has no document to link inside. On, an interaction whose destination is another exported artboard becomes a real <a href="#…"> link to that artboard in the one document, and the document carries the interaction data Figpea needs to reopen it. Interactions whose destination is not in the selection write no link at all rather than a broken one — a target outside the selection gets nothing, so deselecting an artboard removes the links that pointed at it. A browser follows the link when the file is opened directly; inside an <img> or a CSS background nothing is clickable, because those contexts do not run links

An animated comparison of one export at Columns 1, Columns 3 and Columns Auto: the same five artboards reflowing between a single column, a three-column grid and the automatic grid.

The same combined export twice, side by side: on the left with Include backgrounds and Include page titles off, on the right with both on and each artboard's own colour painted behind it.

A combined SVG exported from Figpea and opened in a browser: five artboards in a three-column grid, each with its own background and title.

  1. The options apply to every artboard
    • Fonts, Dimensions, Precision, Minify, Title, Simplify stroke, Color profile, Styling, Text bounding box, Ignore overlapping layers, Resampling and Optimization — the option reference is SVG Export Options. In the combined layout, Links between artboards joins them
    • One set of values covers the whole export, in both layouts; to give one artboard its own settings, export it on its own
    • Fonts is None by default, which is what this lane has always written: the text keeps font names and a viewer without those fonts shows a fallback. Embed @font-face copies each used font's bytes into the file, so the text renders in the design's fonts on a machine that does not have them, and stays selectable. Convert to outlines turns the text into vector paths — it renders anywhere and is no longer editable as text. Embedding copies font files into a document you hand to someone else, so check each font's licence allows it
    • Font subsetting is automatic with Embed @font-face: each embedded font carries only the glyphs your text uses, and a font whose file cannot be trimmed goes in whole. Subsetting never makes a file larger — on a design whose fonts cannot be trimmed it changes nothing
    • In the combined layout one copy of each font covers the export — a single @font-face per used font, in the shared definitions, trimmed with the glyphs of every artboard's text. In the files layout each file carries its own copy, so each file stands alone whenever you hand one on The Export Project dialog's SVG options with Layout set to Combined (one SVG), the SVG entry highlighted in the format list: the Columns and Spacing rows, the Links between artboards checkbox checked with its caption, the two include checkboxes, and the Fonts row set to None with its caption underneath.

The source of a combined SVG exported with Fonts set to Embed @font-face: the document root, one shared defs block holding one style element with a single @font-face rule for Arial, then the Home and Checkout artboards as two g elements carrying data-name, with the font payload shortened to its character count.

  • Optimization is Safe by default: it removes XML comments, <metadata>, unreferenced <defs> and unused namespace declarations, and touches no geometry. None keeps the document exactly as written; Aggressive also rewrites path data inside a 0.05 px tolerance, so compare the render before you ship a file where that matters. Safe is the default and it is what this lane has always applied, so a dialog you do not touch produces the files you already have
  • Resampling is Detailed by default. Basic resamples the images this lane re-encodes — pattern fills, and the raster stand-ins it draws for blend modes — down to the size the export resolves. An image layer keeps its own bytes at either setting: this lane always embeds each artboard's images, which is why Images (embedded, linked or omitted) stays a layer-row option
  • Ignore overlapping layers is on by default, which is what an artboard export has always done: the file holds the artboard and what is inside it. Turned off, it also reaches outside the artboard for anything whose bounds overlap it — content sitting across two artboards comes along into both

Animated demonstration: the combined SVG opened directly in a browser showing the Home artboard and its Go to checkout button, then that button clicked, and the document jumping across to the Checkout artboard the link points at.

The settled end state of that click: the same exported SVG in the browser after the link was followed, with the Checkout artboard filling the window and only the edge of the Home artboard still visible on the left. The same panel scrolled to its option rows: Dimensions set to Fixed, Precision 3, Minify checked, and an empty Title field whose hint says no title element is written.

The Export Project dialog's SVG options with the Advanced group open: Ignore overlapping layers checked, Resampling set to Detailed (Default) and Optimization set to Safe (Default), each with its caption.

Two SVGs from one project export shown side by side as source: the first exported with Optimization set to None, still carrying an unused linearGradient definition and the document's whitespace; the second exported with Aggressive, with that definition gone and a shorter path data string. Both files changed, because the setting applies to every artboard.

The same artboard exported twice side by side: with Ignore overlapping layers on, only the artboard's own content; with it off, the content that overlapped it from outside is included too.

The option rows below the includes: Include backgrounds, Include page titles, Dimensions, Precision, Minify, Title and Simplify stroke, with the Advanced disclosure open beneath them showing Color profile, Styling, Text bounding box, Ignore overlapping layers, Resampling and Optimization.

  1. Selection and ordering are yours
    • Tick the artboards you want, drag the tiles to reorder them, or sort A→Z / Z→A
    • The tiles are numbered in export order, and both layouts follow the order you set; an unticked artboard appears in neither

Dragging an artboard row in Figpea's Export Project artboard list to a new position, with a placeholder marking where it will land and the position numbers re-assigning.

The artboard list after reordering, with the moved artboard's new position number shown.

  1. Round trip
    • A file-per-artboard export reopens one artboard at a time
    • A combined export reopens as one artboard, the size of the grid, with its viewport preserved — each artboard survives as a named group inside that one drawing (a single SVG has one root and one coordinate system, so the artboards are regions of one page rather than pages of their own)
    • Optimization at Aggressive rewrites path data, so leave it on Safe for a file that has to come back into Figpea — the other settings do not move geometry

The same format is on the agent API as export.project({ format: "svg" }), which takes the same layout (svgLayout, svgColumns, svgSpacing, svgIncludeBackgrounds, svgIncludePageTitles), font handling and links (svgFontHandling, svgCrossArtboardLinks), the three content options (svgOptimization, svgImageResampling, svgIgnoreOverlapping) and the same remaining options — see Agent API.

Is SVG export free? No. SVG export is a Pro capability on every plan, for a single asset and for a whole project. Opening, inspecting and editing any file stays free, as does a single 1× export as PNG, JPEG or WebP and saving your work as a .fp file. See Plans.

Can Figpea export every artboard as SVG at once? Yes — every artboard on the current sheet, as one file per artboard in a ZIP or as one combined SVG. Choose SVG in Export Project, tick the artboards you want, then pick the layout and export. The scope is the dialog's, not this format's — What an export covers. It is part of Figpea Pro, the same entitlement as exporting a single asset as SVG.

How do I put all my artboards in one SVG? Choose SVG in Export Project, switch Layout to Combined (one SVG), set Columns and Spacing, then Export. The artboards land in the order the list shows them.

Can I apply optimization to a whole project export? Yes — Optimization is a project option: pick None, Safe or Aggressive in Export Project → SVG and it applies to every artboard, in both layouts. Safe is the default and it is what this lane has always applied, so leaving it alone changes nothing you exported before.

Why is my artboard not where I put it in the combined SVG? The grid follows the order you set in the artboard list, not the order the artboards sit on the canvas. Drag the tiles (or sort them) before exporting.

Do the SVGs stay responsive? In files mode, yes, with Dimensions set to Responsive: every root <svg> keeps its viewBox and preserveAspectRatio and carries no width/height, so CSS sizes it. Leave it on Fixed to bake a pixel size in. A combined file has a single root, so Responsive scales the whole grid as one unit. See SVG Export Options.

Can I re-import the SVGs into Figpea? A file-per-artboard export reopens one artboard at a time. A combined export reopens as one artboard the size of the grid. That is the guarantee for the files Figpea produces; third-party SVG import fidelity is a separate question — see Opening Files.

Are the files the same as exporting each artboard on its own? In files mode, yes: an artboard's SVG in the ZIP is the file you would get by exporting that artboard alone with the same settings. A combined file is not those files in a wrapper — it is one document with one root, one viewBox and one shared context, so an artboard sits inside a drawing rather than standing alone. The geometry inside each artboard is the same in both.

Can one artboard use different options from the others? No — the options apply to every artboard in the export, in both layouts. To give one artboard its own settings, export it on its own, where each row keeps its own options.

Will my fonts render on a machine that does not have them? Only if you embed them. Set Fonts to Embed @font-face in Export Project → SVG and each used font's own bytes travel inside the file, so the text renders in the design's fonts wherever it is opened and stays selectable. With the default None the file keeps font names only, and a viewer without those fonts substitutes its own. Convert to outlines sidesteps fonts entirely by turning the text into paths. Embedding copies font files into the file you share — check each font's licence allows it. See Fonts and file size.

Do my prototype links work after export? In the combined layout, yes — for the destinations you export. With Links between artboards on, an interaction whose destination is another artboard in the same export becomes a link to that artboard inside the single document, and opening the file directly in a browser follows it. A destination you left unticked writes no link, so nothing dangles, and inside an <img> or a CSS background nothing is clickable in any case. The ZIP layout is one file per artboard, so it carries no cross-artboard links.

Does exporting the project as SVG upload my file? No. The SVGs are encoded in your browser and the archive is assembled there; nothing leaves your machine — the same rule as every other export in Figpea.

Export Workflows

For Development

  1. Asset Preparation:

    • Organize layers
    • Set up naming
    • Choose formats
    • Configure scales
  2. Export Process:

    • Select assets
    • Apply settings
    • Generate files
    • Verify output
  3. Quality Control:

    • Check resolutions
    • Verify transparency
    • Test in context
    • Validate sizes

For Collaboration

  1. Project Sharing:

    • Use .fp format
    • Include resources
    • Document structure
    • Set permissions
  2. Asset Distribution:

    • Organize by type
    • Include documentation
    • Provide variations
    • Set up naming
  3. Version Control:

    • Track changes
    • Mark versions
    • Document updates
    • Maintain history

Best Practices

File Organization

  1. Naming Conventions:

    • Use clear names
    • Include dimensions
    • Add scale indicators
    • Mark versions
  2. Folder Structure:

    • Separate by type
    • Group by feature
    • Maintain hierarchy
    • Use clear names

Quality Assurance

  1. Before Export:

    • Clean up layers
    • Check naming
    • Verify scales
    • Test settings
  2. After Export:

    • Verify output
    • Check quality
    • Test in context
    • Validate sizes

Optimization

  1. File Size:

    • Choose appropriate formats
    • Optimize settings
    • Balance quality
    • Consider usage
  2. Performance:

    • Batch when possible
    • Use efficient formats
    • Optimize assets
    • Monitor resources

Troubleshooting

Common Issues

  1. Quality Problems:

    • Check scale settings
    • Verify format options
    • Review source quality
    • Test different settings
  2. Size Issues:

    • Optimize assets
    • Choose appropriate formats
    • Adjust compression
    • Review dimensions
  3. Export Errors:

    • Check layer names
    • Verify permissions
    • Clear cache
    • Update software

For more detailed information about exporting, check our blog posts.

Developer handoff

Hand a developer a self-contained spec file, not a hosted link that can die with a subscription. Both exports below are part of Figpea Pro — export them from the Project Export dialog, choosing Spec Bundle or Design Tokens from the format list on the left.

The Figpea spec bundle opened as a local HTML file, showing an artboard with an Inspector panel reporting a selected element's size, position, color, and font, plus copyable CSS.

Offline spec bundle (Pro)

The spec bundle is a single self-contained HTML file covering every artboard on the current sheet. It opens straight from a downloads folder, from a local file:// address, with zero network requests — no server, no upload, nothing to install for whoever opens it. Click any pinned element to reveal its size, position, color, and font, then copy the CSS straight out of the panel. The font values it reports are the same family and numeric weight the inspector's Export tab reports.

  • Every artboard on the sheet, one offline file
  • Click-to-inspect size, position, color, and font
  • Copyable CSS for each inspected element
  • Opens from file:// with zero network requests — no account needed to open it

Design tokens (Pro)

The design tokens export emits a CSS custom properties file plus a matching tokens JSON, covering your project's distinct fill colors and text styles. It's a documented subset built for dropping straight into a codebase, not a claim of full design-tokens-spec compliance.

  • CSS custom properties for every distinct fill color and text style
  • A matching tokens JSON with the same values
  • Deterministic names, stable across repeat exports

Free complement: copying a layer's CSS from the inspector's Export tab stays free — the CSS block is the last section of that tab, with its own copy button. Measuring distances between elements is a different tool on the canvas, covered in Inspect Tool. The spec bundle and design tokens above are handoff exports, part of Figpea Pro — see Pricing to upgrade.

Read the full walkthrough: Developer Handoff in Figpea. These exports are also the developer-handoff piece of the XD rescue flow.

Mobile Layer Sharing

On a phone or tablet, the bottom action bar carries a Share slot that sends a single layer to whoever needs it without leaving the browser.

Select a layer first, then tap Share — with nothing selected, Figpea asks you to pick a layer. It renders that layer to a PNG at 1× and hands the file to the operating system's own share sheet, so it lands in Messages, Mail, Slack or AirDrop like any other file. If the browser has no Web Share file support, the same tap downloads the PNG instead and tells you it did, so the action never fails silently.

Nothing is uploaded and no link is created — the file goes from your device to the app you choose. Sharing a layer this way is free and raises no upgrade prompt.

It is a copy, not a save: the exported PNG is a new image, and your original PSD, XD or .fig file is never modified. For multi-layer, scaled or vector output, use the export options above.

More on the mobile review loop: Mobile Design Viewer & Touch Review Guide.

More in Export & Handoff

See all in Export & Handoff