Count the elements in an SVG, find scripts, event handlers and external references, check the viewBox, and see what a sanitiser would strip out.
Waiting for an SVG
Reports what is in the file. The preview is sanitised and sandboxed; the report is of the original.
Nothing to preview yet.
The report appears here
The viewBox and what it means for scaling, every element and colour, every id, and whether a screen reader has anything to announce.
SVG Inspector runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
This answers the questions you have about an SVG before you put it somewhere: what is in it, is any of it dangerous, and will it scale. All three are read off the markup, and none of them require rendering the file or trusting it.
A missing or malformed `viewBox` is the most common reason an SVG will not scale. Without one the browser has no intrinsic coordinate system to map to the element's size, so the image renders at its fixed width and height and ignores the CSS you set — the icon that stubbornly stays 24px when you ask for 32. The inspector reports the viewBox, the width and height attributes, and whether they agree with each other.
On the security side it names what it finds rather than giving a verdict. Script elements, `on*` handler attributes, `foreignObject`, external `href` and `url()` references: each with a count and a location, because the useful output is what the file contains, not a traffic light. An SVG with one external reference might be loading a legitimate font or might be a tracking pixel, and the markup says which.
Nothing is executed and nothing is uploaded. The file is tokenised as text in your browser, which is what makes it safe to inspect an SVG from a source you have reason to doubt — which is, after all, the only kind worth inspecting.
Nearly always a missing viewBox. Without it the browser has no coordinate system to map onto the element's box, so the image renders at its fixed width and height and ignores your CSS. Adding a viewBox matching the original dimensions usually fixes it outright.
The four numbers are min-x, min-y, width and height in the SVG's own coordinate space. For an export it should match the artboard. The inspector shows it alongside the width and height attributes so you can see whether they agree.
It tells you what the SVG contains — scripts, handlers, external references, foreignObject — with counts. It does not give a verdict, because one external reference could be a legitimate font or a tracking pixel and only the markup tells you which.
No. It is tokenised as text, which is what makes inspection safe on a file you do not trust. If you want to see it, the SVG optimizer renders a sanitised copy inside a sandboxed frame.
Any href, xlink:href or url() pointing at a URL outside the document — an image, a font, a filter definition. Each one is a request your page makes on behalf of whoever wrote the file, which is worth knowing about before you ship it.