Increase Image Size in KB

The upload form has turned your photo or signature away, and not because it is too big. The IBPS and SBI rule for a signature says "Size of file should be between 10kb - 20kb", and yours is a few kilobytes. Nothing is wrong with the picture. This page explains why forms set a floor, the three ways a file can be made bigger, and why the tool above uses the one that leaves the picture alone.

Why a form sets a minimum

The rules quoted on this page give no reason. The likely one is practical: a portal can check a file's size the moment it is chosen, and a very small file often means a tiny or heavily compressed picture. A floor rejects those automatically. RRB's notice sets floors of three kinds for one signature: between 30 KB and 49 KB, "Minimum 140 pixels (width) x 60 pixels (height)", and a scan at a minimum of 100 DPI.

A minimum KB tests the file, not the picture: a sharp image at the right size can fall below it, and a blurred one can clear it. Plain white paper costs a JPEG almost nothing. On a signature test image we made, the IBPS/SBI preferred size of 140 × 60 pixels came to 3,107 bytes at 95% quality, the highest the tool uses, against the same notice's 10 to 20 KB. At the form's own preferred size, quality alone could not reach its minimum.

Three ways a file can grow

A JPEG gets bigger when it keeps more detail, holds more pixels, or carries data that is not picture at all.

Higher quality

Re-encoding at a higher JPEG quality keeps more of what the encoder would otherwise throw away. A 640 × 480 test photo we made, 78,116 bytes, came to 1,12,079 bytes re-encoded at 95%: 43% larger, with no detail that was not already in the photo. The route also runs out: the tool stops at 95%, where the test signature above was still 3,107 bytes.

More pixels

Bytes grow roughly with area, so enlarging a picture makes the file bigger, but the new pixels are guessed from their neighbours and the size no longer matches the form. On a portrait test photo we made, the IBPS/SBI photograph at its preferred 200 × 230 pixels came to 5,852 bytes at 95% quality. If bytes grew exactly in step with area, reaching the 20 KB floor (20,480 bytes) by enlarging alone would take about 3.5 times the area, roughly 374 × 430 pixels, far from the 200 × 230 the form prefers. This tool never enlarges a picture to make its file bigger.

Padding

Extra bytes that are not part of the picture go where every image decoder skips them, so the count can be set exactly and the pixels stay as they were. The tool combines this with the first route: it encodes at 95% quality at the photo's own pixel size, or at the highest quality that fits when 95% would overshoot the target, then pads the gap. A photo already bigger than the target is reduced first, as any compressor would, and padded after.

The comment segment in the JPEG standard

A JPEG file is a run of marker segments followed by the compressed picture, and each marker is two bytes: FF and a code. The JPEG standard, ITU-T T.81 (ISO/IEC 10918-1), defines marker FF FE for comments: data that is not part of the image. A decoder reads the segment's length and jumps over it, so a padded file looks the same in every browser, gallery and editor. The picture data inside the file is untouched: the same pixels decode from the padded file as from the unpadded one.

The length field is 16 bits and counts its own two bytes, so one segment carries at most 65,533 bytes of content: segment = 4 + content bytes, at most 65,537 bytes. In the 500 KB test below, 3,99,921 bytes of padding took six full segments of 65,537 bytes and a seventh of 6,699 bytes, header included. No segment can be smaller than its 4-byte header, so a gap of 1 to 3 bytes cannot be filled exactly. The tool therefore compresses to at least four bytes under an exact target before it pads: the gap is then either nothing or big enough to fill to the byte.

Why 50 KB becomes 51,200 bytes

A kilobyte is 1,024 bytes to Windows and to most upload checks, and 1,000 to an Android phone or a Mac; the MB to KB converter guide goes through the two counts. None of the notices below says which it means.

For a minimum the larger reading is the strict one, so the tool aims at exactly bytes = KB × 1,024. A file of 50,000 bytes shows as 48.83 KB on Windows and fails a check that counts 1,024; 51,200 bytes passes both.

