Convert TIFF to PNG in your browser
For the TIFF that nothing will open. PNG holds the same pixels exactly and every browser, form and phone reads it. Converted in this tab, never uploaded.
or browse your device. Everything is processed on this device
No TIFF to hand?
A lossless PNG of a photographic scan is many times the size of a JPG you could not tell apart at normal viewing size. If it is going in an email, JPG is the honest answer.
Convert to JPG insteadHow to convert a TIFF to PNG
Both spellings, .tiff and .tif. The decoder is written in this page rather than borrowed from your browser, which has never read TIFF.
The defaults keep every colour, every transparent pixel and the full width. Only reach for the palette if you want the PNG smaller and the image is text or line art.
A .png that opens in every browser, every phone and every upload form, holding the pixels your TIFF held.
Two formats that store the same pixels, and only one that anything opens
TIFF and PNG are both lossless, so converting between them changes the container and not the picture. What changes is who will read it. TIFF is a professional archive format from 1986 that can hold almost any encoding inside it, which is exactly why general software gave up on it: no browser displays one, most web forms reject one, and phones open them grudgingly if at all. PNG does one thing and every piece of software written in the last twenty five years reads it.
Whether the file gets smaller depends entirely on what the TIFF was doing. Scanners and print exports usually write uncompressed or PackBits, which barely compress at all, and against those a PNG is routinely half the size and frequently far less, for identical pixels. A TIFF already written with LZW or Adobe Deflate has had the same sort of treatment PNG applies, so the two land close together and the PNG occasionally comes out slightly larger. Neither outcome is a fault, and this page will not pretend the second one is the first.
If you want the file small rather than exact, this is the wrong page and it is worth saying so. A photographic scan as a JPG will be a small fraction of either file, at a cost you can see only if you go looking for it. Exactness is worth paying for on a document you will read at full size, an image you are about to edit again, or anything with a transparent background to preserve.
TIFF to PNG FAQ
Will the PNG be smaller than the TIFF?
It depends on how the TIFF was stored, and the result panel tells you which case you are in. An uncompressed or PackBits TIFF, which is what most scanners write, usually lands at half its old size or below, and a page of text or line art can fall to a tenth of it. A TIFF already compressed with LZW or Adobe Deflate is doing much the same job as PNG does, so expect it to land close by and do not be surprised if the PNG is slightly larger. If size is the point rather than exactness, convert to JPG instead.
Does converting lose any quality?
No. Both formats store exact pixels, so the PNG holds what the TIFF held, sample for sample. Two controls here can change that, and both are off until you move them: the colours slider, which merges colours on purpose and keeps all 256 where it starts, and the width cap, which redraws the image smaller. Nothing else on this page touches a pixel.
Does a transparent background survive?
Yes. A TIFF with an alpha channel converts to a PNG with an alpha channel and nothing is flattened. This is the main reason to pick PNG over JPG here: JPG has no transparency at all and would put white behind the image, permanently.
What happens to a multipage TIFF?
The first page is converted and the others stay in the TIFF you dropped. Scanners and fax gateways write every sheet into a single TIFF, and a PNG holds exactly one image with nowhere to put the rest. The result panel says how many pages it found, so nothing goes missing quietly. If you need them all, split the TIFF in a viewer first and drop the pages here together.
Which TIFFs can this page read?
Uncompressed, PackBits, LZW and Adobe Deflate, at 8 bits per sample, in RGB, greyscale or palette, with or without alpha. A 16-bit scan is refused rather than quietly halved, and so is a CMYK file, whose four ink channels are not red, green and blue and would decode into the wrong colours. Re-export either as an 8-bit RGB TIFF and it converts fine.
Should I keep the TIFF as well?
If it is an archive master or a print workflow expects it, yes: keep it and treat the PNG as the copy you hand out. If the TIFF only exists because a scanner defaulted to it, the PNG holds the same pixels, is usually smaller and is readable by far more software, and there is nothing left in the TIFF worth the disk except its tag table.
Are my TIFF files uploaded to convert them?
No. The TIFF is decoded and the PNG is written by your own browser, in this tab. There is no upload endpoint in the site for a file to go to, which you can check in your network tools: convert something and watch that no request carries it. Disconnect from the network after the page loads and it still works.
Does this remove EXIF, GPS and AI metadata?
Yes, every time, and there is no way to turn it off. The image is decoded to pixels and encoded again from those pixels alone, so EXIF and GPS, the XMP packet, embedded colour profiles, and any Content Credentials or AI-generation tags the file arrived with do not survive. There is no switch for this, because there is no way to keep them. What no compressor can remove is a watermark written into the pixels themselves, such as the invisible marks some image generators add: those survive re-encoding here and everywhere else.
Related
Same format joins the queue. Anything else re-routes to its own tool.