Compress an image to 90 KB
A practical size for screenshots in support tickets, documents and chat.
- Private by defaultDeleted within an hour
- Super FastProcess in seconds
- No Sign-upStart instantly
How it works
Add your images
Drag and drop, paste, or pick files. They upload over an encrypted connection.
Pick a quality or a target size
Use the quality slider, or tell it exactly how many KB or MB you need.
Download
Save each file, or grab them all at once as a ZIP.
Screenshots are the pictures people send most often at work, and they are usually heavier than they need to be. A full-screen capture from a modern monitor can run past a megabyte, and 90 KB is plenty to keep it readable.
The tool searches for the best setting that fits under 90,000 bytes. Screenshots have flat colour and sharp text, so PNG or WebP often gives a better result than JPEG, and the Format menu lets you try both.
Before you compress, crop to the part that matters. A cropped screenshot is easier to read and smaller to send, and no one needs to look at the whole desktop to see an error message.
Why screenshots are heavy
A capture from a high-resolution display can be 3000 pixels wide, and every one of them is sharp text on a flat background. That detail is more than a ticket needs. Scaling the capture to 1400 pixels wide keeps the text legible and cuts most of the weight.
Keeping text readable
Compression damages thin text first. Check the smallest label in the result at full size. If the characters look smeared, switch from JPEG to PNG or WebP, or raise the target slightly. Never trust the thumbnail to judge text.
Hiding private details
Before you send a screenshot, look for names, email addresses and account numbers. Compressing does not hide them. If you need to cover something, edit the picture first, and compress after, so the cover is part of the final file.
Documents and tickets
Support teams often attach several images to one ticket. At 90 KB each, ten attachments weigh under a megabyte, which sits well within most limits. Consistent compression also makes the ticket faster to open for everyone who reads it.
Screen recordings are different
This page handles still pictures. A recording or an animated capture needs a different kind of tool, and each frame of it is a picture of its own.
Sharing screenshots in chat
Chat tools often compress what you send, and a heavy screenshot can end up smeared. Sending a file that is already light and sharp gives the tool less to damage. A 90 KB PNG of a cropped error message usually arrives clean.
Sender and recipient then see the same picture.
File names you can search for
Name the screenshots you keep for later with something descriptive, such as login-error-page-3.png. Half a year on, you will find the file in seconds instead of opening dozens called Screenshot 1 and Screenshot 2.
It is a small habit that pays off with every ticket.
Frequently asked questions
PNG or JPEG for a screenshot?
PNG or WebP keep text sharper. Use JPEG only if the screenshot contains a photograph.
How wide should a screenshot be?
1200 to 1600 pixels wide is readable for most documentation.
Can I paste a screenshot straight into the tool?
Yes. Paste it with the keyboard, drag it in, or pick the file from your device.
Will my screenshot be uploaded anywhere else?
No. It is processed on our server and deleted, and nothing is passed to third parties.
Why is my result below 90 KB?
A simple screenshot reaches its best quality well under the limit, so the tool stops there.
Can I mark up the screenshot before compressing?
Yes. Add arrows or boxes in any editor first, then compress, so the marks stay part of the picture.