@nap.codes vs SVGOMG
SVGOMG is Jake Archibald's legendary SVGO frontend — the SVG optimizer everyone points to. /svg/ uses the same SVGO engine and adds bulk mode plus one-click flow into /pipeline/. When you're optimizing one hero SVG, SVGOMG is perfect. When you're optimizing 40 icons for a design system, /svg/ is faster.
Side-by-side
| Feature | @nap.codes | SVGOMG |
|---|---|---|
| Optimizer engine | SVGO (identical config surface) | SVGO |
| Where it runs | Your browser | Your browser |
| Signup required | No | No |
| Bulk mode | ✓ (drop a folder) | No — one at a time |
| Toggleable plugins | ✓ | ✓ (more granular) |
| Live preview + diff | ✓ | ✓ |
| Chain into other tools | ✓ via /pipeline/ | No |
| Preset config snippets | ✓ for CDN, favicon, print | No |
| Works offline | ✓ | ✓ |
When to pick us
Pick /svg/ when you have a folder of icons to clean up (design-system exports), or when you want to send the output straight into the next tool (/icons/, /favicon/, /squish/) without saving-and-re-uploading between steps.
When to pick SVGOMG
Pick SVGOMG when you're tuning a single hero illustration and want the very granular plugin toggles Jake exposes. His UI has finer control over some specific SVGO plugins (Reuse Paths, Cleanup Numeric Values precision) than /svg/'s streamlined preset system.
Try the @nap.codes version
Bulk-optimize a folder of SVGs. Preset configs for CDN, favicon, and print.
→ Open /svg/