Increase Image Size in KB / MB

Some forms reject a photo for being too small. Set the minimum size your form demands and this tool raises the file to meet it — the picture itself is untouched.

Why would a form want a bigger file?

Minimum size rules exist to filter out unusable uploads. A 2 KB image is usually a broken file, a blank scan, a thumbnail, or a placeholder someone uploaded by accident. Portals cannot easily judge whether a picture is legible, so they use file size as a rough proxy for "this contains something real" and set a floor — commonly 10 KB or 20 KB.

The rule catches honest uploads too, which is why this page exists. A signature written in black ink on white paper and scanned cleanly compresses extremely well, often to three or four kilobytes. It is perfectly legible at full zoom, and the form still refuses it.

Why your file came out so small

Small files are usually a sign of an efficient image rather than a poor one. The common causes:

CauseWhy it compresses so far
Clean signature or line drawingTwo tones, no texture — almost nothing for JPEG to encode
Small pixel dimensionsFewer pixels means fewer bytes, regardless of quality
Already compressed onceDetail was discarded on a previous save and cannot return
Screenshot of flat colourLarge uniform areas cost almost no bytes
Saved at low qualityThe exporting app chose an aggressive setting

Notice that none of these mean the image is unusable — which is precisely the mismatch between the rule and reality.

How this tool increases file size

Two mechanisms, applied in order.

First, quality. The image is re-encoded at a higher JPEG quality setting, which preserves more of the detail present in the source and produces a genuinely larger file. When your source has detail to spare, this alone often clears the minimum, and the result is a better image than you started with.

Then, padding. If the file is still under the floor at top quality, the tool inserts data into a JPEG comment segment — a section of the format specifically designed to hold text that decoders skip. Every JPEG decoder reads the segment header, jumps past it, and renders the image exactly as it would have anyway.

The output is a standards-valid JPEG of the size you asked for, displaying pixel-for-pixel the same picture. Nothing is stretched, upscaled, blurred or invented.

What not to do instead

Do not enlarge the pixel dimensions. This is the advice you will find most often, and it degrades the image. Upscaling invents pixels that were never captured: a signature's strokes go soft and furry, a photograph looks smeared, and text loses its edges. Worse, many forms cap dimensions as well as file size, so you can fail a second rule while fixing the first.

Do not convert to BMP or TIFF to inflate the size. It works — uncompressed formats are enormous — but most portals accept only JPG, so the upload fails on format instead.

Do not add a visible border or background block. It changes what the reviewer sees, and on a photograph or signature that can itself be grounds for rejection.

Meeting a range: minimum and maximum together

Where a form asks for 10–20 KB, fill in both boxes. The tool aims inside the window rather than at one edge of it: it compresses down if you are over 20 KB, pads up if you are under 10 KB, and leaves the file untouched when it already fits. One pass satisfies both rules.

Your fileRequirementWhat happens
4 KB10–20 KBQuality raised, then padded to 10 KB
14 KB10–20 KBReturned as is — already valid
180 KB10–20 KBCompressed down to just under 20 KB
4 KBat least 20 KBPadded to 20 KB, no upper bound applied

Is padding acceptable?

A fair question, and worth answering plainly. Padding satisfies a byte-count rule without changing what the reviewer sees. It does not alter, fake or enhance the content of your photograph or signature — the image is exactly the one you scanned.

What it does not do is turn an unsuitable image into a suitable one. If your scan is genuinely illegible, or the photograph does not meet the portal's rules about background and framing, padding it to 20 KB does not help and the application will be rejected on the real grounds instead.

We also cannot promise how any specific portal behaves. Nearly all validate file size, dimensions and format, all of which a padded file satisfies — but a portal is free to inspect a file however it likes. Test with your own form, and keep the original.

The alternative: add real detail instead

If you would rather grow the file honestly than pad it, increase the information in the source:

Any of these may lift you past the minimum without padding at all. The tool tells you when the result was padded, so you will know which happened.

If the result is still rejected

Check that the file is JPG and not PNG — padding applies to JPEG output only, since the comment segment is a JPEG feature. Confirm the dimensions still match the form's specification, since some portals check both rules and a file can pass one while failing the other. And verify the number: 20 KB means 20,480 bytes, so a form wanting "more than 20 KB" may want 20,481 rather than 20,000.

Questions

Does padding damage the image?

No. The padding sits in a comment segment that decoders skip, so the visible pixels are byte-for-byte identical to the unpadded version.

Will the portal detect the padding?

Portals check file size, dimensions and format, and a padded file is a standards-valid JPEG that opens normally in any viewer. We cannot promise how a specific portal behaves, so test with your own form and keep the original.

Can I increase a PNG in size?

Padding applies to JPEG output, since comment segments are a JPEG feature. Choose JPG when you need to meet a minimum; for PNG the only way to grow the file is more pixels, which costs quality.

My image is 4 KB and the form wants 20–50 KB. Will this work?

Yes. Set the minimum to 20 KB and the maximum to 50 KB, and the result lands inside that window.

Why not just enlarge the image until it is big enough?

Upscaling invents pixels that were never captured, so strokes and text go soft, and many forms cap dimensions separately — you can break a second rule while fixing the first.

How can I tell whether my file was padded or genuinely re-encoded?

The tool says so beneath the result. If the note about padding does not appear, the extra size came from a higher quality setting rather than padding.

Other size tools