Someone emails you a contract with the classic instruction: print it, sign it, send back a scan. Fifteen minutes, a printer fewer and fewer people own, and a file that comes back degraded. The whole loop can be skipped: the signature goes straight onto the PDF, in tens of seconds — losing nothing, neither in quality nor in practical validity.
What the paper loop actually does to your file
The starting document is clean: selectable text, a few hundred kilobytes. After printing and scanning at 300 DPI, every page becomes a full-format photo: the file balloons to several megabytes, the text is no longer searchable or copyable, and the pages pick up skew, shadows and whatever was on the scanner glass.
The surprising part: that degradation buys nothing legally. The scanned page contains a picture of your signature embedded in a PDF — exactly what a browser signing tool produces, minus the quality loss. What makes a signature acceptable is the intent to sign and the context of the exchange, not whether a piece of paper briefly existed in the middle of the process.
The paths already built into your device
Before any dedicated tool, your system often already knows how:
- Mac: Preview → markup toolbar → Signature. Sign on the trackpad or via your iPhone in Continuity; the signature is reusable.
- Windows: Edge opens PDFs and offers “Draw” / “Text” tools — enough for a quick scribble, less precise for placing a clean signature at an exact spot.
- iPhone / Android: the native markup feature draws with a finger, right on the received file.
Limits of these built-in paths: inconsistent stroke quality, laborious multi-page handling, and on Windows the result stays rough. For per-page initials or a clean signature image, a dedicated tool does better.
The browser path — without upload
The Sign PDF tool opens the document in the browser and builds your signature three ways: freehand drawing (mouse, trackpad, finger on mobile), styled handwritten text, or an imported image (a transparent-background PNG gives the cleanest result). You then place it page by page, at the exact size and position you need.
Everything runs on your device: neither the document nor the signature image is sent anywhere — verifiable in the Network tab. For the full walkthrough, see Sign a PDF locally; for the legal scope, visual signature vs eIDAS.
For a clean signature
- Finger or stylus > mouse: on a phone or trackpad, the stroke is far more natural than with a mouse.
- Reuse an image: photograph a pen signature on white paper, remove the background, import the PNG — an identical result on every document.
- Per-page initials: to sign off a whole contract, reproduce the signature at the same position page after page.
- Flatten before sending: flattening merges the signature into the content layer — the recipient can no longer move or remove it, and the rendering is identical everywhere.
- Keep the unsigned original: a PDF can’t be cleanly “un-signed”.
When a visual signature isn’t enough
A signature placed in a browser is visual: it marks the document with your signature, without identity proof or qualified timestamping. It’s enough for most exchanges — approved quotes, everyday contracts, forms. It’s not enough when the framework requires an advanced or qualified electronic signature, an enforceable evidence file, or regulated delivery: for those, you need an e-signature trust service, and getting a third party to sign remotely requires a managed signing workflow anyway. The full picture in the eIDAS article.
