Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
This converter traces your JPG and rebuilds it as a true SVG — real vector paths and curves, not the original pixels wrapped in an SVG wrapper. That distinction decides whether the result is useful: tracing produces clean, infinitely scalable output for logos, icons, line art, and flat high-contrast graphics, but it does a poor job on photographs. This page walks through the conversion, the one setting that matters, and the cases where tracing is the wrong tool.
.jpg, .jpeg, or .jfif file onto the page, or click "+ Add Files" to browse. You can queue several images and trace them with the same setting.An SVG stores shapes as coordinate paths in plain text, like M12.34,56.78 C.... Number precision sets how many decimal places those coordinates keep:
Precision does not add detail that the trace did not find — it only decides how exactly the found paths are written down. If the output looks blobby, the fix is a cleaner source image, not a higher precision value.
Vectorization is the wrong tool for photographs, screenshots with text, and any image with smooth gradients or thousands of colors — the trace will be inaccurate and the file bloated. It shines on flat-color graphics: logos, icons, stencils, silhouettes, and line drawings. If you only need the JPG to behave like other assets in a vector workflow but don't need true scalable paths, a raster format may serve you better — and if you later need a flat image back from an SVG, the reverse SVG to PNG conversion rasterizes it cleanly.
It vectorizes. The converter runs the open-source vtracer engine, which traces shapes and edges and rebuilds the image as real SVG paths and Bézier curves — it does not base64-encode the original pixels into an <image> tag. That means the output is genuinely resolution-independent for suitable artwork, rather than the same raster picture in a new container.
No. Photographs have continuous tones and millions of colors, so tracing approximates them as many flat color shapes — the result looks posterized and inaccurate, and the file is often far larger than the JPG. Tracing is designed for logos, icons, and line art with limited colors and clear edges. For a photo, keep a raster format.
JPEG is a lossy format: it introduces compression blur and block artifacts that the tracer faithfully follows, softening edges and adding stray shapes. The vtracer engine works best on losslessly compressed input, so the same artwork saved as a PNG generally traces with sharper, cleaner paths.
For most artwork, 4–6 is the sweet spot — crisp paths at a reasonable file size. Drop toward 1–3 when you need the smallest possible file and can accept slightly rounded coordinates; only push toward 8–10 if you genuinely need sub-pixel accuracy, since beyond 6 the extra decimals usually add bytes without a visible change.
Yes. SVG is a W3C XML-based standard supported by Chrome, Firefox, Safari, and Edge — caniuse reports roughly 97% global browser support — and it imports into Illustrator, Inkscape, Figma, and most vector editors. In our testing, a simple two-color logo traced at precision 5 produced a compact SVG that opened identically in the browser and in Inkscape.
Partly. You get vector shapes you can recolor, scale, and reshape in any SVG editor, but the trace rebuilds the picture as filled paths grouped by color — it does not recover your original layers, and any text becomes outlined curves rather than live, editable type.
Yes. Your JPG is uploaded over an encrypted connection, traced on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, and nothing is shared or made public.