Rendering stays inspectable
Original and optimized files are shown side by side using the browser’s script-disabled image mode.
Optimize SVG without uploading it
Remove editor debris, shorten paths and minify markup in a dedicated Worker. Your SVG stays on this device, while titles, viewBox and IDs remain under your control.
Drop SVG files hereSVG only · up to 5 MB each
Batch + ZIPNever uploaded
- Elements
- Attributes
- IDs
- viewBox
- Width / height
Rendering comparison
Inspect the markup
Download SVGContinue locally
SVGO · Worker · local
Real SVG optimization, not whitespace removal
Vector editors leave comments, metadata, redundant groups, long color values and unnecessarily verbose paths. SVGO understands SVG structure, so it can simplify those parts while preserving visible output. The optimizer loads only after you provide a file and runs outside the main thread.
IDs stay under your control
Preserve them for CSS or animation, or allow cleanup when the SVG is a self-contained static asset.
Batch still stays local
Multiple SVGs, the ZIP and the icon-studio handoff are created on this device.
SVG optimization questions
Will SVG optimization change how the image looks?
The default preset is designed to preserve rendering, and this page keeps title and viewBox behavior. Always compare complex animated or scripted SVGs before publishing.
Why preserve IDs by default?
CSS, animation, scripts and external files can reference an ID. Removing an apparently unused ID may break behavior that is not visible to the optimizer.
Does this sanitize an untrusted SVG?
No. SVGO is an optimizer, not a security sanitizer. Preview uses an image context where scripts are disabled, but downloaded files should still be treated as their original trust level.
Does the SVG leave my browser?
No request carries the SVG. The page may download its code and the SVGO Worker on first use; your source and result remain local.