Initializing... drag & drop files here
Supports: PPM
PPM is the raw, uncompressed Portable Pixmap that image-processing and computer-vision tools write — a bare header followed by RGB pixel bytes, with no compression, no transparency, and no metadata. TIFF is the format print shops, scanners, and archives actually accept. Converting PPM to TIFF is the export step at the end of a pipeline (OpenCV, Pillow, ImageMagick, and the Netpbm utilities all emit .ppm): both formats can hold every pixel intact, so done right this is lossless, shrinking the raw bytes while moving them into a professionally readable container.
| Property | Value |
|---|---|
| Family | Netpbm / PNM (Portable Anymap) |
| Origin | Jef Poskanzer's Pbmplus, late 1980s |
| Magic number | P6 (raw/binary, standard) or P3 (plain/ASCII, rare) |
| Color model | RGB, three samples per pixel (BT.709 transfer) |
| Bit depth | 8 bits/channel when maxval < 256; 16 bits/channel when maxval is 256–65535 |
| Compression | None — pixels stored verbatim |
| Transparency | Not supported (no alpha channel) |
| Metadata / color profile | None — header is only width, height, and maxval |
| Typical use | Working intermediate in image-processing and CV toolchains |
The Netpbm specification itself calls this layout "egregiously inefficient" and "highly redundant" — which is exactly why it is meant as a working intermediate, not a file you keep or share.
| Property | Value |
|---|---|
| Full name | Tagged Image File Format |
| Origin | Aldus Corporation, mid-1980s |
| Current revision | TIFF 6.0, finalized June 3, 1992; maintained by Adobe after it acquired Aldus in 1994 |
| Structure | Tag-based container; Baseline TIFF plus optional Extensions |
| Compression | Lossless (LZW, Deflate/ZIP, PackBits) or none; also lossy (JPEG-in-TIFF, added in 6.0) |
| Bit depth | Up to 16 bits/channel in the spec |
| Metadata | Rich — resolution/DPI, color profiles, multi-page, EXIF-style tags |
| Native browser support | Not a web format; only Safari renders TIFF natively, per MDN |
| Best for | Print/DTP, scanning, and long-term archival masters |
.ppm onto the page or click "+ Add Files" to add one or many pixmaps at once; each becomes its own TIFF..tiff or .tif — the bytes are identical, so match whatever your other software expects. Leave Image Resolution on "Keep original" unless you need to rescale.Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — never shared or made public.
It does not have to. A PPM holds raw, uncompressed RGB pixels, and TIFF can store those exact pixels intact, so a lossless conversion is bit-for-bit faithful. The one way to lose quality is to leave Compression Type on its JPEG default, because JPEG-in-TIFF is lossy and would add compression artifacts the PPM never had. Choose LZW, Deflate, PackBits, or None and the TIFF is a perfect copy.
JPEG produces the smallest TIFF, so it is offered as the size-first default — but it is lossy, which is the wrong choice for a clean PPM headed to print or archival. The in-app note says it directly: LZW is the standard for TIFF and offers the best compatibility, while JPEG and WebP compression are often unsupported by professional printing software and standard viewers. For anything you intend to keep, switch to LZW.
Usually, if you compress it. A PPM stores three uncompressed bytes per pixel, so a 1920×1080 image is about 1920 × 1080 × 3 ≈ 6.2 MB of raw data. The same image as an LZW or Deflate TIFF is smaller while staying lossless, because those schemes pack the identical pixels more efficiently — flat graphics and screenshots shrink the most. If you choose None (uncompressed), the TIFF lands at roughly the PPM's size.
No — it preserves exactly what the PPM holds. Most PPMs are 8 bits per channel (maxval under 256), and while the TIFF specification supports up to 16 bits per channel, converting an 8-bit pixmap does not invent depth that was never captured. You get a faithful copy in a more capable, metadata-rich container, not a higher-fidelity image. This converter outputs 8-bit TIFF by default.
Yes. PPM comes in a plain ASCII variant (magic number P3) and a raw/binary variant (P6, the common one). Both encode the same RGB pixel data — the binary form is just more compact on disk — and both convert to TIFF identically.
Neither existed in the PPM to begin with. A PPM stores red, green, and blue only — no alpha channel — and its header carries no ICC color profile, just width, height, and maxval. So the TIFF is fully opaque, and its RGB values are interpreted as plain sRGB. If your pipeline worked in a wider gamut, convert to sRGB before writing the PPM so the TIFF matches what you expect.
No. .tiff and .tif are two spellings of the same Tagged Image File Format, and the bytes inside are identical. The three-letter .tif survives from MS-DOS and early Windows, which capped extensions at three characters under the 8.3 filename rule. This tool exposes a TIFF / TIF toggle so you can match your other software; the PPM to TIF page produces the same file under that name. If you have many formats to send to TIFF rather than just PPM, the broader Image to TIF tool handles them in one batch.
TIFF is the right target for print, scanning, and archival masters. If you need an image to open in a browser or everyday viewer, TIFF won't display in most of them — convert to PPM to PNG for a lossless, universally viewable file, or PPM to JPG for a much smaller lossy one. In our testing, an LZW TIFF made from a 1024×1024 binary (P6) PPM matched the source pixel-for-pixel while taking less disk space than the raw pixmap, whereas the PNG of the same image opened directly in every browser we tried.