TIFF to PNG Converter

How to Convert TIFF to PNG Online

1. Upload Your TIFF Files: Drag and drop or click "+ Add Files" to select.tiff and.tif files from your computer. Batch upload is supported, and multipage TIFF files are handled — each page is extracted as its own PNG.
2. Pick a Quality Preset: Default is "Very High (Recommended)" which preserves the source bit depth and color data. Drop to "High" or "Medium" if you want noticeably smaller PNG output and don't need the original gradients pixel-perfect.
3. Resize or Reduce Colors (Optional): Use Image Resolution to keep the original size, scale by percentage, or enter custom width/height in pixels. Under Colors, leave "ORIGINAL" for full truecolor, or pick "By Color Reduction + Dither" with a palette size (2-256 colors) to shrink files dramatically for diagrams, screenshots, and pixel art. Compression level (1-9) and Compression speed (1-9) trade encode time against final size — leaving defaults (6 and 4) is fine for most scans.
4. Convert and Download: Click "Convert" and grab your PNGs individually or as a ZIP archive. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared.

Why Convert TIFF to PNG?

TIFF (Tagged Image File Format, finalized as Revision 6.0 in 1992 by Aldus/Adobe) is the archival workhorse for scans, prepress, and microscopy — it stores layers, multiple pages, 32-bit-per-channel floats, and CMYK in a single container. But no mainstream web browser renders.tiff inline, and most operating systems need a plug-in or pro app to even thumbnail it. PNG (W3C-standardized in 1996, latest Fourth Edition in 2025) is the lossless format the web actually settled on. Converting from TIFF to PNG is what you do when an archival or scanned file needs to leave the studio.

• Embed scans in web pages and CMSes — WordPress, Shopify, Squarespace, and Webflow all reject.tiff uploads by default. PNG goes in without a plug-in and renders in every browser back to IE6.
• Email and chat attachments shrink dramatically — a 24-bit lossless TIFF often weighs 3-5× more than the equivalent PNG because TIFF defaults to LZW (or no compression), while PNG uses Deflate plus per-row filtering. A 50 MB TIFF scan typically lands at 10-20 MB in PNG.
• Logos, signatures, and UI assets with transparency — both formats carry an alpha channel, so converting a transparent-background TIFF asset to PNG keeps the cutout intact for use on dark headers or colored backgrounds.
• Microscopy, GIS, and medical scans for sharing — 16-bit grayscale TIFFs from a microscope or DICOM export survive the trip to PNG because PNG also supports 16-bit per channel; reviewers can open the result in any browser without ImageJ or QGIS.
• Multipage scans split into individual pages — multi-page TIFF (often used by fax machines, document scanners, and Photoshop) becomes one numbered PNG per page, which is exactly what most photo apps, project management tools, and review workflows expect.
• Strip TIFF-only quirks — TIFF's hundreds of optional tags (compression flavor, photometric interpretation, IFD chains) cause inconsistent rendering across viewers. PNG has a tight, well-defined chunk format that renders the same everywhere.

TIFF vs PNG — Format Comparison

Bit-Depth and Color Preservation Cheat Sheet

Frequently Asked Questions

Will my 16-bit TIFF stay 16-bit in PNG?

Yes. The PNG specification (W3C, Fourth Edition) allows 16 bits per channel for grayscale and truecolor images, with optional alpha at the same depth. A 16-bit RGBA TIFF from a scanner or microscope round-trips into a 48-bit (RGB) or 64-bit (RGBA) PNG with no quantization. Older image viewers may display the result as 8-bit but the file itself still carries the full data.

How does the converter handle multipage TIFF files?

Each page (subfile in the TIFF spec) becomes a separate PNG, numbered sequentially — scan_p1.png, scan_p2.png, etc. If you'd rather keep everything in one file for review or print, convert the TIFF to a multi-page document with TIFF to PDF, or stack individual PNGs back together using Merge Images to PDF.

My TIFF has a transparent background — will the PNG keep it?

Yes, as long as the source has a real alpha channel (most do when exported from Photoshop, Affinity, or GIMP). PNG supports the same RGBA model with full 8-bit or 16-bit alpha, so cutout logos, signatures, and assets with soft anti-aliased edges convert without a white box appearing behind them. If your TIFF only has a "matte" color marked as transparent (some legacy fax/print workflows), that won't translate — you'd need to mask the layer first in an editor.

Why is my PNG smaller than the TIFF? Did I lose quality?

No. TIFF defaults to LZW or no compression, while PNG uses Deflate with five per-row filters that exploit horizontal pixel correlation. Both are mathematically lossless — the pixels in the decoded image are byte-for-byte identical to what you'd get from the TIFF. PNG is typically 30-50% smaller for photographic content and can be 80%+ smaller for screenshots, diagrams, and flat-color UI assets.

Should I convert TIFF to PNG or to JPG?

PNG if you need lossless quality, transparency, screenshots, line art, text, or any image you might re-edit. JPG if you have a flat photographic scan, no transparency, and you care about file size more than per-pixel fidelity — JPG typically lands 5-10× smaller than PNG for photos, but every save throws away detail. For studio archival, keep the TIFF and only export PNG/JPG for distribution. See also TIFF to JPG.

Can I convert CMYK TIFFs from print workflows?

You can, but the result is RGB. PNG only supports RGB/grayscale color modes — there's no CMYK PNG. The converter applies a color-profile transform (using the embedded ICC profile if present, sRGB if not), which is fine for previews and web review but not for press-ready output. If you need a print-faithful proof, keep the file in TIFF or export to PDF.

How big can my TIFF files be?

The converter handles individual scans up to several hundred megabytes in modern browsers (the practical ceiling is upload size and connection speed since processing happens in-session). For oversized archival scans — gigapixel maps, microscopy slides, document books — split the multipage TIFF first or downsample using the Image Resolution percentage option to keep things responsive.

Will browsers ever support TIFF natively, making this conversion unnecessary?

No. WebP, AVIF, and JPEG-XL are the formats browser vendors are investing in for next-generation web imagery; TIFF has been outside that conversation for two decades because of its complexity (over 100 optional tags, multiple compression schemes, byte-order ambiguity). For any image leaving an archival workflow and entering a web, email, or chat context, you still need to convert. PNG remains the right destination when you can't afford to lose a pixel.

What if I want to go the other direction?

Use PNG to TIFF for archival or print pipelines, or Compress PNG if you only need to shrink an existing PNG. For multi-page documents, PDF to PNG extracts one PNG per page from a PDF source.