Convert WebP to TIFF

No. The compression artefacts already baked into the WebP are ordinary pixel data now, and TIFF preserves them perfectly rather than removing them. The file usually gets larger, sometimes several times larger. It is still worth doing before editing, because further edits will not stack a second generation of loss on top. TIFF handles CMYK, 16-bit depth, embedded ICC profiles and multi-page documents, which is exactly what print and archival workflows require. WebP is still second-class outside the browser — print workflows, older Office builds and some phone galleries do not accept it.

By default yes, wherever the target has somewhere to put it — camera model, exposure settings, lens and GPS coordinates all carry across. GPS is the field worth thinking about: if the image is going to be published, use the strip-metadata option so you are not broadcasting where the photo was taken. WebP is Google’s 2010 image format, built from the VP8 keyframe encoder and intended to replace JPG, PNG and GIF at once.

Only the first frame survives, because TIFF is a still format with nowhere to store the rest. If the animation matters, target a format that animates, or convert to a video container instead and keep the motion. TIFF’s flexibility is its weakness — two TIFFs can be structured so differently that software reading one fails on the other — and files are large.

Transparency survives when TIFF is PNG, WebP, TIFF, GIF, or SVG. Converting to JPG flattens the alpha channel against a white background — if you need transparency, pick a transparency-aware target instead of TIFF. TIFF is the Tagged Image File Format from 1986, and it is the format scanning, publishing and archiving industries standardised on.

Embedded ICC colour profiles are read from the source WebP and re-attached to the TIFF output where the format supports it (JPG, PNG, TIFF, WebP). Formats without profile support fall back to sRGB with a soft-proof step.

Camera EXIF (ISO, shutter, lens, GPS) is preserved by default during WebP -> TIFF when both formats support metadata. Use the privacy toggle to strip metadata before download if you want to share images without geolocation or device-fingerprint exposure.

Yes — drag multiple WebP files into the upload zone and they queue in parallel. Free tier accepts 100 MB per file; Premium has no per-file cap and runs more parallel workers, so a 200-image batch typically finishes in under two minutes.

For straightforward format conversion we run the same libpng / libjpeg-turbo / libwebp / ImageMagick pipelines a desktop editor uses, at the same quality. The difference is that desktop tools open one file at a time; we accept a batch and run them in parallel on server-side workers.

Default behaviour is 1:1 — your TIFF output has the same pixel dimensions as the source WebP. If you need to resize as part of the conversion, use /resize-image/ after, or chain the operations with the /image-pipeline/ utility.

For JPG / WebP, quality 75-85 typically yields a TIFF 60-80% smaller than the WebP with no visible difference at normal viewing distance. For lossless TIFF (PNG, TIFF), expect smaller savings — usually 5-30% via better deflate / LZW compression than the source already had.

Yes — uploaded WebP files are processed in isolated workers and deleted within minutes. We never read, store, or share the pixel data. The full retention window is documented at /privacy/.