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 AVIF
Converting a .cur image to .avif re-encodes the pixels for a different balance of size, quality, and support. 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 AVIF image
Converting a .cur image to .avif re-encodes the pixels for a different balance of size, quality, and support. 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 .avif file stores a still image (or sequence) coded with the AV1 video codec inside a HEIF-derived container. It is currently among the most efficient image formats deployed on the web, routinely beating JPEG by half at similar quality while adding HDR, wide gamut, and alpha. For this route the practical draw is best-in-class compression among widely supported web formats and 10/12-bit HDR and wide-gamut color, which JPEG cannot represent — balanced against encoding is much slower than JPEG or WebP, especially at high effort settings, which is worth knowing before you commit a large batch.
Why convert CUR to AVIF?
The practical trigger for this conversion is usually a mismatch: with .cur, windows-specific; macOS and Linux use entirely different cursor mechanisms. Switching to .avif buys you best-in-class compression among widely supported web formats, which is why it is the better fit for serving hero images and photo galleries where bandwidth savings are significant. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
CUR vs AVIF at a glance
| Aspect | Windows cursor (.cur) | AVIF image (.avif) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Lossy — discards detail it judges invisible to shrink files |
| 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 | encodes AV1 intra frames; both lossy and a mathematically lossless mode are defined |
| Strongest at | extracting a cursor image for documentation, screenshot annotation or design reference | serving hero images and photo galleries where bandwidth savings are significant |
| Weak spot | windows-specific; macOS and Linux use entirely different cursor mechanisms | encoding is much slower than JPEG or WebP, especially at high effort settings |
| 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 | eXIF and XMP are stored as metadata items in the HEIF container alongside ICC profiles or CICP color signaling, and mainstream encoders preserve them on conversion |
Pick AVIF as the output
Select .avif in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if AVIF is selectable, the route is real and validated.
Convert on your device
Press Convert. Decoding and re-encoding happen on your device using the browser's native image pipeline and hand-tuned encoders.
Verify and download
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid AVIF file. Outputs keep the original filename with the .avif extension.
CUR to AVIF questions, answered
Will converting CUR to AVIF lose quality?
Some. Since cur is lossless-oriented and avif is lossy-oriented, the encoder will discard detail it judges least visible; the quality slider controls how aggressive that is. Keep the original .cur if you may need a pristine master later.
Is it private to convert CUR files here?
Yes — the .cur file is processed inside your browser tab and never uploaded. Decoding and re-encoding happen on your device using the browser's native image pipeline and hand-tuned encoders. Close the tab and the file is gone from memory.
Where will the AVIF file work?
Chrome 85+ (2020), Firefox 93+ (2021), and Safari 16+ (2022) render AVIF natively, covering the overwhelming majority of current browsers. On the desktop, macOS 13+ and Windows (via the AV1 Video Extension) preview it, but plenty of older editing and printing software cannot open it yet.
Will the AVIF file be bigger or smaller than my CUR?
Smaller, usually dramatically so — that is the main reason this route exists. The quality slider trades size against fidelity; the default sits at the point where most people cannot spot the difference.
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.