SVG Converter
An SVG has no pixels. It is a set of instructions — draw this outline, fill it this color — which is why it stays sharp at any size and why so many places still refuse to accept one. Converting it means choosing a size and drawing it, and the size is the whole decision: pick it here and the drawing is rendered fresh at that resolution, rather than rendered small and stretched. Everything happens in this browser tab.
Drop an SVG to convert
Up to 10.0 MB. It is drawn and encoded in this browser tab — the file is never uploaded.
Drop an SVG above to turn it into a PNG, JPG, or WEBP at any size you like. Because an SVG has no pixels of its own, the drawing is re-rendered at the size you ask for rather than scaled up from a small one — which is why a 16-pixel icon can come out as a crisp 2000-pixel image.
Going the other way — a PNG or JPG into vector paths — is a different job entirely. The PNG to SVG tracer does that one.
Design with the SVG, not just around it
Moda is a vector editor, so an SVG stays an SVG inside it — recolor it, arrange type around it, and export whatever size the platform wants.
Try Moda free →Why the output size matters more than the format
Rasterizing an SVG is the easy direction — there is no guessing involved, just drawing — so the only decision worth making is how big. Get it wrong and you cannot undo it: a PNG exported at 200 pixels will never be sharp at 400, while the SVG it came from would have been sharp at 4,000. That is why this page offers 1x, 2x, 4x and 8x of whatever the file declares, as well as an exact width or an exact height with the other axis following the aspect ratio. Export the size you actually need, and keep the SVG for the next time you need a different one. When in doubt, export larger than the layout calls for: browsers and print both ask for two or three times the nominal size on high-density screens.
When to convert, and when to keep the SVG
Converting is a one-way door — the outlines become pixels and the pixels cannot become outlines again — so the honest advice is to do it only where the SVG is refused. That list is still long: most email clients strip SVG entirely, marketplace and print-on-demand uploaders usually reject it, social platforms will not take it for avatars or share images, several CMSes block it because an SVG can carry script, and Open Graph previews need a raster. Everywhere else — your own site, a design tool, a favicon — the SVG is the better asset and should stay the one you keep. When you do export, PNG is the default worth using for anything a vector drawing usually is; JPG cannot carry transparency, so this page paints your chosen background color under the drawing first.
When an SVG will not render
An SVG drawn as an image runs in what browsers call secure static mode: scripts do not execute, and external resources are not fetched. That is a security boundary, and it is also the most common reason a file that looks right in a design tool comes out blank or missing pieces here. Files that reference a web font by URL, pull in an external stylesheet, or wrap HTML in a foreignObject all lose that content. The fix is in the exporting application rather than here: convert text to outlines and embed anything the drawing needs before you export.
The other direction
Turning a PNG or a JPG into an SVG is not a conversion, it is a redrawing — a tracer has to find the edges in a grid of pixels and follow them, and how well that goes depends entirely on the picture. It works beautifully on logos and line art, and produces an unusable mess on photographs. That job has its own page with the controls it needs: the PNG to SVG tracer, which reports its path and node count so you can see whether the result is worth keeping.
Frequently asked questions
Is my file uploaded?
No. The SVG is read from your disk, drawn into a canvas in this tab, and encoded by your own browser. There is no upload route on this page. As a side effect of how browsers draw SVGs as images, any external resource your file links to is not fetched either — so the conversion makes no network requests at all.
How large can the exported image be?
Up to 10,000 pixels on a side and about 30 megapixels in total. Those two are enforced differently on purpose: an exact width or height past 10,000 is refused with a message, because you asked for a specific number and quietly giving you a different one would be worse; a scale multiplier that lands past either ceiling is scaled back to the largest size with the same proportions, because 8x is a wish rather than a number. The ceilings exist because browsers refuse to allocate very large canvases at all — iOS Safari gives up around 17 megapixels — so an uncapped export would fail on a phone rather than produce a big file.
Why does my export look softer than the SVG did?
Because a raster has to decide what to do at the edges, and a vector never did. Every diagonal and curve gets anti-aliased into part-shaded pixels, which reads as a slight softness next to the infinitely crisp original — and the smaller the export, the larger a share of the drawing those edge pixels are. It is not a fault in the conversion and there is no setting that removes it; exporting at two or three times the size you need and letting the browser scale it down is the fix, which is the same reason phones ship 2x and 3x assets.
My SVG has no width or height. What size do I get?
If the file declares a viewBox, that is used as the intrinsic size and everything works normally. If it declares neither — legal, and common in icon sets meant to be sized by CSS — the page falls back to 512 by 512 and says so, and you can still ask for any exact width you want.