How to Remove Background from a Scanned Signature

Three things, in order. First, the cutout has to survive at small sizes. Scanned signatures for documents often ends up at 200 pixels wide on a phone, and a soft edge that looked fine in Photoshop turns to mush at that resolution. Second, the export needs to drop straight into wherever the image is going next — a listing, a deck, a thumbnail template — without an extra Photoshop round-trip. Third, it needs to be free or cheap enough that you don't ration use.

Most free tools nail one of those three. A few nail two. The combination that actually saves time for lawyers, founders and HR teams is all three at once, which is why the choice of tool matters more than people give it credit for.

Don't pay for HD output anywhere. Every reasonably modern free tool already exports at full source resolution; the "HD upgrade" is a 2018 pricing fossil that some products still charge for.

Don't manually mask first. Let the AI go, see what it gets right, then fix the 5% it gets wrong. People still do it the other way around out of habit.

Don't worry about file size for the master PNG. Disk is cheap. Optimize the JPG you publish, not the PNG you keep.

For scanned signatures for documents, also: don't crop tight before uploading. The AI needs context at the edges, and you'll re-crop in the editor anyway.

Four common failure modes. Watermarks on the export — easy to spot, deal-breaker if you're publishing. Resolution caps on the free tier — sometimes the export is silently 720 wide even when your input was 4000. Color-bleed halos around the subject — visible when you put the cutout on a new background. And missing alpha softness on hair, which makes portraits look stamped.

BG Clear avoids those by exporting full source resolution with no watermark, running ViTMatte for soft alpha, and applying a color-decontamination pass before the export. If you remove background from signature and the result has any of the four problems above, the tool is the issue, not your photo.

Open the tool. Drag your image. Wait. Download. If you're on a phone, the flow is identical except you tap to pick a photo from your camera roll instead of dragging.

The one detail that matters: don't pre-crop your photo before upload. Give the AI the full frame. It does cleaner edge detection on a wider source and you can crop in the editor or after download. Cropping first sometimes lops off pixels the AI was using as context, and the cutout gets slightly worse for no reason.

For scanned signatures for documents specifically, you'll usually want at least 1,500 pixels on the long edge. Anything smaller and the cutout edges start looking soft when you blow it up later.

Three subtle things make a cutout look real instead of fake. The first is alpha softness around hair and fabric — a hard binary edge looks like the subject was cut out with scissors. The second is no color bleed. If the original background was bright orange, you can sometimes see a faint orange halo on the subject's edge, and that halo follows the subject when you put it on a new background. The third is shadow. A cutout floating with no shadow looks pasted in.

BG Clear handles the first two automatically. The shadow you have to add yourself, and a soft 10–20% opacity drop shadow is enough on most images. For scanned signatures for documents, that one detail is what separates "AI cutout" from "studio shot."

Most workflows look like this. The PNG goes into a brand-asset folder (Dropbox, Drive, Notion, whatever). For the immediate use case, you flatten onto white, brand color, or a photo, and export to JPG at the size your destination needs. For scanned signatures for documents, that destination is wherever the final asset lives most of the time.

A tip that saves a lot of time: name the file with the subject and the date, not the use case. "logo-2026-04.png" travels well. "logo-for-website-header.png" doesn't, because three months later you'll need it for a slide deck and re-search the folder.

The browser flow works great up to maybe 50 images a day. Past that, the click-upload-wait-download loop adds up. For lawyers, founders and HR teams running scanned signatures for documents at scale, the next step is the background removal API — same model, but you POST an image and get a transparent PNG back in JSON.

The practical signal: if you're keeping ten browser tabs open to parallelize uploads, switch to the API. The tipping point is usually around 100 images a day.