Decide what needs to become smaller

A photograph has both pixel dimensions and an encoded file size. A 4000-pixel-wide photograph can be unnecessarily large for a small web card even when its JPEG quality is already low. Conversely, a small screenshot may need sharp lettering more than a dramatic percentage saving. Start by deciding where the exported image will appear and which details must survive.

Keep your original outside the working copy. Repeatedly opening and saving a lossy result can add damage without giving you more information. When you want to compare settings, return to the same original so that each result has a fair starting point.

Use a measured first pass

In Compress Image, Balanced starts at 82% quality. That is a starting setting, not a guarantee of identical savings or quality for every file. Process once and read the result card. Compare the original and exported byte size, then open the downloaded image at the size your audience will actually see.

Look at hair, small lettering, fences and smooth sky gradients. If they show rough blocks or smearing, raise quality. If the picture looks good but is still too large for an upload limit, consider whether the receiving page really needs the original dimensions before lowering quality further.

Work through an example

Suppose a 2400×1600 photo is intended for a layout that displays it at 1200 pixels wide. A proportional resize gives 1200×800 pixels. Use Resize Image for that dimension change, then try a moderate JPG or WebP export. The final file size depends on the picture and encoder, so check it rather than assuming a specific KB result.

If your receiving form accepts only JPG, choose JPG even if another format makes a smaller file. Transparency is also a reason to choose differently: an image with transparent corners should remain PNG or a supported transparent WebP. A small JPG that fills transparent space with a colour may fail the actual design requirement.

Choose the right compressor route

Compress Image is the single-picture quality workflow. Batch Image Compressor applies shared settings to several pictures and gives separate result downloads. Reduce Image Size combines smaller dimensions with quality choices. Optimize Image provides web-oriented starting presets and format choices. These routes overlap in implementation but solve different decisions.

For a batch, test one representative photo before processing a large selection. A shared setting is convenient, but a textured photo and a simple graphic will not produce identical savings. Inspect unusually large or unexpectedly tiny outputs instead of judging the entire set from the first result.

Diagnose an unsatisfactory result

A PNG can remain large because its output is lossless; the JPG quality slider does not make PNG encoding lossy. A file can also grow if its original was already efficiently compressed or if its output format changes. More saving is not always the better result.

There is no automatic exact-KB target guarantee in these tools. For a strict form limit, compare the actual exported bytes, reduce dimensions or quality, and test again. Keep the smallest version that still looks appropriate for its purpose rather than pursuing a large savings percentage for its own sake.

When a form asks for a limit in KB

Read the dimensions requirement before adjusting quality. If the form requires a specific width and height, resize a copy to those dimensions first. Then compare the actual exported bytes with the maximum file size. The quality number is an encoder setting, not a guaranteed percentage saving.

Try the next quality setting only if the file remains too large, and inspect lettering and face detail after every meaningful change. If the target cannot be reached at acceptable quality, a different format or more suitable source may be necessary. The current tool does not offer a guaranteed exact-KB solver.