Five Pre-Export Steps Inside Figma (or Any Vector Tool)
- Uncheck 'Clip content' on the icon frame unless truly needed: Leaving Clip Content checked forces Figma to wrap every icon in
<defs><clipPath id="clip0_..."><rect .../></clipPath></defs>, doubling XML length. - Flatten boolean operations (Union / Subtract / Exclude): Unflattened booleans sometimes export overlapping paths with brittle
fill-rule="evenodd"quirks. - Snap anchor points to whole or half pixels on a 24×24 frame: Coordinates like
3.9987blur horizontal lines on standard DPI monitors. - Keep stroke icons as strokes (don't outline strokes prematurely): Unless variable-width calligraphy is required, preserving
stroke-widthkeeps path data 50%–70% shorter and lets developers tune weight in the browser. - Export curved text as outlines: Remember browser editors—including SVG Nexus's Online SVG Editor—do not edit
<textPath>nodes directly, and web visitors may not have your desktop font installed.
Round-Tripping Between SVG Nexus and Figma Without Plugins
Going the other direction is even faster: as documented in the Figma & browser SVG workflow guide, clicking Copy SVG on any of the 76,166 icons in SVG Nexus and pressing Cmd/Ctrl + V directly on a Figma artboard pastes editable vector paths immediately—no third-party Figma plugin or account token required. Before committing final Figma edits back to Git, drop the exported .svg into the SVG Optimizer and SVG-to-JSX Converter to strip stray IDs and convert #000000 to currentColor.