Pixels and kilobytes solve different problems.
“Too large” can mean a wide image, too many encoded bytes, or both. Start with the actual requirement rather than an arbitrary quality slider.
Dimensions describe the grid.
A 640 × 480 image contains 307,200 pixels. Proportional resizing to width 320 gives height 240: 76,800 pixels. The encoded file is not necessarily one quarter of the original size, because its format and compression also matter.
Bytes describe the file you submit.
FieldWise distinguishes decimal KB (1,000 bytes) from binary KiB (1,024 bytes). A 200 KB target is 200,000 bytes; 200 KiB is 204,800 bytes. If a form uses “KB” ambiguously, use its exact byte limit when supplied. Choosing the smaller limit is conservative, but still does not prove acceptance.
A safe preparation workflow
- Use the checker with the destination’s current technical rules.
- If exact dimensions are required, crop or resize deliberately. Fit adds padding; fill removes edge content.
- Use the compressor if saved bytes exceed the limit. It does not silently resize.
- Check the saved copy again and compare its appearance. Keep the source.
When the target is impossible
Noise, detail and readable text affect encoding. The compressor tests a bounded native JPEG/WebP quality range and reports the actual best-tested result. It may miss the target or produce more bytes than the original. There is no guaranteed reduction percentage.
Technical rules are only part of acceptance.
Application photos can have rules about faces, lighting and authenticity. Our tools do not evaluate those. Refer to the destination’s current instructions; official digital-image guidance is one example of combined rules, not a preset used by this site.