Application portals — exams, banks, government services, job sites — often demand a signature image inside a narrow size range, commonly under 20KB, and sometimes within fixed pixel dimensions as well. A scan or photo straight from your phone is usually many times too large. Here is the reliable way to get it down to size without it turning into an unreadable smudge.
Why a signature scan is so big
A signature is mostly empty white space with a few thin strokes, so it should compress to almost nothing. The reason a raw scan is large is simply resolution: a phone camera captures it at millions of pixels, and often with a grey or shadowed background. Cut the pixel count and clean up the background and the file collapses to a few kilobytes.
Step by step
- Crop tight to just the signature, removing the surrounding paper and any margin. Use Crop Image.
- Flatten the background. If the scan is grey or shadowed, a clean white background helps it compress far smaller — and looks more professional in the form.
- Resize the width down. A signature rarely needs to be wider than about 600 px to stay crisp. Use the Signature Resizer or Resize Image.
- Save as JPG and compress to target. The resize-to-20KB and compress-to-20KB workflows aim straight at that limit.
- Check legibility at the size it will actually display in the form — zoom to roughly that scale and make sure the strokes are clear.
If you cannot reach 20KB
If the file will not drop under the limit while staying readable, reduce the dimensions a little further before compressing harder — shrinking pixels protects clarity better than crushing quality alone. A clean black-on-white signature compresses extremely small, so a stubborn file almost always means there is leftover background, colour, or shadow in the image. Re-crop, flatten to white, and try again.
Common portal rules to watch
- Exact KB cap — usually 10–20KB for signatures. Use a target-size workflow rather than guessing.
- Pixel dimensions — some forms also specify width and height; match them before compressing.
- Format — JPG is the safe default; a few portals ask for PNG.
- Background — many require white; flatten any grey scan.
Quick recap
The order is what makes this painless: crop tight → flatten to white → resize the width → save as JPG → compress to target. Jumping straight to "compress harder" is what produces a grey, fuzzy signature that still misses the limit. A clean signature is mostly empty white space, so once the crop and background are right, landing at 10–20KB is almost automatic. If your portal also lists exact pixel dimensions, set those during the resize step rather than after compressing, so the final file ends up at both the right size and the right shape in one go.
Privacy note
Your signature is sensitive — it is your actual legal mark, and you would not want it sitting on an unknown server. Doing this in the browser means the image is cropped, resized, and compressed on your own device and not uploaded to a third party, which is exactly what you want for something like this. You can confirm it the same way you would test any tool here: load the page, switch off your connection, and watch it keep working — proof the file never travelled anywhere.
Use the tool: Signature Resizer — free, runs in your browser where supported, no file is uploaded to a server.
Frequently asked questions
What pixel size should a signature be?
Around 300–600px wide is usually enough to stay crisp while keeping the file tiny. Check your form for any specific dimension requirement.
Why will my signature not go under 20KB?
Usually leftover background, shadow, or too-large dimensions. Crop tightly to the signature, flatten to a white background, reduce the width, then compress.
Is my signature uploaded anywhere?
No. Cropping, resizing, and compressing all happen in your browser, so your signature stays in your browser.
Should the signature be JPG or PNG?
JPG is the safe default and compresses a clean signature very small. Use PNG only if the form specifically asks for it.