Add your CUR file
Drop one or more .cur files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
CUR to SVG
Tracing a .cur image to .svg redraws it as outlined colour shapes, so the result can be scaled, recoloured, or fed to a cutter or embroidery digitizer. Free, private, and validated — the file never leaves your browser.
Private for supported formats — processed in your browser
Runs on your deviceConvert supported files
Drop CUR files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.About converting Windows cursor to SVG vector
Tracing a .cur image to .svg redraws it as outlined colour shapes, so the result can be scaled, recoloured, or fed to a cutter or embroidery digitizer. A .cur file is a Windows cursor: a container holding one or more pointer images at different sizes, plus a hotspot — the exact pixel within the image that counts as the click point. It shares its structure with the Windows icon format and differs from it in only two fields.
An .svg file is a Scalable Vector Graphics document: an XML text file describing shapes, paths, text, and gradients mathematically rather than as pixels. Because the geometry is resolution-independent, one .svg renders razor-sharp at any size, from a 16-pixel favicon to a billboard. For this route the practical draw is infinite scalability with no quality loss at any zoom or resolution and tiny file sizes for geometric artwork compared with high-resolution rasters — balanced against utterly unsuited to photographs, which have no economical vector representation, which is worth knowing before you commit a large batch.
Why convert CUR to SVG?
Tracing is what you reach for when a .cur file is the only copy of a logo, badge, or line drawing you have, and you now need it sharp at any size — a large print, a vinyl or laser cut, or the vector outline an embroidery digitizer starts from. Flat-colour artwork traces cleanly; photographs do not, because there are no crisp colour boundaries for the tracer to follow. Expect to tidy the result in a vector editor for production work.
CUR vs SVG at a glance
| Aspect | Windows cursor (.cur) | SVG vector (.svg) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Vector — resolution-independent geometry instead of pixels |
| How it stores data | the directory header is identical to ICO except that the type field at offset 2 is 2 rather than 1 — that single value is what makes a file a cursor instead of an icon | plain XML: elements like <path>, <rect>, <circle>, and <text> with a d-attribute path language for arbitrary curves |
| Strongest at | extracting a cursor image for documentation, screenshot annotation or design reference | logos and brand marks that must stay crisp at every display density |
| Weak spot | windows-specific; macOS and Linux use entirely different cursor mechanisms | utterly unsuited to photographs, which have no economical vector representation |
| Metadata | the hotspot coordinates and the per-entry size table belong to the container rather than to the image, and no raster target has anywhere to record them. The embedded PNG frame's own metadata is carried through the conversion | metadata travels as XML: <title> and <desc> elements aid accessibility, a <metadata> element can hold RDF or XMP, and Creative Commons licensing blocks are common in Inkscape output; EXIF does not apply |
Pick SVG as the output
Select .svg in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if SVG is selectable, the route is real and validated.
Convert on your device
Press Convert. An image tracer running in local JavaScript groups the pixels into flat colour regions and fits outline paths around them, entirely inside your browser.
Verify and download
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid SVG file. Outputs keep the original filename with the .svg extension.
CUR to SVG questions, answered
Will converting CUR to SVG lose quality?
Tracing is an interpretation, not a lossless conversion: the .cur pixels are grouped into a limited set of flat colours and redrawn as outlines, so gradients band, soft edges harden, and fine texture disappears. The quality slider controls how many colours and how much detail survive. The payoff is that the .svg result then scales to any size without ever pixelating.
Is it private to convert CUR files here?
Yes — the .cur file is processed inside your browser tab and never uploaded. An image tracer running in local JavaScript groups the pixels into flat colour regions and fits outline paths around them, entirely inside your browser. Close the tab and the file is gone from memory.
Where will the SVG file work?
Every modern browser renders SVG natively, inline in HTML or as an image source, and design tools from Illustrator and Figma to Inkscape treat it as a first-class format. Gaps appear in contexts expecting rasters — email clients, older office software, some CMS uploaders — which is when rasterizing to PNG at a chosen resolution becomes necessary.
Will the SVG file be bigger or smaller than my CUR?
It depends entirely on the artwork. A flat logo or line drawing traces to a handful of paths and often lands far smaller than the .cur source. A photograph produces thousands of paths and can be many times larger — if that happens, lower the quality to trace fewer colours, or accept that the image is not a good tracing candidate.
What happens to the metadata in my CUR file?
In .cur, the hotspot coordinates and the per-entry size table belong to the container rather than to the image, and no raster target has anywhere to record them. The embedded PNG frame's own metadata is carried through the conversion. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.