Prepare a readable signature
Crop empty margins before sizing if the portal also has dimension limits. Keep enough contrast between the signature and background, and use PNG when transparent edges matter.
Treat signatures as sensitive documents
This tool processes the file in the browser and never needs to store it. Download the result to a trusted device and remove temporary copies when the application is complete.
Scan or photograph a signature clearly
Use dark ink on clean white paper and even lighting. Avoid shadows, folds, colored backgrounds, and camera blur. Capture enough resolution for smooth strokes, then crop unnecessary margins before the file-size step if the receiving portal also limits width, height, or aspect ratio.
Do not enlarge a tiny, blurred capture merely to increase KB. More file bytes cannot restore a missing pen edge. Return to the paper and create a cleaner source when the signature looks soft, clipped, unevenly lit, or contaminated by background texture.
Choose PNG or JPG from the portal rule
PNG keeps sharp strokes and can preserve a transparent background, which is useful when a form places the signature over another document. JPG is accepted by many application systems and can be smaller, but its lossy compression may add halos around thin lines. Use the exact extension requested by the destination.
If the portal requires a white background, transparency may not help. Preview the final image on the intended background and ensure the signature remains dark, readable, and fully inside the frame. Never rename a file extension without converting its actual format.
Reach a minimum without rewriting the signature
When the source is below the target, preserve-and-pad keeps its image bytes and adds compatible trailing data until the exact size is reached. The signature shape, pixel dimensions, background, and format stay unchanged. This is safer than repeatedly exporting a sensitive image through third-party tools.
A larger container does not improve authenticity or quality. Some strict portals may reject trailing data, so retain the original and use a re-encoded result inside the accepted range if necessary. The browser reports an error rather than returning a corrupt or silently converted signature.
Use a privacy and submission checklist
Process the signature on a trusted device, download it into an appropriate folder, and avoid public or shared computers. This website does not upload the source, filename, EXIF, preview, or result. Analytics receive only coarse format and size buckets when configured, and file regions are masked from session diagnostics.
Before submission, open the result and confirm the exact bytes, extension, dimensions, aspect ratio, background, and visible strokes. Compare it with the destination preview so no edge has been clipped or placed outside its signature box on the final receiving screen. Keep the original separately until the application is accepted, then remove temporary copies according to your own document-retention needs.