About SizeMint
A straightforward compressor for a very specific problem.
SizeMint was built around a simple frustration: an image can look perfectly fine but still be too large for the place where you need to upload it. Instead of making people guess at a quality slider, SizeMint starts with the file-size requirement.
Why this exists
SizeMint started with an annoyance: every answer to "my photo is too big" was either install an app, upload your identity photo to a stranger's server, or guess at a quality slider and re-check the file size five times. None of that felt right for something as routine as shrinking a picture for a form.
So the whole tool is organized around the one number that actually matters — the target file size — and everything runs in your browser, because a photo should not have to travel to a server to get smaller. It is a small independent project, deliberately narrow: one job, done honestly, with the result reported as it is.
Choose 20KB, 100KB, 1MB or your own limit.
The core image workflow runs locally in the browser.
The tool reports when a target could not be reached.
What SizeMint actually does
When you select an image, the browser decodes it and SizeMint creates candidate encodings using standard browser image APIs. For lossy formats, it searches quality settings; if the target remains difficult, it can reduce dimensions and try again. The final Blob is kept in the browser and offered as a download.
This approach is useful for ordinary upload preparation because the core compressor does not need to send the image contents to a SizeMint application server.
Why target file size?
A quality value is not a universal measurement. “80% quality” can produce very different byte sizes for two different photographs, and the same quality number can behave differently between formats. A target such as 100KB is a concrete requirement: either the result fits or it does not.
That is why SizeMint treats target size as the primary constraint and quality as one of the tools used to reach it.
Supported workflow
What SizeMint does not promise
No image compressor can guarantee that every source can become every requested size without changing dimensions or losing visual information. Image complexity, resolution, transparency, browser capabilities and encoding behavior all matter.
SizeMint therefore reports the actual result. If the requested target cannot be reached, it labels the result as a best effort instead of claiming an exact match.
Privacy approach
The core compressor is intentionally designed without an image-upload backend. That does not mean the entire website is invisible to the internet: normal hosting infrastructure can receive technical web requests, and optional advertising services can process information according to their own policies. The Privacy Policy explains the current setup.
Why we built the guides
Compression is a trade-off, not a single magic setting. The SizeMint guides cover practical decisions such as choosing between JPG and WebP, reducing dimensions before quality, preparing a 100KB image and understanding why some images are difficult to shrink.
Keep an original
Compression is intended to create a smaller derivative. For important photographs, design files and documents, keep your original source so you can make a different export later.
Project support
SizeMint is an independent web project. Features, browser support and limits may evolve over time. If you find a problem, the most useful report includes the browser, input format, approximate file size, selected target and what happened.
Contact: idalinux08@gmail.com