16px X-ray · runs in your browser
What does your icon actually become at 16px?
Your icon looks fine at 512. The browser tab draws it at 16. The macOS menu bar throws its colour away and keeps only alpha. Drop it here and see those pixels before your users do.
No icon handy? Try one:
—
Browser tab · actual size
Your app — Dashboard
Your app — Dashboard
macOS menu bar · template image
Same contexts · 4× for your eyes
Found a problem?
Fix it once.
Prove it every build.
This page shows the symptom. The IconFlow CLI renders your SVG in a pinned Chromium, checks 16px legibility, tray alpha and maskable safe zones, and refuses to ship favicon, PWA, Tauri, Electron and tray files until the review still matches the source.
pip install iconflow
iconflow setup # one-time pinned Chromium download
iconflow check icon.svg --tray-svg tray.svgWhat this page can and cannot tell you
- Your browser does the resampling. Different browsers downscale slightly differently. The CLI pins one Chromium so the same SVG always produces the same pixels.
- The checks are heuristics. “Shapes merge” counts regions that are at least one 16px pixel in area at 128px and compares them with what survives at 16px. It catches closed counters and fused strokes; it cannot judge whether the idea is any good.
- The menu-bar preview is how macOS template images work — colour discarded, alpha kept, tinted for the theme. Windows and Linux trays keep colour, but still draw at 16.
- Nothing leaves your device. The file is decoded by an image element, which never runs scripts inside an SVG, and analysed on local canvases.