Why 100KB is the practical default
One hundred kilobytes is roughly the point where a photograph stops feeling heavy. A page with ten 100KB images weighs a megabyte; the same page with ten untouched phone photos weighs sixty. That difference is the entire reason Core Web Vitals and mobile load times exist as ranking factors.
For upload forms it is equally common. Job portals, university systems and marketplace listings frequently cap images at 100KB, and many of them also display the image at a few hundred pixels wide — so the original 4000-pixel file was never buying you anything.
Choose the right format for the job
The rule of thumb: photographs belong in JPEG, websites benefit from WebP, and flat graphics with sharp edges belong in PNG. Converting a photo to PNG at 100KB is the one combination that reliably disappoints, because lossless formats cannot throw away the detail your eye will not miss.
| Format | Best for | Typical result at 100KB |
|---|---|---|
| JPEG | Photographs, portraits, anything with smooth gradients | Excellent — the standard choice |
| WebP | Websites that accept it; same picture in fewer bytes | Sharper than JPEG at the same size |
| PNG | Logos, screenshots, transparency, crisp text | Good for flat graphics, poor for photos |
| GIF / SVG | Animations and vector art — passed through untouched | Convert first if the form needs a photo |
For website owners: the 100KB budget
If you are preparing images for a site, treat 100KB as a ceiling per image and convert to WebP where the platform allows it. A hero image at 100KB WebP will look better than the same image at 100KB JPEG, and it will load faster than either. Pair it with sensible dimensions — a 2400-pixel-wide image displayed at 800 pixels is wasted bytes no matter how well it compresses.