Image Cropper Details
Image Cropper takes a rectangle out of an image at the size you name. You give the crop width and height, and optional left and top offsets move the region around.
Use it to drop dead space from a cover image, cut a square thumbnail from a product photo, or keep only the relevant panel of a screenshot.
The workflow
Opening the tool for the first time, this is the flow:
- Add the image you want cropped to the upload area.
- Enter the crop width and crop height; both fields are required.
- Set the left and top offsets if the region should start at a specific point.
- Leave the offsets empty and the crop is taken from the centre of the image.
- Download the result, which keeps the format of the source file.
Technical details
The limits that apply to the crop region:
- Crop width and crop height accept 1 to 4000 pixels.
- Left and top offsets accept 0 to 4000; leaving them empty centres the crop.
- Ask for a region larger than the image and it is clamped to the image instead of failing.
- Offsets that would run past the edge are pulled back so the region stays inside the frame.
- Formats that carry transparency keep their transparent background.
- Each file can reach 24 MB.
Is this the right tool
Crop when the framing is what has to change: it discards part of the image for good and lets you decide the ratio of what remains.
Keep everything but make it smaller with the Image Resizer, and fix a size problem alone with the Image Compressor. If you need both a crop and a new size, run the two tools in sequence; either order gives the same result.
Quick tips
- For square thumbnails, put the same number in width and height.
- Protecting faces or a logo? Nudge the offsets across a couple of runs, since nothing overwrites your source.
- Applying the same crop to many files is fastest with the values set once and the queue run in a batch.
- Knowing the real pixel size of the image beforehand beats guessing at offsets.
Data and privacy
Your file travels over HTTPS, is processed during that single request and comes back as the download itself. It is never written to a public directory, nothing is kept once the response is sent, and the download is marked as non-cacheable.