Export responsive SVG icons
A how‑to explains exporting responsive SVG icon sets from Figma without raster fallbacks by chaining plugins, aiming to keep icons scalable and consistent across web builds. The guide walks through a plugin sequence that preserves vector quality for responsive layouts. (themebat.com)
A new guide published April 10 lays out a Figma workflow for exporting icon sets as responsive Scalable Vector Graphics, or SVGs, without raster image fallbacks. (themebat.com) SVG files are text-based vector graphics, which means browsers can scale them cleanly at different sizes instead of stretching pixels the way bitmap images do. The Themebat guide says the goal is to keep icons “vector-only,” preserve the `viewBox`, and strip fixed `width` and `height` values so Cascading Style Sheets, or CSS, can size them responsively. (developer.mozilla.org ) (themebat.com) The article’s plugin chain has four steps inside Figma: normalize file names, convert strokes and booleans into pure vector paths, batch-export frames as SVG files, and run an SVGO optimization pass. It names “Rename It,” an outline-stroke or vectorize step, a batch export plugin, and an SVGO-style compressor as the core sequence. (themebat.com) Figma’s own help center says designers can export layers, frames, components, groups, sections, slices, pages, and entire files, including copying objects directly as SVG. Figma also documents “Outline stroke” as a destructive conversion that turns strokes into editable vector paths, which is one of the cleanup steps the guide relies on before export. (help.figma.com 1) (help.figma.com 2) The responsive part depends on `viewBox`, which defines the coordinate system of the SVG, and `preserveAspectRatio`, which controls how that graphic fits a differently sized box in the browser. MDN says `preserveAspectRatio` only works when a `viewBox` is present, which is why the guide treats preserving that attribute as non-negotiable. (developer.mozilla.org 1) (developer.mozilla.org 2) The guide also tells designers to put each icon in its own transparent frame, avoid image fills and embedded bitmaps, flatten complex masks and booleans when needed, and keep padding consistent. Its example naming pattern is `icon-name/size`, such as `search/24`, with a 2-pixel safe zone around 24-pixel icons. (themebat.com) One Figma community plugin cited in the wider ecosystem, “SVG Export,” says it can export selected layers to a ZIP archive or SVG sprite sheet and uses SVGO under the hood for optimization. The plugin page also says teams can save shared presets on a file, including a monochrome preset that replaces fills and strokes with `currentColor` for easier CSS styling. (figma.com) That cleanup step addresses a long-running complaint with default Figma SVG output: exported files can include fixed dimensions, extra groups, clip paths, and hard-coded fills that developers later strip out by hand. Designer Levi McGranahan wrote in 2023 that his team flattened icon artwork into expanded `<path>` elements and moved color control to `currentColor` so icons scaled more predictably in production. (levimcg.com) Themebat notes that exact plugin names may change in Figma’s community library, so the sequence matters more than any single tool: name, vectorize, batch export, then optimize. The result is a set of SVG icons that can be dropped into web builds without a second cleanup pass to undo raster fallbacks or fixed-size markup. (themebat.com)