Initializing... drag & drop files here
Supports: TIFF, TIF
.tif or .tiff files. Batch upload is supported, and multi-page TIFs are accepted — each page becomes its own PNG in the output.TIF (the same format as .tiff — see the comparison table below) is the workhorse of scanning, archival imaging, and pre-press print. It stores every pixel losslessly with optional LZW, Deflate, PackBits, JPEG, or CCITT Group 4 compression, supports 1-bit through 32-bit channels, and packs multiple pages into one file. The catch: no web browser renders TIF, most chat apps reject it, and the files are often 5-10× larger than the equivalent PNG. Converting to PNG gives you the same lossless pixels in a container the entire web can display.
.tif uploads or strip them silently. PNG is in every CMS's allowlist and renders in every browser shipped since 1996 (PNG 1.0 reached W3C Recommendation status in October 1996)..tif with quirky compression (CCITT Group 4, old-style JPEG-in-TIFF). Re-encoding to PNG sanitises them into something modern viewers actually decode..tif and .tiff are not two different formats. Both are filename aliases for the same Tagged Image File Format created by Aldus engineer Steve Carlsen in 1986 and now maintained by Adobe (TIFF 6.0, June 1992, after Adobe's 1994 acquisition of Aldus). The three-letter .tif extension exists because MS-DOS and early Windows enforced 8.3 filename rules; the four-letter .tiff matches the acronym. Internal byte structure, tags, compression options, and multi-page subfile handling are identical between the two extensions.
| Property | .tif | .tiff | PNG |
|---|---|---|---|
| Underlying format | Tagged Image File Format | Tagged Image File Format (same) | Portable Network Graphics |
| Created / standardised | Aldus, 1986 (TIFF 6.0, 1992) | Same | W3C Recommendation, Oct 1996 |
| Compression | Uncompressed, LZW, Deflate, PackBits, JPEG, CCITT G4 | Same | Deflate (lossless) |
| Bit depth | 1, 8, 16, 32 per channel | Same | 1, 2, 4, 8, 16 per channel |
| Transparency / alpha | Yes (via ExtraSamples tag) | Yes | Yes (native) |
| Multi-page in one file | Yes (IFDs / subfiles) | Yes | No — one image per file |
| Typical file size (24-bit photo) | 10-30 MB uncompressed; 3-8 MB LZW | Same | 1-5 MB (Deflate) |
| Browser support | None natively | None natively | All browsers (universal) |
| Best for | Print, scanning, archival, GIS, microscopy | Same | Web, apps, screenshots, transparent UI assets |
Multi-page TIFs are common from scanners, fax archives, and document imaging tools. Because PNG is single-image only, every page in the source TIF lands as its own PNG.
| Source TIF | Resulting PNGs |
|---|---|
scan.tif with 1 page |
scan.png |
report.tif with 5 pages |
report_page1.png … report_page5.png |
| Batch upload: 3 single-page TIFs | 3 PNGs, ZIP-bundled |
| Batch upload: 2 multi-page TIFs (4 pages each) | 8 PNGs, ZIP-bundled |
If you actually want a single multi-page output for sharing or archiving, use Merge TIF to PDF instead — PDF keeps the pagination in one file.
| Setting | What it controls | Recommended |
|---|---|---|
| Quality Preset | Re-encode fidelity before PNG packaging | Very High (default) for archival; Medium for inline web previews |
| Compression level (0-9) | PNG Deflate effort — higher = smaller file, slower encode | 6 (default) balances size and time; bump to 9 for static assets you ship once |
| Compression speed | Encoder CPU effort tier | 4 (default); lower for max compression on small batches |
| Colors (palette) | Reduces 24-bit RGB to 2-256 indexed colors | Use 16-256 + dither for scanned text / line art; leave ORIGINAL for photos |
| Resolution Percentage | Scales width and height by % | 50% halves both dimensions (quarters the pixel count) |
| Preset Resolutions | 4K, 1080p, 720p, 480p, etc. | Pick the smallest preset that still looks crisp on the target device |
.tif different from .tiff?No. They are the same Tagged Image File Format with different extension lengths. .tif exists because MS-DOS and early Windows required three-character extensions; .tiff matches the four-letter acronym. Every modern decoder (Photoshop, Preview, GIMP, ImageMagick, libtiff-based tools) opens both with identical results. This converter accepts either.
No, with one caveat. Both formats are lossless containers, so the pixel data is preserved byte-for-byte at the same bit depth. The exception is if your source TIF stores 32-bit-per-channel float data (rare, mostly HDR microscopy and scientific imaging) — PNG tops out at 16-bit per channel, so float values get tone-mapped down. For standard 8-bit and 16-bit photos, scans, and graphics, the output is mathematically identical.
.tif files my browser can't open. What does this tool do that fixes that?It re-encodes the pixel data into PNG, which every browser shipped since the late 1990s renders inline. Legacy scanner output often uses CCITT Group 4 (1-bit black-and-white) or old-style JPEG-in-TIFF compression. PNG normalises everything to Deflate-compressed RGBA, which Chrome, Firefox, Edge, and Safari all decode without any extension or plugin.
Each Image File Directory (IFD) inside the TIF — the format's name for a page or subfile — becomes one PNG. A 12-page faxed contract scan, for example, produces 12 PNGs named with a _page1, _page2, etc. suffix, bundled into a single ZIP at the end. If you want a single paginated file instead, use Merge TIF to PDF.
Yes. TIFs with an alpha channel (stored via the ExtraSamples tag) convert to PNGs with full RGBA alpha. The transparent regions stay transparent, and partial transparency (anti-aliased edges, drop shadows on a transparent background) is preserved at full 8-bit alpha precision.
Most TIFs are uncompressed or use LZW, which is decent for line art but mediocre for photos. PNG uses Deflate (the same algorithm as ZIP), which usually compresses photos and screenshots 30-70% smaller than uncompressed TIF. You're not losing anything — you're just storing the same pixels in a tighter container.
Yes — if you leave Colors set to ORIGINAL and don't enable palette reduction, 16-bit-per-channel TIFs convert to 16-bit-per-channel PNGs. This matters for medical, astronomical, and scientific imaging where the extra precision drives downstream analysis. If your source is 8-bit, output stays 8-bit; the converter doesn't synthesise extra precision.
This page outputs PNG, but TIF feeds many formats: TIF to JPG is best for smaller, web-friendly photos where you don't need alpha; TIF to PDF packages a multi-page scan into one shareable document; TIF to WebP gives 25-35% smaller files than PNG for modern browsers. Going the other way, PNG to TIF re-packages a PNG into the archival TIF container.
There's no hard daily or count limit. Files process locally in your browser session, so the practical ceiling is your device's available RAM — a single large multi-page scan over a few hundred megabytes can be slow on mobile, but desktop browsers handle multi-gigabyte TIFs without trouble. If a huge file fails, Compress TIF first, then convert.