Skip to main content

TIFF to PNG converter

Convert TIFF images to PNG format

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

Browsers cannot display TIFF, so this page ships its own reader. A short JavaScript parser walks the file header, reads the first image directory, pulls the strip offsets and byte counts, and rebuilds the pixels as RGBA image data. From there a canvas re-encodes them with the browser PNG encoder, which is lossless, so the result is pixel-identical to what the reader produced. The one hard requirement is that the TIFF be uncompressed: a file saved with LZW, PackBits, Deflate or JPEG-in-TIFF is refused with a message rather than decoded incorrectly.

Key facts about TIFF to PNG converter

Key facts about TIFF to PNG converter
Accepted compressionCompression tag 1 only. LZW, PackBits, Deflate and JPEG-in-TIFF files stop with an explicit error.
Bit depth handled8 bits per sample. A 16-bit-per-channel scan decodes to noise, so reduce to 8 bit before converting.
Channel layoutsRGB and RGBA are read directly; single-channel greyscale is expanded, honouring the WhiteIsZero photometric flag.
CMYK scansA CMYK TIFF is read as if it were RGBA and comes out wrong. Convert it to RGB in an editor first.
PagesOnly the first image directory is parsed, so page one of a multi-page fax or scan is what you get.
TransparencyAlpha survives when the TIFF carries four samples per pixel; ordinary three-channel scans arrive fully opaque.
Compression gainedPNG applies lossless Deflate with filtering, so nothing is discarded, unlike a JPEG or WebP export.
Typical size deltaA 5.93 MB uncompressed 1920x1080 photo TIFF lands around 2 to 4 MB as PNG; flat graphics drop under 600 KB.
MetadataThe canvas re-encode writes no EXIF, no XMP and no ICC profile, so the PNG is untagged and read as sRGB.
Extensions acceptedBoth .tif and .tiff are recognised by the picker and by drag and drop.
Opens natively inEvery browser, Word and Google Docs, Slack, Figma, mobile galleries: all the places TIFF is rejected.

What happens to your file

Your scan is read with file.arrayBuffer() and parsed by the TIFF reader that is part of this page bundle, so the bytes never leave the tab. The reconstructed pixels are written into a canvas with putImageData, converted once to a PNG data URL so an Image element can hold them, then re-encoded through canvas.toBlob for the download. No request carrying image data is made at any point, and nothing is written to storage: reload the page and the converter starts empty.

About this tool

  1. 1

    Add the scan

    Drop a .tif or .tiff file on the panel, or click to browse. Several files can be lined up in one go.

  2. 2

    Check it decodes

    If the file was saved with compression the converter says so immediately, before any pixels are written.

  3. 3

    Choose a target size

    Keep Original for an exact copy, or cap the longest edge at 4K, Full HD, HD or one of the smaller presets.

  4. 4

    Convert and download

    Press Convert, then save the .png, or take the entire batch down as a single ZIP archive.

Specs & compatibility
Input and outputTakes .tiff and .tif only (image/tiff) and returns .png with the image/png type; any other extension is refused before decoding.
Conversion pathTIFF to PNG runs in three steps: the page's own baseline parser reads the IFD and rebuilds the pixels, because no browser decodes TIFF; the pixels land on a 2D canvas in this tab; then canvas.toBlob with the image/png type returns the finished file.
Browser supportThe TIFF side needs no browser support at all, only a baseline uncompressed source, because LZW, Deflate and JPEG-in-TIFF files stop with an error, while writing the PNG is just as universal, canvas.toBlob having produced it since canvas existed.
Controls for this pairNo quality slider, PNG not being a lossy target here, so the max-dimension presets from 3840 down to 200 px are the only way to hold the PNG down in size against the TIFF.
Batch, caps and namingTwenty TIFF files per run at 500 MB each; one result downloads as a single PNG, several as converted-png-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 TIFF fails before any PNG bytes exist.
  • If the converter reports compressed TIFF, re-export from your scanner software or editor with compression set to None. That is a save option, not a quality setting, so nothing is lost by turning it off.
  • Greyscale scans read correctly, including the inverted WhiteIsZero convention that fax-style TIFFs use, but they leave as three-channel PNGs and are therefore larger than a true greyscale export.
  • For a multi-page document TIFF, split the pages in a desktop tool first. This reader stops after the first directory and gives no warning that more pages existed.
  • PNG keeps every pixel, so it is the right target when the scan will be edited again. Choose JPG or WebP instead only when the file is going straight onto a web page.
  • Very large scans are limited by canvas size, not by the TIFF itself. Desktop browsers top out near 16,384 px per side, and mobile Safari well below that.
  • Get a scanned contract or archival page into a format that email clients, chat apps and web forms will actually preview.
  • Prepare a microscope, satellite or medical capture saved as baseline TIFF for a report or slide deck that cannot embed TIFF.
  • Turn a flatbed scan into an image you can drop straight into Figma, Google Docs or a CMS upload field.
The reader implements the baseline uncompressed path only, so it checks the Compression tag and stops when it is anything but 1. Guessing would produce scrambled pixels rather than an honest error. Re-save the file from Photoshop, GIMP, IrfanView or your scanner utility with compression set to None and the converter reads it straight away.
No. PNG uses Deflate, a lossless algorithm, so the bytes that come out of the TIFF reader are the bytes stored in the PNG. The only way pixels change is if you deliberately pick a size preset that shrinks the image. Colour values, sharpness and detail are otherwise identical to the source scan.
That is expected. A TIFF can chain many image directories together, and this reader follows the pointer in the file header to the first one and stops there. Document scanners commonly write one page per directory. Split the pages with ImageMagick or a desktop viewer, then convert the individual files here.
Only if the TIFF actually has an alpha channel, which means four samples per pixel. Most flatbed and camera TIFFs store three, and those become fully opaque PNGs. When a fourth sample is present the reader copies it into the alpha byte of every pixel and PNG stores it without change.
The pixel loop assumes one byte per sample. With 16 bits per channel it reads alternating low and high bytes as if they were separate colours, which produces visual noise. Convert the file to 8 bits per channel in your editor, save it uncompressed, and it will decode correctly here.
For photographic scans expect roughly a third to two thirds of the uncompressed TIFF size, because Deflate finds far less redundancy in continuous-tone data than in flat colour. Line art, screenshots and documents compress much harder and often land under a tenth of the original.

Related tools

View all

Need the opposite? Try PNG to TIFF

Updated

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