Who built VectorizeThis?
I’m Maxime Desrosiers, the developer behind VectorizeThis. I have spent more than a decade building websites and front-end interfaces, with particular expertise in WordPress. I also created ShapeDividers.com, a tool for generating decorative SVG section dividers and the CSS needed to use them.
Building ShapeDividers taught me how much SVG structure and compression matter. A vector can look simple on screen while containing unnecessary points, attributes, or markup. Keeping the generated CSS lightweight meant learning how to preserve the visible result without carrying avoidable code.
Why I built it
VectorizeThis began with a problem I encountered during a homepage redesign. I asked ChatGPT for a fresh design, and the result used several appealing icons. The original icons were too small, so I asked for larger versions one by one. Those replacements arrived as PNG files: visually useful, but large, harder to recolor, and awkward to maintain in a website.
I tried several online image-to-SVG converters. The bulk converters I tested often produced weak traces. Some single-file tools introduced strokes where the artwork did not need them. Many results were larger than necessary, so I still had to run them through SVGOMG before using them.
That process felt like something a single tool should handle better: evaluate more than one trace, keep the useful structure, reduce excess markup, and still let the person inspect and adjust the result.
What VectorizeThis does
VectorizeThis turns supported raster images into SVG path geometry in the browser. It can test several tracing configurations, compare the candidates, optimize the selected SVG, and show checks that matter for the intended use. Users can adjust settings, edit a small detected color palette, copy the markup, or download individual and batched results.
The converter is local-first. Image decoding, tracing, comparison, and SVG preparation happen on the user’s device. Product analytics describe actions and settings so the tool can be improved; they do not include source image bytes or filenames. A source image is sent only when a user deliberately attaches it to feedback and consents to sending it.
See how VectorizeThis evaluates vectorization results.
What it does not claim
Automatic tracing is an interpretation of pixels, not a recovery of the designer’s original vector file. Photographs, gradients, compression artifacts, soft shadows, tiny details, and low-resolution sources can all affect the result.
Fabrication-oriented presets and checks help prepare and inspect geometry, but they are not certification for a specific cutter, laser, CNC machine, material, or third-party application. Users should inspect the downloaded SVG and test it in their own workflow before production.
Help improve the tool
If an output looks wrong, use Send Review in the converter or contact VectorizeThis. A clear description, the chosen use case, and the settings that caused the problem are useful. You can optionally send a source image when reproducing the issue would otherwise be difficult.
For details about data handling and use of the service, read the Privacy Policy and Terms and Conditions.