What this hub does
This page holds both directions: draw an SVG into PNG, JPG, or WebP, and trace a PNG, JPG, or WebP into SVG. The work stays in the browser. Files are not uploaded.
The dedicated pages are still there. Use SVG to PNG when you only need a transparent PNG. Use PNG to SVG to trace a transparent bitmap. Use JPG to SVG when JPEG noise is the problem. Edit paths in the SVG editor.
Which direction to pick
If you already have a vector and the other tool wants a bitmap, export the SVG. Scales are 1×, 2×, and 3×, and the long edge stays at or below 4096 pixels. PNG and WebP keep transparency. JPG has no alpha channel, so the page paints a background color first. The default is white.
If you only have a bitmap and you want edges that stay sharp when enlarged, trace it to SVG. One image at a time. The long edge is scaled to 1024 pixels or less before tracing. Presets are logo, line art, and illustration. This version has no photo preset. The result is an approximation made of paths, not the original layers from a design file.
Stay on this page when you want to try both directions, or when you need to switch the export between JPG and WebP. If the file is already a bitmap and you only want another bitmap, with no paths, use the image converter.
Raster and vector
PNG, JPG, and WebP are raster formats: each pixel stores a color, and enlargement looks soft. JPG is lossy, so edges pick up blocks. See ITU-T T.81. PNG can carry an alpha channel, as defined in the W3C PNG specification.
SVG records shapes instead of a pixel grid. MDN's SVG guide is the reference for icons and interface graphics. When that SVG is loaded in an <img>, scripts do not run. See MDN's img element.
Tracing uses VTracer. Lettering becomes paths. It is no longer text you can restyle.