Add your PBM file
Drop one or more .pbm 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 .pbm image to .tiff 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 .pbm image to .tiff re-encodes the pixels for a different balance of size, quality, and support. 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.
A .tiff file is a Tagged Image File Format raster, the long-standing archival and prepress standard for images that must not lose a single bit. Its tag-based structure lets one .tiff hold multiple pages, layers of metadata, and pixel formats from 1-bit fax scans to 32-bit floating-point channels. For this route the practical draw is losslessly preserves any bit depth and color space you throw at it and decades of stability make it the safest long-term archival bet — balanced against files are huge — often 10x a visually identical JPEG, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .pbm, one bit per pixel — no grey, no colour, no transparency. Switching to .tiff buys you losslessly preserves any bit depth and color space you throw at it, which is why it is the better fit for archival masters for museums, libraries, and digitization projects. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | Portable bitmap (.pbm) | TIFF image (.tiff) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Lossless — every pixel or sample is preserved exactly |
| How it stores data | two encodings share the extension: P1 stores pixels as ASCII 0 and 1 characters, P4 packs eight pixels into each byte | structured as Image File Directories (IFDs) of numbered tags, allowing multiple images per file |
| Strongest at | masks, stencils and other genuinely two-tone raster data | archival masters for museums, libraries, and digitization projects |
| Weak spot | one bit per pixel — no grey, no colour, no transparency | files are huge — often 10x a visually identical JPEG |
| Metadata | 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 | eXIF is itself structured as TIFF tags, so TIFF holds it natively, alongside XMP packets, IPTC records, ICC profiles, and GeoTIFF georeferencing tags |
Drop one or more .pbm 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 .tiff in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if TIFF 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 TIFF file. Outputs keep the original filename with the .tiff extension.
Since pbm is lossless-oriented and tiff is lossless-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .tiff itself requires.
Yes — the .pbm 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.
Every serious image editor, scanner driver, and DTP application on Windows, macOS, and Linux reads TIFF, and both major OSes preview it natively. Web browsers are the gap: Chrome, Firefox, and Edge will download rather than display a .tiff, so web delivery always requires conversion to PNG, JPEG, or WebP.
It depends on the content: structured as Image File Directories (IFDs) of numbered tags, allowing multiple images per file. Convert one representative file first and compare before batch-processing a large set.
In .pbm, 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. 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 .pbm → .tiff → .pbm is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.