1Upload the TIFF images you want resized — work from the largest original you have rather than from a copy you already shrank once.
2Type a target width, a target height or a percentage, and leave the aspect-ratio lock on unless you deliberately want stretching.
3Run the resize; every file in the batch is taken to the same target in a single pass.
4Download the resized TIFF file, or the whole set together as one archive.
Resize TIFF FAQ
Does the source format affect the result of a resize?
+
It does. TIFF is the archival container: lossless LZW or DEFLATE, 16-bit-per-channel depth, CMYK, and multiple pages in a single file. That is what decides whether shrinking the file is purely a question of pixels or also a question of re-encoding.
Is there anything specific to TIFF I should watch for?
+
Yes — a single TIFF can hold several pages and 16-bit-per-channel data, so a tool has to decide whether to act on page one or on all of them. Worth checking before you resize a file you will not be able to regenerate.
How does Resize TIFF change the dimensions?
+
Concretely, the pixels are resampled with a Lanczos filter and written back losslessly, so the only thing you lose is the detail that genuinely cannot fit in fewer pixels; nothing is added by the encoder on top. You give it a target width, a target height or a percentage, and it works from the original rather than from a previously resized copy.
Can I keep the aspect ratio, or force exact dimensions?
+
Both. Lock the ratio and one dimension is derived from the other, which is what you want almost always. Unlock it and you get exactly the numbers you typed, at the cost of stretching — useful for a fixed slot, wrong for a photograph.
Does the alpha channel survive?
+
Yes. PNG and TIFF carry a full 8-bit alpha channel and it is preserved end to end. It is only flattened if you deliberately target a format that has no alpha, in which case transparent pixels are composited onto white.
What can I upload to Resize TIFF?
+
PNG, BMP and TIFF are the lossless raster formats this handles directly, and lossy sources (JPG, WebP, GIF) work too if you want them in the same batch. Multi-page TIFFs are detected and handled page by page.
Is there a file size limit on Resize TIFF?
+
Yes: free accounts process images up to 25 MB each; lossless sources hit that ceiling sooner than photographs do, because nothing has been thrown away yet. If you are over it, converting to PNG first is often enough on its own — a BMP is routinely ten to twenty times the size of the identical image as PNG.
Will Resize TIFF lower the quality of my TIFF images?
+
No. A lossless source round-trips bit-exactly, so unless you explicitly ask for a lossy output format the pixels that come back are the pixels that went in. That is the whole reason to keep working in this family while you are still editing.
Why would a modern-format site run Resize TIFF?
+
WEBP.to is built around the modern replacement for both of the old defaults: one format that does lossy, lossless, alpha and animation, and reliably lands smaller than the JPEG or PNG it came from. People arrive here having decided the old defaults are costing them bandwidth, and that decision immediately raises the rest: what size, what quality, what happens to the transparency. Resize TIFF is on the same upload and the same account so those questions get answered in one place.
Once Resize TIFF has run, what is worth doing next?
+
The converter on this site moves images to and from WebP, PNG, JPG and AVIF, which is where you decide whether a smaller file is worth losing the older browsers. Doing it in that order matters: pick the pixels first and the container afterwards, because the container is the cheap decision and the pixels are the expensive one.
Do the sibling sites run something different?
+
The engines are identical — same libraries, same workers, same caps. What is different is the opinion attached, and the opinion here rests on a property of the format this site is named after: the same .webp extension can hold a lossy VP8 frame, a lossless one, or an animation, so the sensible processing path is decided per file rather than per extension.
What happens to my file, and is an account required?
+
No account, and nothing is retained: uploads are deleted from the workers shortly after the job finishes, and nothing is inspected, listed or indexed. Accounts exist for history and batch size only.
