Compress Image to 90 KB

Compress an image to 90 KB — where per-image savings start showing up on your bandwidth bill.

Supports JPEG, PNG, WebP, GIF, BMP and more — up to 50 MB

How to compress an image to 90 KB.

The target is preset, so this takes three steps — plus what to expect at 90 KB.

1
Step 1

Upload your image

Click upload or drag and drop any JPEG, PNG, WebP, SVG, or GIF file from your device.

2
Step 2

Target is already set to 90 KB

This page is preset to 90 KB, so there is nothing to type. Choose JPEG or WebP output for the most efficient result at this size.

3
Step 3

Compare, then download

Press compress and check the result against your original in the slider. Roughly 1400 × 1400 px is the realistic pixel budget at 90 KB — download when it looks right.

Getting the best results

Multiply by your traffic

Per-image savings look trivial until you multiply. Trimming 100 KB from an image on a page viewed 100,000 times a month saves 10 GB of transfer every month.

Set long cache lifetimes

Compression reduces the first transfer; caching removes the repeats. Serve images with a long max-age and a versioned filename so returning visitors download nothing.

Compressing an image to 90 KB.

What 90 KB is actually for, what it can hold, and how to get there without wasting quality.

What 90 KB is good for

90 KB is a size at which arithmetic starts to matter. An image served a million times at 90 KB moves 90 GB; the same image at 300 KB moves 300 GB.

For a site with real traffic, compression is a running cost decision as much as a speed one. The saving repeats with every single request.

Where this size is required

High-traffic pages, CDN-served assets where transfer is billed, mobile applications bundling images, and any site where bandwidth is a line item.

What to expect at 90 KB

Photographs stay clean to roughly 1400 × 1400 pixels, which covers most in-page imagery on a desktop layout.

Frequently asked questions.

Everything you need to know about compressing images to 90 KB.

On metered bandwidth or a CDN, directly and measurably. On a flat-rate plan the benefit is speed and headroom rather than money, which is still worth having.

Yes. A CDN reduces distance and latency but still transfers whatever bytes you gave it. Some can convert formats on the fly, but starting from a well-compressed original is always better.

Multiply the per-image saving by your traffic. Trimming 100 KB from an image on a page served 100,000 times a month saves about 10 GB of transfer every month.

No. A CDN shortens the distance but still transfers the bytes you gave it. Some can re-encode on the fly, but starting from a well-compressed original is always cheaper.

Yes, and it matters more there. Bundled images are downloaded by every user on install, so the saving applies to every single download rather than per page view.

For a photographic JPEG, roughly 1400 × 1400 px is the practical ceiling before compression becomes visible. Flat graphics, screenshots, and document scans do considerably better, because they contain less fine detail to preserve.

No. Images are processed on our secure server only to perform the compression and are deleted immediately after your download. They are never stored, shared, or accessed by anyone.