SIZEMINT GUIDES
ID photos and documents should not travel to a stranger's server just to get smaller. Here is how to hit 100KB entirely on your own device.
One hundred kilobytes is the comfortable middle ground: job portals, ID document uploads, profile photos and blog images commonly land here. It is generous enough that a well-shot photo keeps visibly good quality, yet small enough to satisfy most upload limits and keep pages fast. If your form states a range ending at 100KB (Railway RRB's 50–100KB photo range, for example), target around 75KB to clear the ceiling with margin.
Most online compressors work by uploading your photo to their server, processing it there, and sending it back. For a landscape that is harmless; for an ID photo, a signature or a document scan, it means your identity documents sit on hardware you do not control. SizeMint processes everything locally in your browser — and unlike most privacy claims, this one is verifiable:
Open your browser's developer tools (F12), switch to the Network tab, then compress a photo. Watch the request list: you will see no image upload traffic, because the file never leaves your machine. Any tool that makes a privacy claim should survive this test — try it on others and compare. Read why browser-local compression matters for the full explanation, and the privacy policy for the formal picture.
Open the SizeMint compressor and drop in a JPG, PNG, WebP or AVIF file. With the Network tab open you can confirm nothing uploads.
Type 100 KB as the target size. The compressor searches encodings automatically to find the best quality that fits under 100KB.
At 100KB most photos look clean, but check the result at the size it will actually be used — a profile thumbnail hides flaws a full-screen view reveals.
Confirm the file size in your file manager before uploading it to the portal. Keep your original as the archive copy.
Phone photos carry hidden EXIF metadata — camera model, timestamps, and sometimes GPS coordinates of where the photo was taken. Before uploading an ID photo anywhere, check what travels with it: on most systems you can right-click the file, open properties/details, and see the embedded data. Stripping EXIF is a separate step from compression, so verify your downloaded file the same way and remove location data before submitting identity documents.
At 100KB the target is rarely the problem — the source usually is. Photos taken in dim light, heavy digital zoom, or aggressive phone "beauty" filters compress poorly because the encoder wastes bytes on noise. Retake in daylight with zoom at 1x. If the file is a PNG screenshot of a photo, converting to JPG first typically doubles the usable quality at the same size.
Enter 100 KB as an exact target instead of lowering a quality slider blindly. At 100KB a good source photo keeps visibly clean quality for ID and web use.
Open the Network tab in your browser's developer tools and compress a photo. If no image data leaves your machine, the claim holds. SizeMint passes this test.
Not automatically — EXIF metadata is separate from pixel compression. Check the downloaded file's properties and strip location data before uploading identity documents.
Yes for the file-size check, as long as dimensions, background and format also match the portal's notification. Size is one check among several.
Need a smaller file? See how to compress an image to 50KB. Need more room? Read how to compress an image to 200KB. For the privacy argument in full, see why browser-local compression matters.
Ready? Open the SizeMint compressor, enter 100KB, and keep your photo on your device.
