Loading console...
Shrink photos to a target size or pixel dimension, in the browser. No upload, no watermark, no signup. Fit a photo under 20 KB for a form, or resize for the web in one step.
An image resizer changes how many pixels a photo contains; a compressor changes how many bytes those pixels take up. They are often the same operation because shrinking the canvas and lowering the encoding quality both reduce file size, just at different layers. This tool does both: pick a pixel dimension, a percentage, or a target kilobyte budget, and it produces a file that meets it.
The reason people usually need it is a hard limit. A government form asks for a photo under 20 KB. An email attachment refuses anything over 2 MB. A web page loads faster if its hero image is 200 KB instead of 4 MB. The tool exists to make a large image fit a specific number, without retaking the photo.
The right format depends on what the image is. Photographs compress well as JPG, where the encoder hides detail you are unlikely to notice at web sizes. Flat graphics, charts, and text screenshots need PNG, because a lossy format leaves grey ringing around crisp edges. And when you only care about size, WebP typically beats both — often at the same visible quality — which is why the target-KB mode works best with it.
The three rules of thumb: photos → JPG, graphics → PNG, “make it as small as possible” → WebP. The format selector here lets you switch between them after processing.
Hitting an exact kilobyte target is really a quality search. The encoder has a quality slider, and the file size moves with it. Rather than guess, this tool binary-searches that slider until the output is at or under your target, then reports the size it landed on. If even the lowest quality cannot reach the target, it tells you the smallest it got so you know the limit was genuinely too tight.
In practice, a phone photo can usually reach 20–50 KB without looking degraded. A busy screenshot with lots of text can, because flat colors compress far better. Knowing the difference spares the false hope of forcing a hard target on the wrong kind of image.
Most online resizers upload your files to a server, process them there, and hand back a link. That works, but it means a photo of a document, an ID, or a face passes through someone else’s infrastructure. This tool is different: it runs on the HTML canvas in your browser, so the bytes never leave your device. For anything sensitive — passports, medical forms, private photos — that difference is the whole point.
If an image shows at 800 px wide, do not ship a 4000 px original. Resize to roughly the rendered width and the page loads faster on mobile.
Modern browsers all accept WebP, and it is usually 25–35% smaller than an equivalent JPG.
Stretching to fill a fixed box distorts photos. A contain-fit preserves proportions and leaves clean margins instead.
For forms and marketplaces with KB limits, hit the target with margin rather than exactly at it, so a client-side re-encode does not tip you over.
No. Resizing and compression happen on your device with the browser’s canvas. You can even open the page offline and it still works.
Use the target-size mode, set 20 KB, choose WebP or JPG, and process. The tool lowers quality until the file meets the goal and shows you the result.
Yes. In pixel mode, enter the target width and height. Aspect ratio is kept on by default so the image is fitted, not stretched or cropped.
Yes. Because it runs in your browser, there is no per-file charge, no daily cap, and no account required. Batch-process as many images as you need.
For the two jobs that come up most — “make this photo under X KB” and “resize this to Y pixels for the web” — this covers both in a single, private, in-browser step. It is a natural companion to the rest of the aitols.toolkit: no upload, no watermark, no account, and the exact numbers you need to get an image past a form or onto a page fast.