Skip to main content

WebP to TIFF converter

Convert WEBP images to TIFF format

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

WebP exists to make images small for delivery; TIFF exists to make them predictable for production. Moving between them is usually a handover - an asset that lives on a website now has to go to a printer, a journal or a layout application that will not look at a .webp. The file written here is baseline TIFF at its plainest: little-endian, RGB, eight bits per channel, a single uncompressed strip. It is enormous by comparison with the source, and it carries no transparency, which is the detail worth checking before you send it on.

Key facts about WebP to TIFF converter

Key facts about WebP to TIFF converter
File writtenBaseline TIFF, byte order II, magic number 42, ten directory tags, PhotometricInterpretation 2 and a single strip.
CompressionNone - the tag is set to 1. There is no LZW, Deflate, PackBits or JPEG-in-TIFF option here.
AlphaNot represented. Three samples per pixel are written with no ExtraSamples tag, so transparent WebP areas are stored as black.
Size134 bytes of structure plus three bytes per pixel. A 2400x1600 image is always 11,520,134 bytes, whatever the WebP weighed.
Bit depthEight bits per channel in sRGB - the canvas cannot supply the 16-bit data a retouching workflow might expect from a TIFF.
AnimationOnly the first frame of an animated WebP is written; TIFF here is single-page and single-image.
Resolution tagsXResolution and YResolution are not included, so layout software applies its own default dpi rather than a value from the file.
Colour managementNo ICC profile is embedded and no CMYK conversion happens - a press vendor expecting separations will need a further step.
Opens natively inPhotoshop, InDesign, macOS Preview, Windows Photos, GIMP and scanning or prepress software. Chrome and Firefox will not render it.

What happens to your file

The decode uses your browser's WebP support and the encode is written by this page: alpha bytes are removed as the canvas pixels are packed into RGB triples, and a DataView lays down the file header and the ten tags in front of that block before it becomes a downloadable Blob. Neither half involves a server, so an unreleased image being prepared for print never leaves the machine it is sitting on.

About this tool

  1. 1

    Flatten transparency first

    If the WebP has an alpha channel, composite it over the intended background in an editor - the TIFF cannot store it and will render it black.

  2. 2

    Add the files

    Up to twenty .webp files per run; each produces its own single-page .tif.

  3. 3

    Keep the original dimensions

    Print requirements are usually specified in pixels or dpi, so only resize when you know the target size.

  4. 4

    Convert and verify

    Open the result in Preview or Photoshop before handing it over, and expect a file in the tens of megabytes.

Specs & compatibility
Input and outputTakes .webp only (image/webp) and returns .tiff with the image/tiff type; any other extension is refused before decoding.
Conversion pathWEBP to TIFF runs in three steps: an <img> element decodes the WebP and passes frame one to the canvas; 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 WebP side needs Chrome 32, Firefox 65, Edge 18 or Safari 14 to decode, 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 WEBP.
Batch, caps and namingTwenty WEBP 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 WEBP fails before any TIFF bytes exist.
  • A TIFF made from a compressed web asset is not a high-quality master - if the original photograph or design file exists, export the TIFF from that.
  • When the recipient asked specifically for LZW-compressed TIFF, this file will not satisfy them; it is uncompressed by design.
  • Zipping a batch before transfer helps a lot, because uncompressed RGB data is highly redundant and compresses well in transit.
  • Print vendors often want CMYK and an embedded profile; plan a colour-managed step in proper editing software after this conversion.
  • Handing a web asset to a print shop, publisher or editorial team that accepts TIFF only.
  • Placing an image into a layout application that prefers TIFF for linked graphics.
  • Feeding an imaging or measurement system that reads baseline TIFF but has no WebP decoder.
Because WebP compresses aggressively and this TIFF does not compress at all. Three raw bytes per pixel with no encoding means the size follows from the dimensions alone. A 300 KB WebP at 2400 by 1600 pixels becomes an 11.5 MB TIFF, and a plain white image of the same size would occupy exactly as much.
No. The TIFF records exactly the pixels the WebP decoder produced, including any softening or artifacts the lossy encoding introduced. Uncompressed storage guarantees nothing further will be lost, but no format conversion can restore detail that was discarded earlier.
The alpha channel is dropped and those areas appear black, because the encoder writes three colour samples per pixel and canvas pixels that are fully transparent hold zero in each. Composite the image onto the background you want before converting if the transparency is meaningful.
Not from this page. Each file converts independently into a single-page TIFF, and a batch simply returns several files in a ZIP. A multi-page TIFF requires an encoder that links several image file directories together, which is beyond what this one writes.
Yes - uncompressed baseline RGB is the most conservative TIFF variant in existence and every major application reads it, including Preview, GIMP and Windows Photos. Browsers are the exception, since Chrome and Firefox never added TIFF rendering, so the file downloads rather than displaying in a tab.

Related tools

View all

Need the opposite? Try TIFF to WEBP

Updated

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