Set a target size in KB
Type the maximum file size you need to hit — for an upload limit, email cap or form requirement.
Optimize
Reduce image to a specific size in KB
Files never leave your device
No files yetDrop your file here
or choose a file from your devicePick a maximum file size in KB. The tool tunes WebP or JPG quality, then reduces dimensions when needed to meet the target.
FreeFiles stay on deviceIn-browser
Privacy you can verify
How privacy worksWant to verify local processing?
Use DevTools to confirm this tool does not upload selected files to ImageME for processing.
How it works
Three steps from start to finish.
Let the tool search for the right settings
It runs a local binary search across WebP/JPG quality and, if needed, reduces dimensions until the output meets your target.
Download a file at or under your limit
Export the result, confident it satisfies the size constraint you set — without manually guessing quality values.
Use cases
Where this tool earns its keep.
Meeting strict upload limits on forms and portals
Government forms, job application systems and visa portals often cap photo size precisely — hit that number without trial and error.
Satisfying email attachment caps
Get a photo under a sender's or recipient's attachment size limit without resorting to a separate compression service.
Producing ID or document photos to spec
Many ID photo and document-upload requirements specify an exact maximum size in KB — meet it directly and predictably.
Fitting images into a fixed storage or bandwidth budget
When every image in a batch needs to stay under a certain weight for a database, CMS or app bundle, hit that ceiling reliably.
Tips
Get the most out of it.
Pick realistic targets
A 4K photo at 50 KB is going to look ugly.
Resize first
For very small targets, drop the dimensions before reducing.
Pick WebP
WebP can hit smaller targets at the same visible quality.
Common mistakes
Avoid these before you export.
Setting a target far below what the image can sustain
Asking a detailed 4K photo to fit in 20 KB forces extreme quality loss and visible artefacts — there's a floor below which any photo will look poor, regardless of the algorithm.
Not allowing dimension reduction for very small targets
For aggressive size targets, quality reduction alone often can't get there cleanly — letting the tool also reduce dimensions usually produces a better-looking result at the same final size.
Ignoring the visible trade-off at extreme targets
The smaller the target relative to the source, the more visible the compression becomes. Check the preview at 100% before relying on a very tight target for something that needs to look good.
FAQ
Questions people ask about this tool.
How does the tool decide what to reduce first?
It searches quality settings first, since that usually preserves the most visual detail. If quality reduction alone can't reach your target, it reduces dimensions as well, aiming for the best-looking result at your size limit.
Will it always hit my exact target size?
It aims to land at or under your target — slightly under is normal and expected, since exact byte-for-byte targeting isn't possible with image encoders. It will not produce a file larger than your limit.
What happens if my target is unrealistically small for the image?
The tool will get as close as it can, but very small targets relative to the source will produce visible quality loss — that's a property of compression itself, not a limitation of the search.