Upload limits usually care about both dimensions and bytes. Use Image Resizer to set the pixel dimensions, then Image Compressor to reduce file size and compare the result before downloading.
1. Resize to the required dimensions
Choose an image in Image Resizer. Enter one dimension to preserve the original proportions, or enter both dimensions and select a fit mode:
- Contain keeps the whole image inside the box.
- Cover fills the box and crops overflow.
- Fill stretches to both dimensions.
- Inside limits the image to the requested maximum dimensions.
- Outside preserves the aspect ratio and aims to make both dimensions at least the requested values. This endpoint also has
withoutEnlargementenabled, so a smaller source is not upscaled and may remain below the requested minimum.
For example, a 2400 × 1600 source resized to 1200 × 1200 with Cover produces a square crop. Start with a sufficiently large source because this tool does not enlarge small images. The server upload guard allows image files up to 20 MB; the output keeps its format for supported inputs. Check the final file before relying on its extension.
2. Compress and compare
Open Image Compressor with the resized file. Choose a quality value, process it, and compare the original and compressed previews. There is no guaranteed percentage reduction: the result depends on the source format, dimensions, image detail, and selected quality. If the output is larger, the tool reports that condition so you can lower quality or keep the original.
3. Verify before uploading
Check the downloaded file's pixel dimensions and byte size in your operating system or upload form. Confirm that:
- The width and height match the receiving service's requirement.
- The file is below its byte limit.
- Text, faces, and fine edges remain readable at the displayed size.
- The format is accepted by the destination.
Image Resizer and Image Compressor are server-assisted: the selected file is uploaded to process it, and the result is returned for download. Do not use these tools for images your data policy forbids sending to a server. Browser-only alternatives are available elsewhere in the catalog, but the exact processing path and format support vary by tool.
This workflow deliberately verifies the actual artifact instead of promising a fixed file size. A smaller image can still exceed an upload limit, and aggressive compression can make a technically valid upload unusable to readers.
The fit descriptions follow Sharp's `resize` options, including the endpoint's withoutEnlargement behavior.