How to sign a PDF without printing and scanning

There is a small, widespread workflow tax people pay every time they receive a PDF that needs a signature. The routine goes something like this:

Download the PDF from your email
Find a printer that works
Print the PDF (usually after wrestling with paper jams)
Sign it with a pen
Walk to the scanner or use your phone’s camera
Scan it — and re-export as PDF
Email the scan back

On a good day that’s twenty minutes. On a day when the printer is out of toner, it’s a quest.

You do not have to do any of that. A signed PDF does not legally require a wet-ink signature in most jurisdictions. An electronic signature — a signature created digitally and embedded into the PDF — is recognised by the US ESIGN Act (2000), EU eIDAS, UK, Canadian, and Australian laws for nearly every kind of contract.

Here’s how to skip the print-and-scan loop entirely.

The one-minute version

Open pdf2sign.app/sign in your browser (any browser, any device)
Drop the PDF onto the editor
Draw, type, or upload your signature
Drag it onto the signature line, resize
Click Download

That’s it. The signed PDF lands in your Downloads folder. Reply to the email, attach the signed copy, send.

No printer. No scanner. No 20-megapixel phone photo of an A4 page curling at the corners. No software install. No account.

What about legal validity?

This is the most common hesitation people have about electronic signatures, so it’s worth being specific:

United States — the ESIGN Act of 2000 and state-level UETA adoption treat electronic signatures as legally equivalent to wet-ink signatures for nearly all contracts. The exceptions are narrow (wills, some estate/family matters, some real-estate steps).
European Union — eIDAS Regulation 910/2014 recognises three tiers: simple electronic signature (SES), advanced electronic signature (AES), and qualified electronic signature (QES). An SES — which is what a drawn, typed, or uploaded signature is — is legally admissible for the vast majority of contracts. Some specific documents (certain notarial acts, some real estate) require AES or QES.
United Kingdom — the Electronic Communications Act 2000 and case law treat electronic signatures as valid for most contracts.
Canada — the federal PIPEDA and provincial UECA adoption give electronic signatures legal weight.
Australia — the Electronic Transactions Act 1999 does the same.

For the day-to-day case — freelance agreements, rental forms, consent sheets, NDAs, permission slips, dental-practice intakes, insurance renewal forms — an electronic signature created with a free browser tool is every bit as binding as the paper version.

Why not just use Preview or Adobe Reader?

You can. macOS Preview signs PDFs with its Markup tool. Adobe Reader has a Fill & Sign feature. Edge on Windows has “Add signature.” Each of these works for simple cases. Three practical reasons people reach for a web tool anyway:

Cross-device consistency. You sign a PDF on your Mac, then tomorrow you need to sign a similar one from your phone. The macOS Markup signature doesn’t travel to your iPhone. A browser tool works identically everywhere.
Form-field preservation. Preview and Edge’s signer sometimes strip form fields on save. If the PDF is a fillable form (tax form, insurance questionnaire), that’s a problem. Web signers using pdf-lib preserve fields.
Privacy. macOS stores your saved signature locally, but Adobe Sign uploads your PDF to Adobe’s cloud. If the document is sensitive, you may not want any vendor to have a copy, ever. A browser tool that processes files client-side never uploads them in the first place.

How the browser does it without uploading

The short version: modern browsers can read files from your disk using the File API, render PDF pages to a canvas using pdf.js, capture your pen strokes on the canvas, and embed a PNG into the PDF using pdf-lib — all without making a single network request that carries your file.

You can verify this yourself. Open DevTools → Network in Chrome, Safari, or Firefox. Go to pdf2sign.app/sign. Drop a PDF, sign it, download it. The Network panel shows the initial static assets load, and then silence. No POST, no PUT, no upload. You can even disconnect from the internet after the page loads — the full flow still works offline, because all the code is already on your device.

For the full technical write-up, see the security page.

The realistic flow, end to end

Let’s run through a specific scenario. A freelance client emails you a contract as a PDF attachment:

Receive the email. The PDF is sitting in Gmail/Outlook/Apple Mail as an attachment.
Save the PDF. On desktop, drag the attachment to your desktop (or right-click → Save As). On iPhone, use the share sheet → Save to Files. On Android, tap the download icon.
Open pdf2sign.app/sign. New tab. The editor loads.
Drag the PDF in. The editor renders the first page. Scroll to the signature page if the contract is long.
Create your signature. Three options:
- Draw on the canvas with your trackpad / finger / Apple Pencil / Surface Pen
- Type your name in a handwriting font (Dancing Script, Caveat, Great Vibes, Pacifico)
- Upload a photo of an existing signature on paper
Drag the signature onto the signature line. Resize with the corners. You can also add multiple signatures (initials elsewhere), typed text (the date), or upload any extra image the contract needs.
Click Download. The signed PDF saves to your Downloads folder.
Reply to the email. Drag the signed PDF into your reply. Send.

Elapsed time: under a minute, most of it spent scrolling to the signature page. No printer, no scanner, no cropped phone photo, no 20-minute round trip.

When you should reach for more than a browser signer

Browser-based signing is right for 95% of individual signing needs. For a few specific cases, you want a full e-signature platform like DocuSign or Adobe Sign:

Multi-party contracts. If the other party also needs to sign, and you want the signing to happen in order with a single final audit-trail PDF, use a platform that routes between signers.
Audit trail requirements. Some regulated industries (real estate, healthcare, financial services) require a tamper-evident audit certificate — timestamps, IP addresses, identity verification. Browser tools don’t produce these.
Qualified electronic signatures (EU QES). Notary-equivalent signatures under eIDAS require certificate-based identity verification from a Trust Service Provider. DocuSign and Adobe Sign Advanced offer them; pdf2sign does not.

For everything else — the 95% — a browser tool is the right shape.

The summary

Printing and scanning to sign a PDF is a habit left over from a time when browsers couldn’t handle PDFs. They can now. For almost any document you will sign this year, a free browser signer is faster, greener, and more private than the printer route. Try it once and you won’t go back.