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 PBM
Converting a .cur image to .pbm 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 Portable bitmap
Converting a .cur image to .pbm 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.
A .pbm file is a Portable Bitmap: the simplest image format in common use, storing exactly one bit per pixel — black or white, with no grey and no colour. It carries a two-character magic number, the width and height, and then the pixels, and nothing else. For this route the practical draw is small enough to specify in a paragraph and to write from a shell script and uncompressed and lossless, so nothing is hidden between the header and the pixels — balanced against one bit per pixel — no grey, no colour, no transparency, which is worth knowing before you commit a large batch.
Why convert CUR to PBM?
The practical trigger for this conversion is usually a mismatch: with .cur, windows-specific; macOS and Linux use entirely different cursor mechanisms. Switching to .pbm buys you small enough to specify in a paragraph and to write from a shell script, which is why it is the better fit for masks, stencils and other genuinely two-tone raster data. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
CUR vs PBM at a glance
| Aspect | Windows cursor (.cur) | Portable bitmap (.pbm) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Lossless — every pixel or sample is preserved exactly |
| 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 | two encodings share the extension: P1 stores pixels as ASCII 0 and 1 characters, P4 packs eight pixels into each byte |
| Strongest at | extracting a cursor image for documentation, screenshot annotation or design reference | masks, stencils and other genuinely two-tone raster data |
| Weak spot | windows-specific; macOS and Linux use entirely different cursor mechanisms | one bit per pixel — no grey, no colour, no transparency |
| 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 | none beyond optional # comments in the header. There is no colour profile, no EXIF and no timestamp; a PBM carries dimensions and pixels and nothing else |
Pick PBM as the output
Select .pbm in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if PBM 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 PBM file. Outputs keep the original filename with the .pbm extension.
CUR to PBM questions, answered
Will converting CUR to PBM lose quality?
Since cur is lossless-oriented and pbm is lossless-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .pbm itself requires.
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 PBM file work?
Netpbm, ImageMagick, GIMP and most scientific imaging tools read PBM; browsers and consumer applications do not. Novus Convert decodes both the ASCII and the packed binary form locally and converts to PNG, JPEG, WebP and the other raster targets — which is usually the point, since PBM is a good interchange format and a poor delivery one.
Will the PBM file be bigger or smaller than my CUR?
It depends on the content: two encodings share the extension: P1 stores pixels as ASCII 0 and 1 characters, P4 packs eight pixels into each byte. Convert one representative file first and compare before batch-processing a large set.
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.