Image to SVG — Convert to Vector
Trace a raster image into scalable SVG vector paths.
Drop your JPG / PNG / BMP file hereTap to select a file
Supports JPG, PNG, BMP, up to 10MB
What to do next
Related tools
About Image to SVG
Image to SVG is shaped around how people actually use image editing and conversion utilities online: open the page, drop in a file, get the result. Trace a raster image into scalable SVG vector paths. The interface stays out of the way once the work begins so the engine can use the available CPU and memory for the actual transformation.
If you fit any of these descriptions, Image to SVG should slot cleanly into your workflow: illustrators packaging artwork; designers preparing marketing assets; developers preparing UI screenshots. The tool keeps the controls focused on what matters for each of these use cases.
Image to SVG performs the transformation entirely inside the JavaScript runtime. Your file lives in the tab's memory while the engine works on it; the result lives in the tab's memory until the browser triggers the download. Both are released when the tab closes, the way every browser tab releases its memory.
Technically, the work is done by Potrace compiled to WebAssembly, loaded as part of the page. Inputs in JPG, PNG, and BMP format are recognised automatically and validated before the engine begins processing. Files up to 10 MB are supported per run; that ceiling keeps browser memory usage stable on a wide range of devices.
Reach for Image to SVG when you need a predictable result on a single file. The page works on the first visit, the controls are visible without a menu, and the output is delivered the moment the engine finishes.
Image to SVG is intentionally narrow in what it does, which makes it easy to slot into a longer workflow. Take its output, hand it to whichever next tool fits the job, and Image to SVG stays out of your way until the next time you need it.
The download is delivered as `{name}.svg` the moment processing completes — no email link, no "your result will be ready in 5 minutes" queue, no expiry timer. The file is generated in your browser and saved by your browser's normal download flow.
The architecture imposes only the limits the browser itself imposes. The published 10 MB ceiling is conservative; most modern devices comfortably handle inputs up to that size, and the cap exists so the tool degrades gracefully on phones and budget laptops rather than running out of memory.
The transformation in Image to SVG is deterministic — the same input plus the same options produces the same result every run. That predictability matters when the result has to match an upstream specification or be reproducible later.
Some background on the design choices behind Image to SVG: every option you see on the page is there because a real workflow needs it, and every option that is not shown has been deliberately omitted to keep the common case fast. The bias is toward minimal-but-complete.
If you want to get the most out of Image to SVG, three small habits help. Drag-and-drop is faster than the file picker once you get used to it. The keyboard shortcut for downloading the result is whatever your browser uses for "save link as," because the result is a normal download. And if you are working on a sensitive file, processing in an Incognito or Private window is a good extra layer — it leaves no trace in browser history when the tab closes.
For most failure modes, refreshing the page and re-running the job is enough — the engine has no persistent state to corrupt. If the same input fails twice in a row, the input itself is most likely the problem (a truncated file, an unexpected variant of the format, or a stream the engine does not recognise).
As a single-page tool, Image to SVG stays focused on one image editing and conversion step. Multi-step workflows are composed by chaining adjacent tools — each tool produces a standard file the next one can read directly, so a longer pipeline is just a sequence of short tab-and-tab visits.
Open the workspace above to start using Image to SVG. The engine loads on the first interaction so the page itself stays light, and once the tool is warm it processes subsequent jobs quickly. The moment the page is interactive, the tool is ready to do real work on your file.
How it works
- 1Reach the Image to SVG page in your browser to begin.
- 2Drop a JPG, PNG, and BMP file onto the upload area, or click to pick one from your device.
- 3Pick any non-default settings you need. Most users leave the defaults alone for the first run and only revisit if the result needs tuning.
- 4Click to start the job. The engine (Potrace compiled to WebAssembly) processes the input in the page; you can watch the progress indicator until it completes.
- 5Download the result as `{name}.svg`. The file is generated in your browser and saved through your normal download flow.
- 6Re-run with different settings as often as you want. Each run produces a fresh output and the original file on disk is never modified.
Common use cases
- Optimise a product photo so it loads quickly on a slow connection using Image to SVG.
- Compose a mockup banner without bouncing between three different apps.
- Prepare a transparent logo for use over different backgrounds.
- Strip EXIF data from a photo before posting it publicly.
- Apply a quick filter for a social-media post.
- Convert a batch of camera files into web-friendly formats.
- Resize a hero image for a landing page without losing crispness.
- Crop an image down to the section you actually want to share.
- Convert a phone screenshot into a CMS-friendly format.
- Sharpen a slightly soft photo before sending it to print.
FAQ
How does vectorisation work?
The tool traces the edges in your image and converts them into scalable SVG paths using the Potrace algorithm.
Will the SVG look identical to the original?
Best results come from high-contrast images like logos and line art. Photographs will look stylised.
Can I adjust the threshold?
Yes — use the threshold control to fine-tune how much detail is captured in the trace.
Is the source for Image to SVG available?
Image to SVG is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript and WebAssembly to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (Potrace compiled to WebAssembly) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.
Why does Image to SVG feel slow on large inputs?
Most jobs finish in seconds. Speed scales with input size and with how many CPU cycles your browser tab has available — the engine runs in your browser, so it shares resources with whatever else you have open. For inputs near the 10 MB ceiling, expect anywhere from a few seconds to roughly a minute on a typical laptop. Closing other heavy tabs noticeably speeds things up.
How accessible is the Image to SVG interface?
Image to SVG uses native HTML controls wherever possible, which means keyboard navigation, focus rings, and screen-reader labels work the way the platform expects. The drop zone accepts files via the keyboard-accessible file picker as well as drag-and-drop, and result downloads use standard browser download flows. If you spot an accessibility gap, Favtoo treats it as a bug worth fixing.
How do I run Image to SVG over a folder of files?
Image to SVG processes one input at a time by design — it keeps memory usage predictable on lower-end devices and makes results easier to verify. To handle a folder, run the tool once per file; the page stays loaded between runs and remembers your last-used settings, so the second run is essentially instant.
Will Image to SVG keep working in a year?
Image to SVG is updated whenever the underlying engine releases an improvement or a bug fix. Because the tool is delivered as a static page, every visit fetches the latest version automatically — there is no "version" to manage on your end. If a particular release ever changes default behaviour, the change is documented on Favtoo's changelog so you can confirm what shifted.
Does Image to SVG match what professional tools produce?
Image to SVG is built on Potrace compiled to WebAssembly, which is the same class of engine used by professional image editing and conversion pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.
Will Image to SVG ask me to pay to download the result?
Image to SVG is free to use. The processing runs in your browser, which keeps the per-user cost low enough that the tool can be offered openly. The download is the same file the engine produced — you can use it for as many runs as you need.
Which browsers are supported by Image to SVG?
Image to SVG works in any modern browser released in the last few years — Chrome, Edge, Firefox, Safari, Brave, Arc and the major Chromium derivatives are all supported. The underlying engine relies on widely-supported web APIs, so there is nothing exotic to install. If you are on a very old browser version and the tool fails to load, updating to the latest release of your preferred browser is the only fix needed.
Does Image to SVG ask for any browser permissions?
Image to SVG only needs the standard web platform — file picker access for the inputs you choose to load, and optionally clipboard access if you copy the result rather than downloading it. There is no microphone, camera, geolocation or background-permission request, because none of those are needed for the work the tool does.