Who builds vectortrace

Who operates it

vectortrace is built and operated by SIA DEVINTRY, a company registered in Jelgava, Latvia. It is a small operation: one product, one server, and no investor to answer to about which features ship.

The full provider identification — the registered address, the company number and the VAT number — is on the imprint, which is also the page to cite if you need our details for an invoice or a supplier record. The terms of use are at Terms.

What the product is

vectortrace converts raster images — PNG, JPG, WebP, BMP and GIF — into editable vector files: SVG, PDF, EPS and DXF. The tracing engine is a Rust workspace compiled to WebAssembly, and it runs in a Web Worker inside your own browser tab.

That is the whole architecture, and it has one consequence worth stating plainly: your image is never uploaded. There is no upload request to inspect and no bucket to audit, because the file never leaves the machine you opened the page on. The exception, spelled out in the privacy policy, is the public HTTP API, which by definition receives the image you send it and processes it in memory without writing it to disk.

Why the tracing runs in your browser

Two reasons, and the second one is what makes the first one affordable. The first is that a lot of the artwork people trace is not theirs to send: an unreleased brand mark, a client file under a non-disclosure agreement, a scan from a medical or legal document. A tool that uploads those to be traced is asking for a decision the person often cannot make.

The second is that tracing is CPU-bound work on a single image, and the machine in front of you already has a CPU sitting idle. Moving that work to a server would buy queueing, upload waits and a bill that grows with every conversion, in exchange for nothing the visitor can see. Keeping it local means previews are free and unlimited, the converter works on a plane, and the infrastructure behind the site stays one small server in the EU.

What the choice costs us is honest to state: the engine has to fit in a WebAssembly module and run on your CPU, so it cannot throw a large model on a rented graphics card at a difficult image. That is the trade, and the benchmark page is where you can see what it currently buys and what it currently costs.

How quality is measured

Tracing quality is measured, not asserted. The published run covers the committed smoke (30 fixtures) corpus, was taken on 2026-09-05, and measured engine 0.3.34. Every figure it produced is transcribed from the same baseline file the continuous-integration gate compares against, so the numbers on the site are the numbers a regression would fail on.

That includes the unflattering ones. The run reports boundary error, region-count error and node-count ratio together, because a tracer can buy an excellent boundary by emitting far more nodes than the artwork needs, and a page that shows only the good half is an advertisement. The corpus, the metrics and the commands to reproduce them are at Benchmarks.

How to reach us

Write to hello@vectortrace.app. Email is the only support channel — there is no phone line, and pretending otherwise would only waste your time.

Bug reports about a specific image are the most useful thing you can send, because the engine is judged on real artwork rather than on synthetic shapes. A description of what you traced, what you expected and what you got is enough; the file itself is welcome but never required.