TIFF to PGM
Convert TIFF to PGM in your browser. Nothing's uploaded.
Runs in this tab. The file stays here.
This runs in your browser. Nothing is uploaded.
Format hubs: TIFF · PGM · Convert
About TIFF to PGM
Converts TIFF to PGM in your browser. Common in scanning and print. Decoded and written in this tab. Output is PGM. Nothing is uploaded.
TIFF is common in scanning and print. Decoded and written in this tab. PGM is netpbm greyscale. Same local encoder path as PPM. This page is only that pair. It isn't a generic dump box that guesses the destination after an upload. If you have a different container, use that format's hub instead of forcing the file through the wrong decoder.
The still is read into memory and converted with a TIFF decoder in the tab (UTIF), then the matching still encoder. You can open the network tab first: you should see this origin load, not a POST of the file. After the page (and encoder, if this is media) has loaded, wifi can go off. That's the whole product, not a badge.
PGM is a lossless or uncompressed target. It won't restore detail a lossy TIFF file already threw away. It stores the current samples or pixels more honestly, usually in a larger file. That's useful when the next tool in a chain insists on PGM, not when you're trying to “improve” a compressed original.
Related conversions sit on this same origin. TIFF to another destination, or another source into PGM, are separate pages so the titles stay specific. The TIFF hub and the PGM hub list every pair I actually ship. Missing pairs are missing because the encoder or decoder isn't here, not because they are paid.
Start from the TIFF hub if you're leaving this format, or the PGM hub if you need to arrive in it. Those pages are indexes, not upload forms. A generic dropdown still exists under Video convert and Audio convert when you would rather pick the destination after you drop the file. Stills use jSquash or canvas; HEIC is the one exception that needs its own decoder. You can disconnect after that core has loaded.
How to use TIFF to PGM
- 1Drop a TIFF file onto the panel, or click to browse. Other formats belong on their own pair pages.
- 2There's no quality slider. PGM keeps the pixels it's given.
- 3Click Convert & download. The PGM file saves on this device.
What it won't do
- Input is TIFF (image/tiff,.tif,.tiff). A different container belongs on its own pair.
- One file per conversion. Batch convert is a different page.
Common questions
Does converting TIFF to PGM upload the file?
No. This is a static page. The still stays in the tab. The network panel should show this origin, not a POST of your TIFF file.
Will TIFF to PGM look or sound the same?
Pixels or samples that are already in the TIFF file are kept. Anything TIFF already discarded is gone. PGM won't invent it back.
Why is there a separate TIFF to PGM page instead of one converter?
Searchers type this pair. A generic convert tool with a dropdown is easy to build and easy to bury. Each pair is its own URL, its own title, and a file picker that expects TIFF. The generic pickers still live at video convert and audio convert if you want a dropdown.
Can I convert PGM back to TIFF on this site?
Yes: that's /convert/pgm-to-tiff. Going back and forth through a lossy codec twice is how you make mud. Do it once if you must.
Related tools
Why this one doesn't upload your file
There is no server to upload to. This page is a static file, and the work happens in your browser using the same graphics and WebAssembly code that renders every other site you visit. Your file is read from disk into memory, processed, and handed back as a download. Once the page has loaded you can disconnect from the network entirely and it keeps working. The longer explanation