Sometimes a website asks me to upload a picture under 150 KB or 200 KB. It sounds simple until the text turns fuzzy or the file suddenly changes from PNG to JPG.
I built a free image compressor partly because I kept running into this. Here is how I approach it.
First, check what the file needs to be
A file’s size, dimensions and format are three different things:
- File size is how much storage it uses, such as 150 KB.
- Dimensions are its width and height in pixels, such as 1200 × 800.
- Format is PNG, JPG or WebP. Some forms require one specific format.
I check the upload form before changing anything. A smaller PNG isn’t much use if the form only accepts JPG.
For photos, start with JPG or WebP
Photos contain lots of colors and fine detail. JPG and WebP can often reduce their file size more effectively than PNG.
But a lower quality slider isn’t a free improvement. If you push it too far, faces, edges and text can become visibly distorted.
My rule is simple: keep a reasonable minimum quality and be willing to reduce dimensions when the file limit is strict. A smaller but readable photo is usually more useful than a large blurry one.
You can try this in the browser image compressor. It won’t force the quality below the minimum you choose. Resizing to meet a target is an explicit option, not something that happens without asking.
For screenshots and documents, PNG often makes sense
Screenshots, UI elements and scans may contain very small letters or sharp edges. PNG often suits this kind of image better.
When a form requires a PNG below 150 KB, I use the PNG to 150 KB tool. It tries to keep the PNG format and original dimensions first.
There is a catch: not every image can fit under 150 KB without losing visible detail. Reducing the number of PNG colors may work for simple graphics, but it may change gradients or fine details. Transparency adds another constraint.
For a scanned form, I always inspect small text, signatures and stamps before using the result. An automatic quality check cannot replace looking at the actual image.
If the target is too small, make a trade-off deliberately
I normally try the following order:
- Keep the original file if it already meets the limit.
- Choose an appropriate format if the upload form allows it.
- Compress carefully, keeping text and important details readable.
- Reduce pixel dimensions only if allowed, rather than destroying quality just to hit an arbitrary number.
- Stop if the requirements conflict. A tool should say it cannot meet the limit instead of silently producing unusable output.
When you need an exact width or height, use the image resizer. It shows the original pixel dimensions before you edit them.
What about privacy?
I sometimes process pictures from work, family photos and screenshots with personal information. I don’t want to upload them to an unknown server just to change their size.
So the Made by Yong image tools process the image on your device in the browser. The image file itself isn’t uploaded to my site.
You can convert formats, resize images or batch-process several files the same way.
That’s the whole idea: make a small, annoying task easier without making you give up control of your images.