On: keep transparency in PNG where the TIFF supports it. Off: composite on white (smaller RGB files).
zlib 1–9
TIFF decode (UTIF.js) and PNG DEFLATE may run in a Web Worker when supported. Nothing is uploaded to SynthQuery. Up to 15 files, 100.00 MB each; up to 300 pages per TIFF per run.
Very large TIFFs or many pages can use significant RAM in the browser. Exotic compression or color spaces may fail in UTIF—try re-saving from a desktop viewer if decode errors appear. CMYK TIFFs are converted to RGB for PNG output in the browser.
About this tool
Tagged Image File Format remains the lingua franca of scanning, prepress, GIS exports, scientific imaging, and fax-era archives because it can store multiple pages, optional transparency, diverse compression schemes, and rich metadata in one container. Yet most browsers, social platforms, and lightweight CMS widgets still prefer Portable Network Graphics for inline display: PNG is lossless for typical RGBA workflows, supports alpha without proprietary decoders, and drops into HTML img tags without helper plugins. SynthQuery’s free TIFF to PNG Converter bridges that gap entirely in your browser. You upload TIFF or TIF files, see how many image pages each document contains, choose whether to export every page, only the cover sheet, or a precise list such as one comma three five dash twelve, toggle alpha preservation or white compositing, dial PNG zlib compression from one through nine, and download individual PNGs or a single ZIP archive. Decoding relies on UTIF.js so common packings such as LZW, PackBits, and many JPEG-in-TIFF stacks are handled without sending your bytes to our servers. A Web Worker runs the heavy decode-and-encode path when your browser allows it, which keeps the tab responsive while multi-hundred-megabyte scans churn. Whether you are a marketer unblocking creative handoffs, an archivist publishing derivatives, or an analyst sharing map tiles, this page gives you a predictable, privacy-preserving path from TIFF to web-ready PNG.
What this tool does
The interface follows the same proven layout as our PDF to PNG and HEIC to PNG utilities: conversion options on the left, a generous drop zone and queue on the right, then a thumbnail grid once outputs exist. Drag up to fifteen TIFF files onto the dashed region or activate the hidden file input—only extensions ending in .tif or .tiff (plus matching MIME hints) enter the queue so accidental JPEG picks do not waste a conversion pass. Each row shows monospace filename, byte size, and a live page tally after a quick metadata decode pass; while that probe runs you see a compact spinner instead of guessing whether a fifty-megabyte file stalled. Multi-page documents display an explicit count such as “12 pages,” which answers the first question stakeholders ask before batch exports.
Page scope is per file but driven by one global mode for simplicity: All pages walks every stacked IFD we classify as a raster image, First page only grabs the opening frame for thumbnails or quick previews, and Specific pages accepts comma-separated integers plus inclusive ranges with the same parser used on our PDF tool so muscle memory transfers across SynthQuery. If you request pages outside the available range they are ignored; if nothing valid remains we fall back to page one with an inline hint so silent empty exports do not occur. A safety cap prevents accidentally materializing hundreds of poster-sized frames in one run on a tablet—when the cap applies, the toast explains that only the leading pages exported and invites another pass.
Preserve alpha channel mirrors the transparency semantics of our other PNG exporters: enabled, semi-transparent artwork survives as true RGBA PNG; disabled, translucent edges composite onto white before encoding so legacy slide tools that mishandle premultiplied alpha still get predictable fills. PNG compression level maps directly to zlib DEFLATE effort in our truecolor writer—six remains the balanced default, nine squeezes archival batches, one minimizes CPU time on enormous canvases. UTIF.js performs the TIFF baseline and extension decodes locally; unsupported proprietary compressions surface readable errors rather than opaque failures. Mobile layouts preserve forty-four-pixel touch targets, status text is exposed to screen readers during long jobs, and downloads support per-card saves, staggered multi-download anchors, and JSZip packaging without routing archives through SynthQuery infrastructure.
Technical details
TIFF is less a single image format than a flexible IFD-linked container: each image directory can specify photometric interpretation, sample layout, compression type, colorimetry, and even private tags from specific vendors. That flexibility lets the same extension represent fax bilevel scans, CMYK separations, floating-point scientific data, and transparency-friendly RGBA—all reasons TIFF survived decades in production pipelines. PNG, by contrast, standardizes a smaller set: primarily deflate-compressed raster chunks with optional alpha, gamma hints, and textual metadata, all engineered for lossless round trips on the web. Browsers adopted PNG early and universally; TIFF never gained first-class <img> decoding across engines, which is why “TIFF preview” flows often require downloads or plugins.
UTIF.js implements enough of the TIFF ecosystem to decode many real-world files in pure JavaScript, including LZW (when not patent-encumbered in your jurisdiction historically), PackBits, and JPEG compression inside TIFF strips. It converts several photometric modes to RGBA8 for canvas-friendly processing, including CMYK to RGB approximations suitable for screen review—print professionals should still proof separations in ICC-aware desktop software. PNG output here is truecolor RGB or RGBA at eight bits per channel with zlib levels you choose; we do not emit palette PNG or interlaced PNG modes because those paths complicate predictability for transparency-heavy exports. Metadata such as EXIF or GeoTIFF tags are not automatically copied into PNG textual chunks; if you must preserve geolocation or copyright strings, plan a metadata migration in a DAM or scripting environment after download.
File size dynamics differ: TIFF may be smaller than PNG when lossy JPEG compression wraps photographic content, yet PNG often wins on flat graphics because DEFLATE loves repeated scanline patterns. Converting JPEG-compressed TIFF to PNG never restores lost frequency information—it losslessly stores whatever pixels UTIF reconstructs, which includes JPEG artifacts. For gigantic uncompressed strips, memory spikes can occur because the decoder must realize full raster buffers before PNG encoding; that is why we cap pages per run and recommend splitting enormous surveys across multiple conversions on constrained devices.
Use cases
Web producers receive multi-page TIFF scans from legal discovery or compliance archives and must publish select pages as PNG for articles where PDF embeds are blocked—this tool extracts only the needed IFDs without running desktop batch scripts on locked laptops. E-commerce teams get vendor packshots as CMYK-plus-alpha TIFFs from prepress houses; converting here produces sRGB-friendly PNG derivatives for Shopify or WooCommerce while keeping the TIFF master offline. GIS analysts export GeoTIFF mosaics for internal review but need quick PNG tiles for Slack or Notion comments; choosing first page or a tight page list avoids pushing entire spatial databases through chat uploads.
Medical and research staff sometimes hold DICOM-adjacent TIFF stacks from instruments; when institutional policy allows browser-local transforms, PNG snapshots aid teaching slides that forbid raw modality files. Photographers who inherit scanned negatives as 16-bit TIFF may down-convert to eight-bit elsewhere first, then use SynthQuery for the final PNG intended for portfolio CDNs. Educators building accessible coursework attach PNG versions of TIFF handouts because learning management systems handle PNG previews universally. Marketing agencies batch-convert creative TIFFs delivered from retouchers before dropping assets into Figma libraries that prefer lighter PNG imports. Whenever accompanying blog posts discuss AI-assisted captions for those images, consider pairing visual workflows with SynthQuery’s AI Detector and Humanizer from the main tools directory for a consistent governance story.
How SynthQuery compares
Desktop utilities remain indispensable for ICC-managed print workflows, scripted watch folders, and proprietary camera raw stages. IrfanView offers lightning-fast inspection and batch rename on Windows with a plugin ecosystem that has saved countless production desks. XnConvert delivers cross-platform queueing, filters, and format hopping when you need repeatable recipes across thousands of files. GIMP provides deep editing, masks, and color tools when TIFF is merely the starting point for compositing. SynthQuery targets a narrower scenario: explainable, install-free conversion when policy forbids uploads or when you only need a handful of derivatives on a machine you do not administer. The table below contrasts typical strengths—pick based on compliance, automation depth, and whether you need editing versus straight raster translation.
Aspect
SynthQuery
Typical alternatives
Privacy & air gap
UTIF.js and PNG encoding run locally; optional Web Worker isolation; no SynthQuery file storage for the conversion itself.
IrfanView and GIMP keep files local when you run them; many “online TIFF converters” upload to shared infrastructure—verify terms.
Batch automation
Interactive UI with ZIP export for fifteen files and hundreds of capped pages per run—great for ad hoc batches.
XnConvert and shell-driven ImageMagick recipes excel when you script nightly folders or watch directories.
Editing & color science
No pixel editing; browser-sRGB pragmatic output; CMYK TIFF becomes RGB PNG for screen use.
GIMP, Acrobat-related rasterizers, and prepress RIPs manage ICC profiles, spot colors, and layered retouching.
Desktop apps expose dozens of filters—powerful but slower for one-off conversions on locked-down laptops.
How to use this tool effectively
Begin with the highest-quality TIFF you legitimately control—prefer uncompressed or losslessly compressed masters when downstream PNG size must reflect real detail, and avoid re-saving lossy JPEG-in-TIFF repeatedly because generational noise accumulates even when the outer wrapper stays TIFF. Click the drop zone or use your operating system picker to add files; confirm each row lists the expected filename and size, then wait for the page counter to finish probing before pressing Convert so your mode selection applies to accurate depth. If a file never leaves “Reading pages,” it may be truncated, password-wrapped inside a container we cannot parse, or compressed with an exotic scheme; re-export from a desktop viewer and retry.
Choose the page mode that matches the deliverable. All pages suits scanned book spreads, microscopy z-stacks packaged as IFD sequences, or fax batches where every sheet must become its own PNG asset. First page only is ideal for insurance cards, engineering title blocks, or GIS thumbnails where the remainder is reference data you do not want to rasterize yet. Specific pages accepts lists like two dash five comma eight comma eleven; malformed tokens are skipped harmlessly. Next decide whether transparency matters: keep Preserve alpha on for logos, masks, and cartography overlays; turn it off when you need guaranteed opaque pixels for email clients that flatten poorly. Adjust the PNG compression slider—higher numbers spend more CPU searching redundancy in scanlines, which often shrinks flat-color exports dramatically.
Press Convert to PNG and read the status line as each document decodes. When thumbnails appear, verify framing and contrast quickly, then download individually, trigger staggered all downloads for browsers that throttle rapid anchors, or fetch a ZIP for handoff to collaborators. If outputs look softer than expected, remember that PNG cannot invent detail absent from the TIFF—upsampling belongs in dedicated editing tools after you confirm source resolution. For follow-on optimization, visit the PNG Compressor or Image Resizer linked below; for mixed-format pipelines, pair this export with our WebP Converter when modern codecs beat PNG on the wire.
Limitations and best practices
Not every TIFF variant decodes in UTIF: proprietary compression codes, encrypted medical wrappers, or malformed strip offsets may throw errors—re-save from a desktop reference viewer when possible. Sixteen-bit and exotic float samples may down-range or fail depending on tag combinations; for scientific fidelity keep IEEE-float TIFF in native toolchains. Password-protected or DRM-wrapped containers must be decrypted before import. Because browsers allocate contiguous memory for large rasters, monitor Task Manager if you stack multiple gigapixel attempts; splitting jobs preserves stability. Treat PNG exports as derivatives, not replacements for archival TIFF/A masters when compliance requires the original tags and compression. After export, run the PNG Compressor if byte budgets tighten, or the Image Resizer before pushing hero images into responsive srcsets.
If upstream vendors deliver PDF instead of TIFF, rasterize pages with DPI control in the same UX family.
Frequently asked questions
Yes. After each file loads we count raster image IFDs and show the total beside the filename—twelve pages means twelve convertible frames unless you restrict the mode. Choose All pages to export every detected frame, First page only for a single thumbnail, or Specific pages with comma-separated numbers and inclusive ranges (for example, 1,3,5-8). A per-run safety cap prevents browsers from exhausting memory on accidental thousand-page faxes; if you hit the cap, run again with narrower ranges.
When Preserve alpha channel is enabled, UTIF decodes supported transparency and associated alpha into RGBA buffers, and our PNG writer emits truecolor PNG with alpha whenever partial transparency exists—matching the behavior of our PDF and HEIC exporters. When the toggle is off, translucent pixels composite onto white before encoding, yielding opaque RGB PNG that behaves predictably in slide decks or email clients that mishandle alpha. TIFF features such as spot color plates or premultiplied quirks may still interact oddly with downstream apps, so spot-check thumbnails before publishing.
TIFF is a family of tag-driven layouts with optional compression, color spaces, and multi-page sequences; implementing a complete decoder inside every browser engine was never prioritized the way PNG, JPEG, and GIF were. Some Safari builds show certain baseline TIFFs, but you cannot rely on consistent <img> support across Chrome, Firefox, and Edge. Converting to PNG—or serving WebP/AVIF derivatives—gives deterministic previews, smaller attack surface for malformed tags, and compatibility with virtually every CMS media field.
The UI accepts up to 100 megabytes per file and up to fifteen files per session because TIFF archives from scanners and GIS exports can dwarf typical JPEGs. The practical limit is still your device RAM: uncompressed RGBA buffers scale with width times height times four bytes, so a single enormous strip may fail even when the file is under 100 MB. If conversion aborts with memory errors, split the TIFF in a desktop tool, reduce bit depth, or export fewer pages per run.
UTIF.js decodes many standard compressions including LZW, PackBits, and JPEG compressed tiles or strips—common outputs from Photoshop, GDAL, and scanner drivers. Proprietary vendor compressions or rare fax encodings may not be implemented; in those cases you will see an error toast suggesting re-export. Remember that “compressed TIFF” does not imply lossless: JPEG compression inside TIFF is still lossy, and converting such data to PNG preserves the decoded pixels—including any JPEG artifacts—losslessly from that point forward.
Yes. Set the page mode to Specific pages and enter a specification such as 2,4,7-10 using commas or spaces. Ranges are inclusive and deduplicated; invalid tokens are skipped. If the parser finds nothing valid, we fall back to page one and you can adjust the string. This is useful when a multi-page scan contains only a few sheets relevant to a blog post or ticket attachment.
PNG stores eight-bit RGB or RGBA channels losslessly relative to the raster UTIF reconstructs. If your TIFF holds sixteen-bit medical or photographic samples, UTIF’s RGBA8 path quantizes to eight bits per channel, which is imperceptible for many web cases but not equivalent to a full high-bit archive. Likewise, JPEG-compressed TIFF never regains frequencies lost before decode. For web graphics and typical office scans, quality is effectively preserved; for regulated archives, keep the original TIFF and treat PNG as a display derivative.
Many CMYK TIFFs decode through UTIF’s photometric handling and convert to RGB pixels before PNG encoding, which matches how browsers always display images (sRGB-oriented). This is suitable for screen previews, quick approvals, and CMS thumbnails. It is not a substitute for ICC-profiled print proofing: separations, spot inks, and paper simulation still require desktop prepress software. If colors look flat after conversion, adjust the master TIFF in a color-managed editor before exporting PNG for critical brand work.