Compression decision guide
Compress an image by controlling dimensions first, then quality
Good compression is not the smallest possible file. It is the smallest reviewed copy that still works for the website, form, message, document, or archive you are preparing.
Start with the destination, not a quality number
A 4000-pixel phone photo is often far larger than an email, product listing, or article needs. Reducing its dimensions can remove more bytes than lowering quality aggressively, while keeping edges and textures more stable. Find the largest size the image will actually be shown, allow a little room for high-density screens or later crops, and use that as the maximum width.
Quality controls are encoder settings, not universal percentages. A value of 80 in one application does not guarantee the same file size or visible result in another. Use the number as a repeatable starting point, then judge the downloaded pixels.
Keep the original. Compression should create a delivery copy. Do not overwrite the only source until the recipient or platform accepts the result.
Use a practical starting range
| Destination | Start with | Inspect closely |
|---|---|---|
| Chat or email preview | About 1200–1600 px on the long edge; JPG or WebP for photos | Faces, small labels, and screenshots embedded in the image |
| Website content image | Match the rendered width; test WebP and a compatible fallback where needed | Gradients, product edges, layout shift, and mobile rendering |
| Interface screenshot | Keep its intended pixel dimensions; prefer PNG for crisp text | One-pixel lines, small type, icons, and transparency |
| Print or future editing | Keep a source-quality file; create a separate smaller preview | Required print dimensions, color handling, and repeated export loss |
Separate the 3 compression decisions
- Dimensions: remove pixels the destination cannot display. This is usually the safest large reduction.
- Format: use JPG for photographic tones, PNG for transparency or exact hard edges, and WebP for supported modern delivery.
- Encoder quality: lower it gradually only after dimensions and format are sensible.
These controls solve different problems. Converting a huge photo to WebP without resizing can still leave an unnecessarily large file. Saving a software screenshot as low-quality JPG can meet a size limit while making the text harder to read.
Run one representative test before a batch
- Keep the source file and choose one representative test image.
- Set the maximum width for the real destination.
- Choose JPG, PNG, or WebP based on the image content and compatibility need.
- Start with a balanced quality setting and process the test image locally.
- Compare dimensions, file size, and visible artifacts before downloading the batch.
Choose a test image that contains the difficult details in the batch: hair, foliage, fine product texture, a smooth sky, small text, or strong dark-to-light edges. If a single setting must cover several image types, review more than one sample. A setting that works for portraits may fail on screenshots.
Review the downloaded result at 100%
File size is easy to measure, but it is not the quality verdict. Open the output and compare it with the source at the same zoom. Look for block patterns, ringing around text, banding in skies and gradients, loss of texture in hair or fabric, and color changes near saturated edges.
Then test the real destination. A web image should be checked in the page at desktop and mobile widths. An attachment should be reopened after sending it to yourself. A form upload should be confirmed by the service instead of relying only on the local file extension.
Know what compression does not solve
- It cannot restore detail already missing from a blurry or previously damaged image.
- It does not guarantee that all metadata is removed; use a metadata-specific export and inspect the result.
- It cannot make visible names, faces, addresses, or account details private.
- It cannot predict how another platform will recompress, crop, or recolor the upload.
AllPic performs the image operation in the browser session, but the web page still loads site assets and may load optional model resources for AI tools. The compression tool itself does not need an AI model. See the web privacy page for the precise boundary.
Final delivery checklist
- The source file is stored separately.
- The output dimensions match the destination instead of the camera maximum.
- The destination accepts the selected format.
- Detailed areas were checked at 100%, not only as a small preview.
- The downloaded file was reopened and its size, dimensions, and transparency were confirmed.