filetity

TIFF or TIF -> PNG · Local tool

TIFF to PNG

Turn a TIFF or TIF into a PNG, losing nothing and keeping transparency.

Last updated

  1. 01 / Your device

    the file stays here

  2. 02 / Browser memory

    the work runs locally

  3. 03 / Back to you

    saved on this device

When you would use this

Situations, not settings.

A scan you will edit again
PNG is lossless like the TIFF, so cropping or correcting it later costs nothing in quality.
Artwork or a diagram with transparency
A TIFF with an alpha channel keeps it as a PNG, where JPG would fill the transparent areas in.
Putting a scan on a web page
No browser displays a TIFF, so it has to become something else before anyone can see it in a tab.

How it works / no cloud

A conversion engine, not an upload form.

No browser can display a TIFF, so filetity decodes it here rather than handing the file to the browser and hoping. The reader covers uncompressed, LZW with the horizontal predictor, Deflate, CCITT Group 3 and Group 4 fax, big and little endian byte order, RGB and RGBA, 8 and 16 bit grey, palette colour and 1 bit black and white, then draws the pixels on a canvas and encodes a PNG, which is lossless, so the pixels that come out are the pixels that went in. Everything outside that set is refused by name instead of guessed at, because a decoder that quietly returns a blank image is worse than one that says no. Nothing is uploaded.

  • Offline ready
  • Installable app
  • No file limit queue

Straight answers

No accordion. Nothing hidden.

Is it free?
Yes, with no watermark and no page limit.
Does it need an account?
No. There is no account system.
Is my file processed on my device?
Yes. The file is read by your browser and never uploaded. There is no server to send it to.
What formats are supported?
TIFF and TIF in. PNG out, one file per image, or a ZIP when you convert several.
What are the limits?
Scans work, including the fax formats. CCITT Group 3 and Group 4, which is what fax machines and most document scanners write, are decoded here, in both bit orders and both polarities. What is still refused is refused by name rather than handed back damaged: PackBits, JPEG inside a TIFF, CMYK colour, floating point samples, separate colour planes, and tiled colour images. A multi-page TIFF is refused too, and says how many pages it has, because one image in means one file out here. Worth knowing: the CCITT decoder has been tested against files written by libtiff and by Pillow, not against output from a physical fax machine, so an unusually old file may still be turned away.
Does it work on mobile?
Yes, on any modern mobile browser. Large files are limited by the memory the phone gives the browser.
Does it work offline?
Yes. Nothing is downloaded to make this work, so it keeps working with no network connection once the page has loaded.
Is anything lost going from TIFF to PNG?
No. Both are lossless, so every pixel survives and the image can be edited again without degrading. That is the reason to pick this over TIFF to JPG for a scan, a diagram or artwork.
Does transparency survive?
Yes. A TIFF with an alpha channel comes out as a PNG with the same alpha, because PNG has a real one. The transparent areas are not filled in.
Why is the PNG sometimes larger than the TIFF?
Because a lot of TIFFs are already compressed, usually with LZW or Deflate, and for photographs PNG is not always better at it. The file size may go either way. Nothing is lost either way, which is the thing PNG guarantees and file size does not.
What about 16 bit TIFFs?
A 16 bit greyscale TIFF is read and converted, using the high byte of each sample, which is what libtiff does. The output PNG is 8 bit per channel, so a scientific or medical image that genuinely needs 16 bit depth should stay a TIFF.

How this one works

Keep working locally

7 available · more coming