Skip to content
Esc

Increase image size in KB

Files never leave your device

Upload forms that say "minimum 20 KB" or "20–50 KB" reject photos and signatures that were compressed too far. Drop the image, pick the size, and get a file of exactly that many bytes that looks identical, with the same width and height. It runs in your browser; nothing is uploaded.

Target size
1 KB is
Method

The picture is not re-saved: hidden comment data is added inside the JPG or PNG until the file is exactly 50 KB (51,200 bytes). WebP, HEIC and other formats are saved as JPG first. Form gives a range like 20–50 KB? Aim for the middle.

How to use it

  1. Pick the target: 20, 50, 100, 200 or 500 KB, or type your own. If the form gives a range, such as 20–50 KB, pick a number in the middle.
  2. Keep 1 KB = 1,024 bytes unless the form says otherwise: that reading gives the larger file, so it clears a minimum either way. Keep every pixel is the default; choose Higher quality first if a portal strips hidden data.
  3. Drop one or more images, or press Try a sample photo. Each result shows the exact bytes and the unchanged pixel size; download them one by one or as a zip.

Details

Keep every pixel
JPG: comment (COM) segments are added after the file header. PNG: one tEXt chunk is added before the end. Both are standard parts of the format that viewers skip, so the picture is not re-saved
Higher quality first
Re-saves as a JPG at the highest quality that stays under the target (searched between 50 and 100), then adds padding for the last few bytes. The file grows with real image data, which survives portals that strip metadata
Exact size
The file is built to the exact byte count, then read back: it must decode at the same width and height, or it is not offered
Kilobyte
1 KB = 1,024 bytes by default (20 KB = 20,480 bytes), which passes a minimum under either reading. Switch to 1,000 if the form defines KB that way
Input
JPG and PNG keep their format. WebP, HEIC, AVIF, GIF and BMP are saved as JPG first, since most forms ask for JPG
Limits
Only makes files bigger. A file already over the target is left alone, with a pointer to Compress image

Questions

Are my files uploaded?

No. The page loads its code once, then reads and processes your files inside the browser tab. Nothing is sent to a server; you can confirm it in your browser's network panel while a file converts.

Does increasing the KB improve the photo?

No. A bigger file does not add detail. Keep every pixel leaves the picture exactly as it was; Higher quality first re-saves it with less compression, which can remove a little blockiness but cannot restore what an earlier save threw away. Start from the original photo when you can.

Will the portal accept a padded file?

Most portals check only the file type, the byte size and sometimes the pixel size, and a padded JPG or PNG is a valid file that opens everywhere. A few systems re-encode uploads or strip comments; if yours rejects the file or shows a smaller size, use Higher quality first, which adds real image data.

The form says 20–50 KB. What should I choose?

Pick a value inside the range, ideally the middle such as 30 KB, so the file passes whether the form counts 1 KB as 1,000 or 1,024 bytes.

Why not just enlarge the photo's pixels?

Upscaling blurs the image and can break a form's pixel limits, such as a 200 × 230 px photo rule, and the file size it produces is hard to predict. Padding hits the exact size without touching the pixels. If the form also wants a specific pixel or cm size, set that first with Resize image in cm.

My signature is 8 KB and the form needs 10–20 KB.

Set the target to 15 KB and drop the signature. If it still needs cropping or cleaning, run Compress signature to 20 KB first with Keep at least 10 KB on, then come back if it lands below the floor.

Can I do several photos at once?

Yes. Drop them together; each is enlarged to the same target, and Download all saves a zip.