Skip to main content

PNG to TIFF converter

Convert PNG images to TIFF format

No watermarkFree & unlimited
All processing happens in your browser. No data is sent to any server.

TIFF is a container with a tag directory rather than a single fixed layout, which is why two TIFF files can be nothing alike. The one written here is deliberately the plainest reading of the baseline spec: little-endian byte order, ten directory tags, three 8-bit samples per pixel, photometric interpretation RGB, a single uncompressed strip holding the whole image. Anything that can read a TIFF at all can read this. What it will not do is carry your PNG's transparency, its colour profile or any compression, so the file that comes out is large and literal.

Key facts about PNG to TIFF converter

Key facts about PNG to TIFF converter
TIFF flavourBaseline, little-endian (II, magic 42), ten IFD entries, PhotometricInterpretation 2 and PlanarConfiguration 1.
CompressionNone at all - the compression tag is set to 1. There is no LZW, Deflate or JPEG-in-TIFF option on this page.
ChannelsThree 8-bit samples per pixel. No alpha sample is written, so a transparent PNG pixel is stored as black rather than as white or as a cut-out.
Strip layoutOne strip covering every row, with RowsPerStrip equal to the image height - simple to parse, and easy on readers that dislike multi-strip files.
Exact size134 bytes of header and directory plus three bytes per pixel. A 3000x2000 image is always 18,000,134 bytes.
Bit depthEight bits per channel. A 16-bit PNG is reduced during decoding, so this route cannot produce a high-bit-depth TIFF for retouching.
Resolution tagsXResolution and YResolution are not written, so a layout application will apply its own default rather than a dpi value from the file.
Pages and layersSingle page, single image. Multi-page TIFF, layers and CMYK separations are outside what this encoder produces.
Opens natively inmacOS Preview, Photoshop, InDesign, GIMP, Windows Photos and most scanning or fax software. Chrome and Firefox will not display it in a tab.

What happens to your file

Browsers cannot write TIFF, so the page writes it itself. The decoded PNG is drawn to a canvas, getImageData hands back an RGBA array, the alpha byte of every pixel is dropped as the RGB triples are packed into a buffer, and a DataView writes the file header and the ten tags in front of that pixel block before it becomes a Blob. It is the same story as every converter here - browser decode, canvas, local byte assembly, local download - with no request leaving the tab at any stage.

About this tool

  1. 1

    Add the PNG

    Check the pixel dimensions first: the output length depends on them alone, and large scans grow quickly.

  2. 2

    Flatten transparency beforehand if needed

    There is no alpha sample in the output, so composite the artwork over its intended background colour before converting.

  3. 3

    Resize only if the destination allows it

    Print and archive workflows usually specify pixel dimensions, so leave the presets on Original unless you know the target size.

  4. 4

    Convert and hand off

    The .tif downloads directly, or arrives inside a ZIP when you converted several at once.

Specs & compatibility
Input and outputTakes .png only (image/png) and returns .tiff with the image/tiff type; any other extension is refused before decoding.
Conversion pathPNG to TIFF runs in three steps: an <img> element hands the file to the browser's own PNG decoder; the pixels land on a 2D canvas in this tab; then getImageData feeds a baseline IFD writer that assembles the file in page memory.
Browser supportThe PNG side decodes in every browser ever shipped, while writing the TIFF needs nothing from the browser, the directory being written in the page.
Controls for this pairNo quality slider, TIFF not being a lossy target here, so the max-dimension presets from 3840 down to 200 px are the only way to hold the TIFF down in size against the PNG.
Batch, caps and namingTwenty PNG files per run at 500 MB each; one result downloads as a single TIFF, several as converted-tiff-files.zip, zipped by JSZip 3.10 in page memory.
Device ceilingThe canvas caps it: past roughly 16,384 px a side Chromium refuses the bitmap and iPhone Safari gives up sooner, so an oversized PNG fails before any TIFF bytes exist.
  • If the recipient asked for a compressed TIFF such as LZW or ZIP, this file will not satisfy them - it is uncompressed by design.
  • Preview on macOS and Photoshop both open the result directly, which is the quickest way to confirm a print vendor will accept it.
  • For pure archiving, a PNG holds the same pixels plus the alpha channel in far fewer bytes; TIFF is worth it when a workflow demands the format.
  • Scanned documents converted this way can be enormous - a 600 dpi A4 page is well over 100 megabytes as uncompressed RGB.
  • Meeting a print or publishing submission requirement that specifies TIFF files.
  • Feeding an imaging, scanning or laboratory application whose importer only reads baseline TIFF.
  • Getting artwork into a layout program that treats TIFF as its preferred placed-image format.
No. Only three samples per pixel are written and no ExtraSamples tag declares an alpha channel, so transparency cannot be represented. Because the conversion copies the RGB values as they sit in the canvas, fully transparent pixels arrive with zero in every channel and appear black. Flatten first if that is a problem.
It stores every pixel as three raw bytes with no compression at all, while PNG runs prediction filters and deflate over the same data. The output length is fixed by the dimensions: width times height times three, plus 134 bytes. A flat white image and a dense photograph produce files of identical size.
The visible pixels are preserved exactly - both formats hold 8-bit RGB values, and nothing is quantised or approximated. What disappears is everything around the pixels: the alpha channel, the embedded colour profile, and the PNG's physical-dimension hint. A round trip back to PNG returns the same picture.
Not here. Each input produces its own single-page file, and a batch simply gives you several .tif files in a ZIP. Multi-page TIFF needs an encoder that writes a chain of image file directories, which is beyond what this page builds.
Yes - baseline uncompressed RGB is the most conservative TIFF variant there is, and both read it without complaint, as do Preview, GIMP and Windows Photos. Browsers are the exception: Chrome and Firefox do not render TIFF, so the file will download rather than display.

Related tools

View all

Need the opposite? Try TIFF to PNG

Updated

We use anonymous analytics to improve ToolChamp. No personal data is stored or sold. Privacy Policy