1Upload your images and wait for the preview to appear.
2Drag out the region you want to keep, or lock the selection to 1:1, 4:3 or 16:9 and drag freely inside that ratio.
3Confirm the crop — the same rectangle is applied to every file you uploaded, which is how a set ends up genuinely consistent.
4Download the cropped Image file, with everything outside the frame discarded.
Crop Image FAQ
Can I crop several files to the same region at once?
+
Yes, and that is the case worth doing here rather than in an editor: the same rectangle is applied across the batch, which is how a set of product shots ends up genuinely consistent instead of approximately consistent.
Can I crop to a fixed aspect ratio?
+
Yes. Lock the selection to 1:1, 4:3, 16:9 or any custom ratio and drag freely inside that constraint — which is how you get a set of images that all fit the same layout slot without measuring anything.
Does my source format change how a crop behaves?
+
It can. this format is read and written by the same streaming pipeline as everything else we support. That decides whether the crop is a pure pixel operation or whether the file has to be rebuilt around it.
Anything specific to Image worth knowing before I crop?
+
Yes — the pipeline reads the real format from the file header rather than the extension, so a mislabelled upload still works. That is the sort of detail that only shows up after you have overwritten the original.
Will Crop 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 Crop 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 Crop Image cost anything?
+
No. Crop 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 Crop 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 Crop 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 Crop 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 Crop 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.
