JPG
Usually compact for photos. Transparency is replaced with white.
PhotosSet an exact KB or MB target. Your image stays in this browser and is never uploaded.
Processing and downloads happen locally. Refreshing or closing the page clears the current queue.
1 KB = 1024 bytes. 1 MB = 1024 x 1024 bytes.
JPG, PNG or WebP. Up to 20 files, 20 MB each.
The controls are intentionally direct. Choose images, set the byte requirement, then download verified results.
Add one JPG, PNG or WebP, or choose a batch of up to 20.
Choose exact, maximum or minimum size in KB or MB.
Every result is decoded and checked again before download.
Government forms, job portals, exams, identity documents and content systems often enforce rigid file limits. A valid image can still be rejected when its byte count falls outside the stated range. This tool changes the encoded file size without claiming to create new visual detail.
Exact mode is deliberately strict. A 100KB result is 102,400 bytes, not a rounded label placed on an approximate file. Maximum mode is different: it keeps the result at or below the ceiling and avoids adding filler to a smaller valid image. Minimum mode guarantees the result is not below the stated target.
KB and MB measure stored bytes. Width and height measure pixels. An image can keep the same dimensions while its encoding changes, but a very small maximum may require dimension reduction. The result always reports both values.
The browser first tries to keep the original pixel dimensions. For JPG and WebP it searches encoding quality. For PNG it uses the browser's lossless encoder. If a maximum is still unreachable and reduction is allowed, the pixel grid becomes smaller in controlled steps.
Usually compact for photos. Transparency is replaced with white.
PhotosKeeps transparency and sharp edges, but can be larger for photos.
TransparencyOften provides a useful balance of size, quality and transparency.
Modern webThe site does not need your image data to resize it. Files, names, previews and output blobs remain in browser memory. Optional analytics can record anonymous actions such as a completed batch, never file contents or file names.
Refreshing the page clears the queue. Result URLs are revoked when an item is removed or the tool is reset. Re-encoding also removes common EXIF metadata by default, including camera and location fields that may be embedded in a source photo.
No. Processing happens in the current browser tab. The server does not receive image contents, file names or output files.
No. Adding encoded bytes does not create new visual detail. The purpose is to satisfy a file-size requirement, not to perform AI upscaling.
The downloaded Blob must contain exactly the target number of bytes. Targets use 1KB = 1024 bytes and are verified after processing.
JPG and JPEG, PNG and WebP are supported for input and output. GIF, SVG and HEIC are not supported in this version.
Increasing file size usually keeps the same dimensions. Reaching a small maximum may require fewer pixels, and the result shows both dimensions.
Yes in current Chrome, Edge, Firefox and Safari. Large batches may finish faster on a desktop because all processing uses local device memory.
No by default. Re-encoding removes common EXIF metadata, which can include camera and location information.