Add your CR2 file
Drop one or more .cr2 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.
Developing a .cr2 camera file into .pbm turns unprocessed sensor data into a finished image any app can open. Free, private, and validated — the file never leaves your browser.
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.Developing a .cr2 camera file into .pbm turns unprocessed sensor data into a finished image any app can open. A .cr2 file is a Canon RAW photograph, the second-generation format Canon's DSLRs wrote from 2004 until the switch to CR3 in 2018. It records the sensor's mosaiced readout before white balance, sharpening, or color rendering are baked in, giving full latitude to reprocess the shot later.
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.
The practical trigger for this conversion is usually a mismatch: with .cr2, files run 20-40 MB where a JPEG would be a few megabytes. 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.
| Aspect | Canon RAW 2 (.cr2) | 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 | tIFF container with multiple IFDs holding the raw sensor image and several embedded JPEG previews | two encodings share the extension: P1 stores pixels as ASCII 0 and 1 characters, P4 packs eight pixels into each byte |
| Strongest at | developing photos from Canon DSLRs with full exposure and white-balance latitude | masks, stencils and other genuinely two-tone raster data |
| Weak spot | files run 20-40 MB where a JPEG would be a few megabytes | one bit per pixel — no grey, no colour, no transparency |
| Metadata | full EXIF including lens and exposure data, extensive Canon MakerNotes, and XMP sidecar or embedded metadata are all standard; MakerNotes hold camera-specific details generic tools may not parse | 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 |
Drop one or more .cr2 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.
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.
Press Convert. A LibRaw WebAssembly decoder demosaics the sensor data in your browser and renders a developed image ready for export.
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.
Since cr2 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.
Yes — the .cr2 file is processed inside your browser tab and never uploaded. A LibRaw WebAssembly decoder demosaics the sensor data in your browser and renders a developed image ready for export. Close the tab and the file is gone from memory.
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.
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.
In .cr2, full EXIF including lens and exposure data, extensive Canon MakerNotes, and XMP sidecar or embedded metadata are all standard; MakerNotes hold camera-specific details generic tools may not parse. 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.