Round targets such as 100 KB, 500 KB, and 2 MB appear everywhere, but they are not quality grades. The same 100 KB budget may be generous for a small flat graphic and brutal for a large detailed photograph.
Think of targets as budgets
| Target | Can be sensible for | Often too tight for |
|---|---|---|
| 100 KB | Small thumbnails, simple graphics, tiny portal photos | Large detailed photos, readable scans |
| 500 KB | Web product images, profile photos, many form uploads | High-resolution print or complex zoom images |
| 2 MB | Detailed web photos, larger document images | Very long scanned documents or high-bitrate video |
The Fitabyte Lab demonstrates this content effect. In our controlled 1600 × 1200 reference files, a flat graphic stored very efficiently, while a synthetic photo-like scene required hundreds of kilobytes at moderate JPEG/WebP settings.
Choose the target from the destination
- Use the published maximum when a portal enforces one.
- Leave a small safety margin instead of aiming at the exact byte boundary.
- For your own website, balance page speed with the dimensions visitors actually see.
- For email, preserve enough quality for the recipient’s task and use a link for very large originals.
- For archival or future editing, keep the source separately; delivery copies can be smaller.
Do not compress to a round number just because a tool offers it
If a website accepts 5 MB and your 1.4 MB photo already looks good, reducing it to 100 KB provides no benefit to that upload. Compression is a constraint-solving step, not a score where the smallest result always wins.
Use Fitabyte Compress when there is a real maximum to meet. If you are deciding between formats first, read WebP vs JPG vs PNG.