1Upload the AVI 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 AVI file, or the whole set together as one archive.
Resize AVI FAQ
What dimensions should I actually target?
+
Match the slot it will live in. A full-width web hero rarely needs more than 1920 pixels wide, a content image 1200, a thumbnail 400, and doubling those numbers covers high-DPI screens. Anything beyond that is bytes nobody sees.
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 source format affect the result of a resize?
+
It does. AVI is the 1992 Microsoft container: broad codec support but no modern streaming features, no B-frame-friendly indexing and poor subtitle handling. 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 AVI I should watch for?
+
Yes — AVI has no modern index or B-frame-friendly structure, so accurate seeking usually requires a real re-encode rather than a copy. Worth checking before you resize a file you will not be able to regenerate.
Will Resize AVI lower the quality of my AVI videos?
+
It depends on whether the job needs a re-encode. Operations that only touch the container or the timeline are done as a stream copy and the picture is bit-identical to the source. Anything that has to redraw frames goes through x264/x265 at a quality level you set, where CRF 23 is visually transparent on most footage.
Can I run Resize AVI on several AVI videos at once?
+
Yes. Uploads queue in parallel, which matters more here than anywhere else because video jobs are minutes rather than seconds. Free accounts run one file at a time; a pass lifts that.
What happens to audio, subtitle and chapter tracks?
+
They are carried across. Multi-track audio, embedded subtitle tracks and chapter markers survive wherever the target container can represent them — that is the main thing that separates a proper job from a naive re-encode that silently keeps only track one.
Does Resize AVI cost anything?
+
No. Resize AVI is free without an account, and the output carries no watermark, no corner logo and no intro card. Uploaded video is deleted from the workers shortly after the job completes.
Why does a WebM site host Resize AVI?
+
WEBM.to is built around the container the open web actually chose — VP9 or AV1 with Opus audio, decoded natively by every modern browser and needing no plugin, licence or player. Video is the case where extra round trips hurt most — the files are large and every upload costs real minutes. Running Resize AVI on the same pipeline as the conversions means one upload covers the whole job instead of one upload per tool.
What should I do with the result once Resize AVI is finished?
+
The converter on this site moves video between WebM, MP4, MKV, MOV and the rest, or pulls the soundtrack out entirely, without another upload. Sequencing it that way matters more for video than anywhere else: each re-encode is another generation, so the fewer of them stand between the source and the file you publish, the better it looks.
Is Resize AVI here the same tool the sibling sites run?
+
The engines are shared — the same ffmpeg build with x264, x265 and libvpx, the same workers, the same limits. What a WebM site adds is a view on containers and codecs: which combinations play everywhere, which need a re-encode and which can simply be copied across. It also starts from one fact about the format this site is named after: WebM is VP9 or AV1 with Opus audio, which browsers decode natively but which most desktop editors still transcode on import.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploaded video is deleted from the workers shortly after the job finishes, nothing is watched and nothing is indexed. Free accounts exist for history and batch size, not for access.
