How to find duplicate SVG IDs before they break your icons
An icon that looks perfect on its own can break the moment it shares a page with another icon. The cause is almost always the same: both icons define the same id — paint0_linear, clip0, filter0 — and the browser resolves every url(#...) reference to the first definition it finds. One icon quietly borrows the other's gradient, and if the first icon is hidden inside a closed menu, the second can vanish completely.
This tool finds the collision where the icons already are: on your own device. When you paste markup or drop files here, your browser:
- Lists every id — with the element it belongs to and its line number — and flags any id defined more than once, in one file or across the whole batch.
- Maps every reference — url(#...) in fill, clip-path, mask and filter attributes and in style blocks, href and xlink:href, aria-labelledby and aria-describedby, and #id selectors in style blocks — and names any reference that points at an id nothing defines.
- Fixes it with one prefix — every id becomes prefix-id, every reference is rewritten to match, and a second definition of the same id becomes prefix-id-2, so the fixed file has no duplicates left and renders exactly as the original did alone.
What makes this checker different
The pages that top the results for this search are guides that tell you to paste a snippet into the browser console, a build-time optimiser plugin, or an editor extension that only works inside one program — and the one generic checker that exists takes a plain list of ids, one per line, so it cannot see SVG markup, references, or cross-file collisions at all. This page is the only free, fully client-side dedicated SVG duplicate-id checker we found that parses the markup itself: ids with elements and line numbers, every reference mapped, dangling references named, several icons checked together for the Figma-export failure, and a one-click fix that downloads the corrected file — with no daily limits, no account and no upload — plus a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.
When is checking the right choice — and when is it the wrong one?
Checking is right whenever SVG markup is about to be inlined: icons pasted into HTML, a component library, a design-system sprite, or several Figma exports landing on the same page. It is the wrong choice for an SVG that will only ever load through an img tag — each img is its own document, so ids there can never collide — and for a file you never inline, where the ids are namespaced by the file itself. If your icons already live in a sprite with unique ids, this check will simply come back clean.
Honest limitations
A text scan, not a validator
This tool reads ids and references as text. It cannot certify that your markup is well-formed XML — a broken tag elsewhere in the file is outside what it checks.
External references are out of scope
A url(#id) that points into another file, or an href to a different document, cannot be resolved from the text you paste. Those references are listed, not verified.
SMIL event references are flagged, not fixed
References such as begin="id.click" are animation triggers, not id lookups in the usual sense. The checker warns you when it sees one instead of rewriting it.
References resolve to the first definition
When an id is defined twice, the fix points every reference at the first definition and renames the second one. If your second definition was the intended target, rename it by hand instead.
It never changes your file
This tool only reports and downloads a fixed copy. Your original file is never modified — the fix is a new download, and the preview shows the icon as it renders.
Not an optimiser
Fixing ids does not minify, clean up, or shrink your SVG. Run an SVG optimiser after fixing the ids if you want the file smaller as well as correct.