Every row meets a minimum of the number typed, whichever way the form counts. The 30 row is RRB's floor for a signature, and the 200 row is the size of the second test below.

What happened in our tests

We ran the 640 × 480 test photo, 78,116 bytes (76.3 KB on Windows), through this page three times.

At 500 KB, 78.1% of the file is padding. Where the photo was smaller than the target, the pixels stayed 640 × 480, because a form that fixes the pixel size expects it kept.

In the first row the photo was already bigger than the target. Keeping all 640 × 480 pixels would have meant a very low JPEG quality, so it was reduced the way the Image Resizer in KB reduces anything, to 523 × 392 pixels and just under 20,480 bytes, then topped up. A 4,032 × 3,024 test photo of 4.74 MB went the same way at 50 KB: exactly 51,200 bytes at 826 × 620 pixels. If your form fixes the pixel size, set it on a page that has pixel controls.

Forms that set a minimum

Figures are as the official notices print them, checked on 24 September 2026. The last column counts the minimum at 1,024 bytes a KB and the maximum at 1,000.

SSC and RRB take the photograph live during the application, so the signature is the only file of theirs on the list. PAN is missing for a reason. Neither PAN agency's published rules set a floor for the photo or the signature, so a PAN file never needs padding. The PAN page covers both agencies' ceilings.

Keeping inside a range

Every form above sets a ceiling too, and this page makes exactly KB × 1,024 bytes. Type the maximum and the file breaks the ceiling under the 1,000-byte reading: 50 gives 51,200 bytes, or 51.2 kB. The highest whole number safe to type is maximum × 1,000 ÷ 1,024, rounded down: 19 for a 20 KB ceiling, 47 for RRB's 49 KB, 48 for 50 KB, 97 for 100 KB and 195 for 200 KB. For a range, aim for the middle, not either edge: typing 35 for a 20–50 KB rule gives 35,840 bytes.

The form presets on the Image Resizer in KB and the signature page do this for you: best quality under the maximum, then, if the file is short of the minimum, padding to the middle of the byte range. Tested on our images:

The SSC signature, at 709 × 236 pixels (6.0 × 2.0 cm at 300 DPI), came to 13,203 bytes and needed no padding: more pixels, more to describe.

What padding cannot do

Padding satisfies a check on file size, and nothing else.

• It adds no detail. A blurred photo stays blurred, and anyone who looks at it sees the original.
• It does not change the pixel size. IBPS and SBI prefer 200 × 230 pixels for the photograph; RRB wants at least 140 × 60. This page has no pixel controls, so do the whole job on a page that has them; those pages pad in the same step.
• It does not set the DPI. SSC's upload page asks for 300 DPI. That is a number in the file's header, and this page offers no DPI setting; the signature page's SSC preset writes 300 DPI and pads if the file needs it.

What this tool assumes

• A photo smaller than the target keeps its pixel size: it is saved at 95% quality, or at the highest quality that fits, then padded to exactly the target × 1,024 bytes.
• A photo already bigger is reduced first, quality and then pixels if quality alone cannot do it, to at least four bytes under the target, so the padding always lands exactly.
• One exception keeps a small file from failing: a very large, plain image can be small as a PNG and still too many pixels for the target as any JPEG. A 3,000 × 3,000 test scan of 29,977 bytes cannot be a 50 KB JPEG at that size, so it came out at exactly 51,200 bytes at 1,775 × 1,775 pixels, and the note under the result says so.
• The page has no pixel, centimetre or DPI fields, and padding changes none of them.
• The engine underneath is the one the Image Resizer in KB guide describes: the file is handled in this tab and never sent anywhere, and what you save is a JPEG without EXIF data.
• The tool reaches the size you type; whether a form takes the file depends on the form's own checks. It has no connection with any exam body or PAN agency.