What the Browser Optimizer Strips—and What It Protects

When you paste XML or drop a file into the client-side SVG Optimizer on SVG Nexus, it parses and cleans the document entirely in your browser tab and displays exact before-and-after byte telemetry (for example, shrinking an editor export from 3,639 B to 3,311 B or tighter depending on metadata overhead—without ever inventing fake compression claims).

  • Removed safely: <?xml ...?> prologs, <!DOCTYPE>, Adobe/Inkscape/Sketch/ Sodipodi namespaces, XML comments, empty <g> wrappers, redundant whitespace, and unsafe script/event attributes.
  • Preserved carefully: Root xmlns and viewBox coordinates, currentColor hooks, and visible vector geometry.

Choosing Between Web, App, and Print Presets

Comparing the three built-in presets in SVG Nexus SVG Optimizer
PresetTarget Use CaseKey Behavior & Trade-Off
Web (Default)Inline HTML icons, React/Vue components, CSS Data URIsAggressive metadata removal and compact coordinates; note that it may flatten complex SVG filters that render inconsistently across browsers.
App (Mobile-First)React Native, Flutter (flutter_svg), iOS/Android vector assetsBalances compact path strings with strict SVG element compatibility expected by mobile vector parsers.
Print (High Fidelity)Large-format signage, PDF embeds, high-zoom diagramsRetains higher coordinate decimal precision so subtle Bézier curves never develop micro-steps when scaled up.

Coordinate Decimal Precision and Single-File Workflow Caveats

Comparing verbose 5-decimal path coordinates vs clean 2-decimal precision
<!-- Raw export with excess sub-pixel decimals -->
<path d="M12.00014 2.00031L15.09017 8.26044L22.00002 9.27019" />

<!-- Optimized down to 2 decimals -->
<path d="M12 2l3.09 6.26L22 9.27" />