1Upload your WebP 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 WebP file, with everything outside the frame discarded.
Crop WebP FAQ
Anything specific to WebP worth knowing before I crop?
+
Yes — 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. That is the sort of detail that only shows up after you have overwritten the original.
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.
How does Crop WebP select and cut the area?
+
Concretely, the crop is applied to the decoded image and the result is re-encoded, so it costs one generation; where the crop happens to land on 8-pixel MCU boundaries the encoder can keep the original blocks and the cost disappears. You drag the region you want directly on the preview, or type exact pixel coordinates if you already know them.
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 Crop WebP cost anything?
+
No. Crop WebP is free with no account, no watermark on the output and no signup wall in front of the download. Uploads are deleted automatically a short time after the job finishes.
What can I upload to Crop WebP?
+
Anything in the lossy raster family — JPG, JPEG, JFIF and WebP — plus the lossless formats (PNG, BMP, TIFF) if you want to mix them in one batch. The format is read from the file header, not the extension, so a photo saved with the wrong suffix still goes through.
Is there a file size limit on Crop WebP?
+
Yes: free accounts process images up to 25 MB each, which covers essentially every camera JPG and phone photo; the work is done by libjpeg-turbo and libwebp, the same libraries a desktop editor links against. Larger files are the one thing the free tier will stop you on, and the limit is per file rather than per batch.
What happens to EXIF and colour profile data?
+
Camera EXIF (ISO, shutter, lens, GPS) and the embedded ICC profile are carried across by default, because dropping the profile is what makes colours shift on re-import. Use the privacy option to strip metadata before download if you are about to publish the file.
Why does a MP3 site host Crop WebP?
+
MP3.to is built around the format that made portable audio ordinary: universally playable, small enough to ignore, and lossy in a way that only matters if you keep re-encoding it. Audio jobs cluster: the same person who needs a format changed usually needs the file cut, levelled or made smaller in the same sitting. Putting Crop WebP behind the same upload, the same caps and the same account is what turns three tabs into one.
What should I do with the result once Crop WebP is finished?
+
The converter on this site moves audio between MP3, WAV, FLAC, M4A, OGG and Opus, so the output format is a decision you can leave until the end rather than commit to at the start. Doing that after Crop WebP rather than before means the encode happens once, on the file you actually settled on, instead of twice.
Is Crop WebP here the same tool the sibling sites run?
+
The engines are shared — the same ffmpeg build, the same workers, the same limits. What a MP3 site adds is a point of view about bitrates, about what survives an encode and about when a lossless intermediate is worth the upload time. It also starts from one fact about the format this site is named after: MP3 frames are fixed-size blocks, so a cut lands on a frame boundary and gapless playback markers do not survive a re-encode.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploads are deleted from the workers shortly after the job finishes, nothing is listened to and nothing is indexed. Free accounts exist for history and batch size, not for access.
