1Upload the videos 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 Video file, or the whole set together as one archive.
Resize Video FAQ
Does the source format affect the result of a resize?
+
It does. this format is read and written by the same streaming pipeline as everything else we support. 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 Video I should watch for?
+
Yes — the container and codec are probed before anything runs, so mixed uploads in one batch are handled per file. Worth checking before you resize a file you will not be able to regenerate.
How does Resize Video change the dimensions?
+
Concretely, each clip is probed for its real resolution first, then scaled and re-encoded, so a batch of mixed sources lands on one target size rather than one scale factor. 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.
What happens to audio, subtitle and chapter tracks?
+
They are carried across wherever the target container can hold them, including multiple audio languages, embedded subtitles and chapter markers, rather than silently keeping only the first track of each.
Which video formats does Resize Video accept?
+
MP4, MOV, MKV, WebM, AVI, WMV, FLV, 3GP, M4V, MPEG and MPG. Each file is probed for its real container and codec before anything runs, so a mixed batch is handled correctly file by file.
Is there a file size limit on Resize Video?
+
Yes: free accounts process video up to 1 GiB per file whichever container you brought; ffmpeg with x264, x265 and libvpx does the encoding. It is high enough that upload speed is usually the binding constraint rather than the cap itself.
Will Resize Video lower the quality of my videos?
+
Only if the operation requires re-drawing frames. Container-level and timeline-level work is done as a stream copy, which is bit-identical to the source and finishes in seconds. Anything that must re-encode does so at a quality level you choose.
Why would a modern-format site run Resize Video?
+
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 Video is on the same upload and the same account so those questions get answered in one place.
Once Resize Video 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.
