If you already have a clear signature image, the difficult part is usually not the signature itself. It is making that image satisfy an upload rule without damaging the handwriting.
A form may ask for width and height, a file-size range, an accepted format, or several at once. Treating those as one problem is how signatures end up stretched, tiny, clipped, or technically “under 20 KB” but still rejected.
If you still need to draw or type a clean signature first, use the Signature Generator guide. This guide starts after you already have the signature image.
Read the upload requirement as separate constraints
Suppose an application says:
JPG, 300 × 80 pixels, 10–20 KB
That short line contains three different tests:
- Format: the file must be JPG/JPEG.
- Dimensions: the image canvas must be 300 pixels wide and 80 pixels high.
- File size: the encoded file must fall between 10 KB and 20 KB.
Passing one test does not make the others correct. A 15 KB image can still have the wrong dimensions, while a correctly sized image can still exceed the KB limit or use an unsupported format.
Also read the wording carefully. “Maximum 20 KB” means the file should not exceed that ceiling. “10–20 KB” is a range, so a 7 KB file can be too small even though it is below 20 KB.
Treat examples like the one above as illustrations only. For a real application, follow the current dimensions, file-size range, format, background and other requirements shown by the official portal or notification.
Canvas size is not the same as the visible signature
An image has a rectangular canvas. Your handwriting occupies only part of that rectangle.
Resizing changes the whole canvas, not just the ink. If a small signature sits inside a large white image, reducing that canvas to a narrow upload box also reduces the handwriting. The final width and height may be correct while the signature itself looks tiny.
Two files with identical final dimensions can therefore look very different depending on how much of each canvas the handwriting occupies.
Blank space and KB should not be confused, either. A plain background can compress efficiently, so removing white margins does not automatically guarantee a dramatic reduction in file size. The main reason to control the margins is to use the final canvas well and keep the signature readable.
Aspect ratio: why signatures get stretched or squashed
Aspect ratio is the relationship between width and height.
A 300 × 100 image has a 3:1 ratio, while a 300 × 80 target is 3.75:1. Forcing one directly into the other by changing width and height independently alters the shape of every stroke. Larger mismatches produce obvious stretching or squashing.
The safer options are to reframe the source to a shape closer to the target or fit the image while preserving its proportions. Which method is appropriate depends on the requirement and how much blank area exists around the handwriting.
A useful rule is simple: changing the canvas is usually better than changing the geometry of the handwriting.
Crop or reframe before the final resize
Cropping should remove unnecessary margins while preparing a canvas shape that can fit the required aspect ratio without distorting the handwriting.
“Crop tightly” does not mean cut right up to the ink. Leave a small safety margin around the complete signature. Check the first stroke, the end of the last letter, dots, underlines and any flourish that extends above or below the main writing.
The goal is not the smallest possible rectangle. It is a sensible frame for the required output shape. If the target is wider than your current crop, some horizontal margin may be useful.
Cropping after forcing the image into exact dimensions is often too late: the handwriting may already have been distorted or reduced unnecessarily.
Pixels and KB solve different problems
Pixel dimensions describe the geometry of the image. KB describes how much data the saved file occupies.
The two are related, but there is no fixed conversion such as “300 × 80 pixels always equals 20 KB.”
Two images with the same dimensions can have different file sizes because format, compression quality, background noise and image detail all affect encoding.
This explains a common upload problem: the KB value is correct, but the form still rejects the file because its dimensions are wrong. Reducing file size does not automatically resize width and height.
Setting exact dimensions can also change the encoded file size, so a previously compliant KB value may change after resizing or export.
If the dimensions are already correct and the form only asks you to reduce the file size, use the Signature Compressor instead of resizing the image unnecessarily.
When dimensions and KB both matter, order matters
A practical sequence is:
- start from the best existing copy of the signature;
- crop or reframe it for the target shape;
- set the final pixel dimensions;
- use the required format and background;
- adjust compression to meet the KB rule;
- inspect the final downloaded file.
The important part is that compression comes near the end.
If you compress first and resize afterward, the later export can change the KB value again while working from a source that may already have lost fine stroke detail.
Once the source is framed correctly, the Signature Resizer can be used to set the required dimensions and file-size constraints. The portal's requirement should decide the values; the tool should not decide them for you.
Changing format can also change file size, so use the type the destination accepts. Do not remove a background merely because the option exists; change it only when the destination allows or requires it.
When the requirement is in centimetres
A physical size such as “2 cm high” does not describe one unique pixel height by itself. To convert physical dimensions into pixels, you also need a resolution value, commonly expressed as DPI.
The relationship is:
pixels = inches × DPI
and:
inches = centimetres ÷ 2.54
So 2 cm is about 236 pixels at 300 DPI but only about 76 pixels at 96 DPI. That is why the same centimetre measurement can produce different pixel values under different DPI assumptions.
If an application gives both physical dimensions and a required DPI, use both. If it gives only pixels, you do not need to invent a centimetre conversion. Follow the specification actually provided.
Protect thin strokes during strong compression
Signature images are sensitive to aggressive processing because a small dot, thin line or faint ending stroke may carry meaningful detail. When the KB limit is strict, inspect those areas closely.
Avoid repeatedly compressing an already reduced JPG. Repeated lossy exports can soften edges, so keep a better original and create each required output from that source.
Background cleanup also deserves a close look. If faint ink is similar in tone to the paper, an aggressive cleanup operation can remove part of the signature along with the background.
There is a practical limit to compression. Some large-dimension, tiny-KB combinations require visible quality loss, so use only as much compression as the actual requirement demands.
Diagnose the final downloaded file, not only the preview
The downloaded file is what the portal receives. Open it and check its actual properties before submission instead of relying only on the editor preview.
| What you see | What to check first |
|---|---|
| KB is correct but upload still fails | Pixel dimensions, format, minimum file size and other portal rules |
| Correct dimensions but signature looks tiny | Excess blank canvas around the handwriting |
| Signature looks wide, flat or unusually tall | Aspect ratio was probably forced instead of reframed or fitted |
| File is below a stated minimum | The requirement is a range, not only a maximum |
| Dots or thin endings disappeared | Compression or background cleanup may be too aggressive |
| Dimensions changed after another edit | The file was resized, cropped or re-exported again after the earlier check |
For a final measurement, the Signature Size Checker can confirm the downloaded file's pixel dimensions, file size, format and aspect ratio without changing it.
A good signature upload is not simply “small enough.” It is a file in which all of the stated constraints agree at the same time and the handwriting is still complete and readable. Read the requirement literally, protect the shape of the signature, compress only after the geometry is settled, and verify the actual file you are about to submit.