Add your JPEG file
Drop one or more .jpeg 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 .jpeg 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 .jpeg image to .pbm re-encodes the pixels for a different balance of size, quality, and support. A .jpeg file is byte-for-byte the same format as a .jpg file; only the extension spelling differs. The four-letter .jpeg ending is the format's full name, while .jpg exists because early MS-DOS and Windows file systems limited extensions to three characters. Renaming between the two changes nothing about the image data.
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 .jpeg, two spellings for one format confuse filters, upload validators, and scripts that match extensions literally. 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 | JPEG image (.jpeg) | Portable bitmap (.pbm) |
|---|---|---|
| Format type | Lossy — discards detail it judges invisible to shrink files | Lossless — every pixel or sample is preserved exactly |
| How it stores data | identical bitstream to .jpg: DCT-based coding defined in ITU-T T.81 / ISO/IEC 10918-1 | two encodings share the extension: P1 stores pixels as ASCII 0 and 1 characters, P4 packs eight pixels into each byte |
| Strongest at | workflows on macOS and Linux where tools historically defaulted to the .jpeg spelling | masks, stencils and other genuinely two-tone raster data |
| Weak spot | two spellings for one format confuse filters, upload validators, and scripts that match extensions literally | one bit per pixel — no grey, no colour, no transparency |
| Metadata | eXIF, XMP, IPTC, and ICC profiles are stored exactly as in .jpg files, and all of it survives a simple rename between the two extensions | 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 .jpeg 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.
No new loss is introduced — since jpeg is lossy-oriented and pbm is lossless-oriented, everything the .jpeg file still contains is carried over exactly. What was already discarded by the original lossy encode cannot be recovered, though; converting to .pbm does not "restore" quality.
Yes — the .jpeg 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.
Larger, sometimes much larger. A lossless .pbm must store every pixel or sample the decoder produced, without the perceptual shortcuts .jpeg used. Use this route for editing headroom, not for saving space.
In .jpeg, eXIF, XMP, IPTC, and ICC profiles are stored exactly as in .jpg files, and all of it survives a simple rename between the two extensions. 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.