Skip to main content

TIFF to WebP converter

Convert TIFF images to WEBP format

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

WebP is the target to pick when a scan is heading for a web page rather than an archive. The page reads the TIFF with its own baseline parser, rebuilds the pixels in a canvas, and asks your browser to encode them as WebP at the quality you choose. Unlike the JPEG route, alpha survives, so a four-channel TIFF keeps its cut-out edges instead of being flattened onto white. Unlike the PNG route, the encoder is lossy, which is what makes a photographic scan land in the low hundreds of kilobytes.

Key facts about TIFF to WebP converter

Key facts about TIFF to WebP converter
Encoder usedcanvas.toBlob with image/webp, so your browser own WebP encoder does the work. No codec is downloaded.
Lossy onlyThis path always produces lossy WebP. There is no lossless WebP mode exposed by the canvas API.
Quality range30 to 100 in steps of 5, default 90. The slider value is passed straight through to the encoder.
TransparencyAlpha is kept when the TIFF stores four samples per pixel, and WebP encodes it without a separate mask.
Typical size deltaA 5.93 MB uncompressed 1920x1080 scan lands near 250 to 500 KB at quality 90, below a JPEG of equal quality.
Source requirementUncompressed TIFF only. An LZW or Deflate scan is rejected up front rather than half-decoded.
Encoder availabilityChrome, Edge and Firefox encode WebP from canvas. A browser without an encoder returns PNG bytes under the .webp name.
MetadataThe re-encode carries no EXIF, XMP or ICC data across, so the WebP is untagged and treated as sRGB.
PagesThe parser reads the first image directory only, so page one is what gets encoded.
Dimension ceilingWebP tops out at 16,383 pixels per side, which is close to the canvas limit desktop browsers impose anyway.
Opens natively inAll current browsers, Windows 10 1809 and later, macOS Big Sur and later, Android, GIMP and Affinity.

What happens to your file

Everything runs inside the page. The TIFF is read as an ArrayBuffer, decoded by the parser bundled with this tool, and drawn into a canvas that belongs to this tab. Encoding happens through canvas.toBlob, which is implemented by the browser itself, so at no point is a copy of your scan sent to a server or held in a queue. The download is a Blob URL created locally, and the browser revokes it when the tool is reset or the tab is closed.

About this tool

  1. 1

    Pick the scan

    Drop one or more .tif or .tiff files on the panel, or open the file browser by clicking it.

  2. 2

    Choose a quality

    Slide between 30 and 100. Values around 80 already look clean because WebP handles gradients better than JPEG.

  3. 3

    Optionally downscale

    Use the size presets to cap the longest edge if the scan is far larger than the layout it is destined for.

  4. 4

    Run the conversion

    Press Convert and watch the progress bar; the result panel shows the old and new sizes side by side.

  5. 5

    Download

    Save the .webp, or pull a multi-file run down as one ZIP assembled in the browser.

Specs & compatibility
Input and outputTakes .tiff and .tif only (image/tiff) and returns .webp with the image/webp type; any other extension is refused before decoding.
Conversion pathTIFF to WEBP 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/webp 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 WebP works in Chromium browsers and Firefox, and where the type is unsupported the canvas specification makes the browser return PNG bytes under the .webp name.
Controls for this pairA 30 to 100 quality slider (steps of five, default 90) drives the WEBP encode, max-dimension presets from 3840 down to 200 px resize the TIFF first, and the strip-metadata toggle is moot on this pair.
Batch, caps and namingTwenty TIFF files per run at 500 MB each; one result downloads as a single WEBP, several as converted-webp-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 WEBP bytes exist.
  • WebP keeps subtle gradients cleaner than JPEG at the same nominal quality, so a setting of 75 to 80 often replaces a JPEG at 90 with no visible difference.
  • Serve WebP behind a picture element with a JPEG fallback if any of your visitors are on very old browsers or on email clients that render HTML but not WebP.
  • Alpha only arrives if the TIFF genuinely has four samples per pixel. Check in your editor before assuming the cut-out will survive.
  • Because no ICC profile crosses over, convert wide-gamut scans to sRGB before running them through here, otherwise colours will look flat in the browser.
  • If the download is unexpectedly large and opens as a PNG, your browser has no WebP encoder and silently substituted one. Try the conversion in Chrome, Edge or Firefox.
  • Publish archive or museum scans on a website where page weight matters and the originals are far too heavy to serve.
  • Feed a static site generator or image pipeline a modern format when the photographer delivered uncompressed TIFF.
  • Attach a visual reference to an issue tracker or wiki that previews WebP but refuses to render TIFF at all.
For most photographic scans, yes, by roughly a quarter to a third at matching visual quality. The gain comes from WebP predicting blocks from their neighbours, which suits the smooth tonal areas typical of flatbed scans. The margin narrows on very noisy or heavily textured images, where both encoders spend their bits on the same detail.
It does, provided the source really carries an alpha channel, which means four samples per pixel in the TIFF header. In that case the parser copies the fourth sample into the canvas alpha byte and the WebP encoder stores it natively. Three-channel scans, which is the common case, produce a fully opaque image.
Not through this tool. The canvas toBlob API exposes a single quality number and always drives the lossy encoder, so even at 100 the output is lossy WebP rather than the lossless variant. When you need a bit-exact copy of the scan for a web page, use the PNG target instead and accept the larger file.
The bundled reader handles the uncompressed baseline layout only and checks the Compression tag before touching any pixels. Scanner and editor software very often defaults to LZW, which trips this check. Re-export the file with compression turned off, which changes no pixel values, and the conversion runs normally.
Every actively maintained browser, Windows File Explorer and Photos since Windows 10 version 1809, macOS Preview since Big Sur, Android, plus GIMP, Affinity Photo and recent Photoshop releases. The remaining gaps are older desktop software and some email clients, which is why a fallback is still worth shipping on public pages.
Up to a point. The decoded image has to fit in a canvas, and desktop browsers cap that around 16,384 pixels per side with an overall area limit as well; mobile Safari gives up considerably sooner. WebP itself stops at 16,383 pixels per side. Use a size preset to bring an oversized scan into range before converting.

Related tools

View all

Need the opposite? Try WEBP to TIFF

Updated

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