About the SVG Viewer
Last updated
SVG Viewer opens SVG files and SVG code in your browser, shows what they look like and what is inside them, and helps when they don't show up the way they should.
What it does
- Draws pasted code, single files, whole folders and .zip bundles, with zoom, panning and four backgrounds.
- Reports the size a file draws at, its width, height and viewBox (with inches, millimeters and points converted to pixels), its colors and the number of elements.
- Finds the problems that most often make an SVG blank or wrong, explains them, and fixes the safe ones on request.
- Shows every shape as a thin outline on request, so hidden or white shapes become visible.
- Changes a color everywhere it is used, sets the size, rotates by 90° and mirrors the drawing.
- Shows the icons inside a sprite sheet (a file of <symbol> elements) as small pictures, each one to open on its own.
- Opens files from a web address, and has a library of 8,587 open-source icons (Tabler Icons, MIT; Lucide, ISC) to open and edit.
- Exports SVG, PNG, JPG, WebP and ICO (plus a complete favicon set) at the size you choose, checks the exported file's pixel size, and copies the SVG as a data URI, CSS, an <img> tag, a React component or a React Native component.
Why it was made
In November 2026, before building it, I tried the SVG viewer pages on the first two pages of Google's results for “svg viewer” with the same nine test files. Of the nine sites I could test, four could not show an icon copied out of a web page, because that code lacks the xmlns attribute. Three gave only a general failure message (“Failed to process SVG”, “Could not render”) when one tag was left unclosed, with no line number, and one marked that broken file as valid. One ran a script from inside a test file. None showed a folder or a .zip as a set of thumbnails, which is what anyone holding a bundle of fifty cut files needs. This SVG viewer is built around those gaps.
| Site | Icon copied from a web page (no xmlns) | File with one unclosed tag | File with a script |
|---|---|---|---|
| A | Shown | Error with line and column | Not run |
| B | “Failed to process” | Same message, no location | Not run |
| C | “Could not render” | Same message, no location | Not run, with a note |
| D | Shown | Small marker on the line | Ran (changed the page title) |
| E | Broken-image icon | Browser's raw error text | Not run |
| F | Shown | Blank preview labelled “Valid SVG” | Blank preview |
| G | Every file is uploaded to the site's server; after the first file it answered “Daily upload limit reached” | ||
| H | Shown | Marked invalid | Not run |
| I | “Couldn't render” | Same message, no location | Not run |
A tenth result could not be tested: it only accepts uploads to its own server, and uploading means accepting its terms. None of the nine opened a folder or a .zip as thumbnails.
How the numbers are checked
Sizes follow the CSS rules for absolute lengths (1 inch = 96 px = 25.4 mm = 72 pt) and the way browsers size an SVG image from its width, height and viewBox. The checks and conversions are covered by automated tests with hand-worked examples, and the export sizes are verified by reading the saved file back. The rules are linked at the bottom of the home page.
What it can't know
The preview is your browser's drawing of the file as an image. Design and cutting programs, inline SVG on a web page, other devices' fonts and outside files referenced by the SVG can all change the result. The terms list these limits in full.
Who runs it
SVG Viewer is run by an independent developer, not a company. It has no advertising and no sponsors, and it is not affiliated with any of the software or sites mentioned on it.
Statistics and privacy
Your files are never uploaded. The site counts page views and which features are used, with my own analytics and a random ID, to see what works and what fails; it never records your SVG code or file names. The privacy policy explains exactly what is recorded and has a switch to turn it off.
Corrections
If the SVG viewer shows a file wrongly, gets a size wrong or misses a problem, please say so through the contact page. A short, non-private piece of SVG code that shows the problem is the most useful thing you can send.