Signature background remover FAQ: PNG, privacy, and limits

The viewer may place empty pixels on a white canvas. Export PNG or WebP, then put the file over a colored page to check the alpha channel.

Use PNG when the page must remain visible behind the ink. WebP can preserve transparency where supported; JPG always needs an opaque background.

Yes. Keep the page flat, the camera parallel, and the mark away from printed text, stamps, and nearby lines.

It keeps the accepted canvas dimensions, but the mask is estimated internally. Inspect thin strokes and use Restore when the source confirms a pale line.

The selected file and generated result stay in the current browser tab. Model and site assets may download, but the signature image is not sent to an image-processing server.

Wait for the model progress message, check the connection, and retry with a smaller photo if the browser reports a memory problem. Download finished results before refreshing.

The editor accepts up to 50 files within its combined session pixel budget. Large scans can reach the memory limit first, so process a smaller group when needed.

Only when the signer has clearly authorized the specific use. Removing paper does not create consent, identity proof, or signing authority.

Lower the removal strength, use a sharper scan, and compare the output over a dark preview. Choose Original or Blue when the editor offers that option.

Crop closer to one signature and reduce uneven paper shadows before processing. If a line touches the ink, use Erase and Restore around the affected stroke.

Download a transparent PNG, insert it as a picture, choose a wrapping mode such as In Front of Text, and resize from a corner.

No. A PNG is a visual image of handwriting. A certificate-based signature uses a digital identity and may provide tamper evidence.