Convert TIFF to PNG.
Scanner TIFFs to lossless PNG — right on your own device.
Drop TIFF files here
or browse your files
Paste with ⌘V · or drop files anywhere on the page
Files never leave your device. Everything runs in your browser, nothing touches a server — tools you've used even work offline.
Convert TIFF scans and photos to lossless PNG entirely in your browser — no upload, and no size ceiling imposed by a server. The decoded page is written to PNG pixel-for-pixel, giving editing pipelines and archives a universal lossless file that opens everywhere.
How it works
- Drop files anywhere on the page, click to browse, or paste with ⌘V.
- Pick a quality or preset — or set an exact target size and let the tool find it.
- Compress, compare before/after, and download — individually or as a ZIP.
From archival TIFF to usable PNG
TIFF is the native tongue of scanners and pro cameras, and almost nothing else speaks it. PNG carries the same pixels losslessly and opens in every editor, browser and pipeline. Multi-page TIFFs keep their first page — export pages individually from the scanner when you need them all. Wide-gamut scans are converted to sRGB, with a note when that happens. For sharing rather than archiving, TIFF to JPG lands far smaller, and Compress PNG squeezes the PNG itself.
Frequently asked questions
Is anything lost in the conversion?
No pixels — at the default quality 100 the decode is written to PNG exactly. Wide-gamut color is mapped to sRGB (the tool notes when it applies), and TIFF metadata is not carried over.
What happens to multi-page TIFFs?
The first page converts; the rest are ignored. Scanner software can export pages as separate files when you need every page.
Why is the PNG still large?
PNG is lossless — a detailed 600-dpi scan simply holds a lot of information. If size matters more than perfect pixels, JPG at quality 90 is the practical compromise.
Is it private?
Yes. The conversion happens entirely on your device — the image is read, re-encoded and saved without ever touching a network. There is no server-side queue, no temporary copy in some bucket, nothing to expire or leak. Want proof? Run one file through, switch your connection off, and run another — it still works.