1Upload the 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 Image file, or the whole set together as one archive.
Resize Image 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. 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 Image I should watch for?
+
Yes — the pipeline reads the real format from the file header rather than the extension, so a mislabelled upload still works. Worth checking before you resize a file you will not be able to regenerate.
Will Resize Image lower the quality of my images?
+
That depends on what you brought. A lossless source (PNG, BMP, TIFF) round-trips exactly; a lossy one (JPG, WebP, GIF) is already the product of one quantisation pass and only re-encodes if the operation genuinely requires it.
Can I run Resize Image on several images at once?
+
Yes, and mixing formats in the batch is fine — settings are applied per file with the right decoder for each. Free accounts run one file at a time; a pass removes that.
What happens to metadata and transparency?
+
EXIF and the ICC colour profile are carried across wherever the target format supports them, and an alpha channel survives into any format that has one. Transparency is only flattened when the destination format has no way to represent it.
Does Resize Image cost anything?
+
No. Resize Image is free without an account and adds no watermark. Uploads are deleted from the workers shortly after the job completes.
Why does a WebM site host Resize Image?
+
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 Image 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 Image 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 Image 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.
