Add your PGM file
Drop one or more .pgm 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.
Converting a .pgm 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.
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.Converting a .pgm image to .pbm re-encodes the pixels for a different balance of size, quality, and support. A .pgm file is a Portable Graymap: a single-channel greyscale image storing one intensity value per pixel, with the maximum value declared in the header. It is the middle rung of the Netpbm ladder — richer than a one-bit bitmap, simpler than a colour pixmap.
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 .pgm, uncompressed, so files are large relative to PNG for the same data. 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 | Portable graymap (.pgm) | 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 | p2 stores samples as whitespace-separated ASCII integers; P5 stores them as raw bytes | two encodings share the extension: P1 stores pixels as ASCII 0 and 1 characters, P4 packs eight pixels into each byte |
| Strongest at | machine vision and image-processing pipelines that operate on intensity alone | masks, stencils and other genuinely two-tone raster data |
| Weak spot | uncompressed, so files are large relative to PNG for the same data | one bit per pixel — no grey, no colour, no transparency |
| Metadata | none beyond header comments. No colour profile, no EXIF, no acquisition metadata — anything an instrument recorded alongside the pixels has to travel in a separate file | 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 .pgm 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. Decoding and re-encoding happen on your device using the browser's native image pipeline and hand-tuned encoders.
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 pgm 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 .pgm 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.
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 .pgm, none beyond header comments. No colour profile, no EXIF, no acquisition metadata — anything an instrument recorded alongside the pixels has to travel in a separate file. 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.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .pgm → .pbm → .pgm is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.