JPG to SVG Converter

Convert JPG to SVG: What This Tutorial Covers

This converter traces your JPG and rebuilds it as a genuine SVG — real vector paths and Bézier curves, not the original pixels wrapped in an <image> tag. That distinction decides whether the output is useful at all: tracing produces clean, infinitely scalable results from logos, icons, stencils, and flat high-contrast graphics, and produces bloated nonsense from photographs. This walk-through covers the single setting the page exposes, what the tracing engine is doing behind it, the two slider values you should avoid, and the errors that account for almost every disappointing result.

How to Convert JPG to SVG

1. Upload Your JPG File: Drag and drop your .jpg, .jpeg, or .jfif onto the page, or click "Add Files" to browse. Several images can be queued and traced with the same setting.
2. Set Number Precision: Under Advanced Options, the Number precision slider runs from 1 to 10 and sits at 6. The on-page note recommends 4 to 6 for most work; keep it at 8 or below, for the reason described in the walk-through.
3. Clean the Source First (Optional): The tracer follows exactly what is in the pixels, including JPEG blocking and background clutter. Crop out anything you do not want vectorized and start from the largest, sharpest copy you have.
4. Convert and Download: Click "Convert" and download your SVG. No sign-up, no watermark.

Walk-through: What Number Precision Actually Does

An SVG describes shapes as coordinate paths in plain text, like M12.34,56.78 C.... The slider on this page feeds two things at once inside the tracing engine: how precisely those coordinates are written down, and how finely colours are separated before shapes are found.

• Lower it (1–3) for the smallest file. Coordinates round to fewer decimals and similar colours merge into single shapes, so the text shrinks and the drawing simplifies. On flat artwork the visual difference is usually invisible — two or three decimal places is the professional norm for hand-authored SVG.
• Leave it at 4–6 for most work. This is the range the page itself recommends: crisp edges, faithful colour separation, sensible file size. Start here and only move if the result tells you to.
• Push to 7–8 only for genuinely intricate art. More decimals and finer colour separation preserve sub-pixel curve detail and subtle shade boundaries, at a real cost in file size and path count.
• Do not use 9 or 10. Colour precision in this engine is measured in bits per channel and tops out at 8, which is already full 24-bit colour. Values above that are outside the engine's accepted range and the trace is rejected rather than producing a more detailed file. There is nothing above 8 to gain.

Precision cannot add detail the trace did not find — it only decides how exactly the found shapes are recorded. If the output looks blobby, the fix is a better source image, not a higher slider value.

What Traces Well and What Doesn't

The Tracer Settings Behind the Slider

The page exposes one slider, but the engine underneath runs with a fixed configuration worth knowing, because it explains several results people find surprising.

Common Errors and How to Fix Them

• "The SVG looks blobby and posterized." You traced a photograph. Continuous tone has no edges to follow, so the tracer approximates millions of shades as flat regions. Keep photos as raster — JPG to PNG or WebP — and reserve tracing for flat artwork.
• "There's a giant rectangle behind my logo." That is the stacked layer hierarchy doing its job. The photo's background was a colour, so it became a vector shape like any other. Delete that path in an SVG editor, or remove the background from the source image before uploading.
• "The SVG is bigger than the JPG was." Busy or noisy sources produce thousands of paths, one per colour region, and path data is text. Lower the precision slider, simplify or crop the source, or accept that this image is not a vectorization candidate.
• "Edges are fuzzy and colours smear into each other." JPEG compression itself adds blocking and ringing around edges, and the tracer follows it faithfully. The same artwork saved losslessly traces sharper — try PNG to SVG if you can get a PNG copy.
• "Thin lines and small text vanished." Fine features fall under the speckle threshold or below the resolution the trace can resolve. Start from a larger version of the image; anything under a few hundred pixels gives the tracer too little edge information to work with.
• "The conversion failed." Check the slider. Values of 9 or 10 exceed the engine's colour-precision limit and are rejected. Set it to 8 or lower and run it again.

When This Doesn't Work

Vectorization is the wrong tool for photographs, screenshots containing text, and anything built from gradients or soft shadows — the trace will be inaccurate and the file bloated. It is the right tool for flat-colour graphics with clear boundaries. Note also that tracing rebuilds the picture from scratch: it recovers shapes, not structure, so you will not get your original layers back and any lettering arrives as outlined curves rather than live type. If you need to go the other way afterwards, SVG to PNG rasterizes cleanly at any size you specify.

Frequently Asked Questions

Does this embed my JPG inside an SVG, or actually vectorize it?

It vectorizes. Many "converters" simply base64-encode your raster image into an <image> element inside an SVG wrapper — the file has an .svg extension but it is still the same pixels, and enlarging it still blurs. This page runs a real tracing engine that finds edges and colour regions and writes them as <path> elements with Bézier curve data, so the output genuinely scales without loss on suitable artwork.

What Number precision value should I use?

Start at 4–6, which is what the page recommends and where most artwork lands. Drop toward 1–3 when you want the smallest possible file and can accept simplified shapes and merged colours. Move to 7–8 only when intricate detail is genuinely being lost. Do not go to 9 or 10 — the engine's colour precision is capped at 8 bits per channel, so those values are out of range and the trace will not complete.

Will a photograph convert into a clean, scalable vector?

No. Photographs have continuous tone and millions of colours, so tracing has to approximate them as many flat filled shapes. The result looks posterized, loses all fine texture, and is frequently several times larger than the JPG it came from. There is no slider setting that fixes this — it is a mismatch between what photographs are and what vector graphics can represent. Keep photos as raster images.

Why is there a large filled rectangle behind everything in my SVG?

Because the tracer stacks colour layers on top of a full-size background layer. That approach avoids the hairline white seams you get when adjacent shapes are cut out of each other, but it means the background colour of your JPG becomes an ordinary vector path in the output. Select and delete that bottom path in Inkscape, Illustrator, or Figma, or remove the background from the source image before you convert.

Why does my JPG trace worse than a PNG of the same artwork?

Because JPEG is lossy. Its compression introduces blocking and ringing artifacts, particularly around the hard edges that tracing depends on, and the tracer follows that wobble as though it were real detail. It also blurs colour boundaries, so flat areas that should merge into one shape split into several. If you have access to a lossless copy of the artwork, PNG to SVG will give you cleaner paths from the same picture.

Is the resulting SVG editable, and do I get my layers back?

You get fully editable vector shapes — you can recolour, rescale, reshape, and delete individual paths in any SVG editor. What you do not get is your original document structure. The trace rebuilds the image as filled paths grouped by colour, so named layers are gone and any text has become outlined curves rather than live, re-editable type with a font attached.

Which apps and browsers open the output?

SVG is a W3C standard and is rendered natively by Chrome, Firefox, Safari, and Edge, so the file works directly in a web page or as an <img> source. On the desktop it imports into Illustrator, Inkscape, Figma, Affinity Designer, and the cutting software used by Cricut and Silhouette machines — which is why logo and stencil tracing is far and away the most common reason people use this conversion.

What happens to my uploaded file?

It is uploaded over an encrypted connection, traced on our servers, and deleted automatically a few hours afterwards. There is no sign-up, no watermark, and nothing you upload is shared or made public.