Sign a Contract and Return It

A contract you must sign and return is one job with four steps: read every page, fill the blanks, apply a signature the other side can rely on, and return the file. The same document travels through all four — so each step is safer when it happens in your own browser, and the one step that genuinely needs a server is the one that earns its keep.

Step 1: Read Every Page Before You Sign

Signing means you saw it. open a PDF in your browser — nothing uploaded, free — and walk the document page by page, not just the signature page. The clause nobody reads is always the one that costs money later: the auto-renewal, the indemnity, the jurisdiction clause. A local viewer is also the right place to check that the file is the final version, not an earlier draft that kept circulating.

Step 2: Fill the Blanks

fill a PDF form — in your browser, free. Fill every field the counterparty expects; empty fields are the most common reason a signature gets rejected on arrival.

Step 3: Apply the Signature

There are two kinds, and the difference is one of trust, not quality:

• A simple signature — sign a PDF, running in your browser, free, no upload — places your signature on the page. It is what most everyday agreements need.
• A qualified signature — sign a PDF with a digital certificate — runs PAdES signing on PDFLean’s encrypted cloud path and uses plan quota. This is the version a counterparty or a regulator asks for when the signature itself has to carry evidence: who signed, when, and that the document did not change afterward.

Which one you need is set by the counterparty or the jurisdiction, not by the file.

Step 4: Return It With the Values Intact

Before you send the signed file back, flatten a PDF — in your browser, free — if it contains form fields you filled. Flattening bakes the values into the pages, so the signature and the values display in any viewer the counterparty uses, including the ones that ignore form fields.

Verify Before You Return

Open the finished file and check that the signature appears where it belongs, that every filled value still shows, and — for a qualified signature — that the signature panel reports your certificate and the document as unmodified.

Frequently Asked Questions

Do I need an account? The reading, filling, simple signing, and flattening steps run in your browser with no account. The qualified PAdES signing step runs on the encrypted cloud path, which needs an account and uses plan quota.

Does PDFLean keep a copy of my contract? The browser steps never upload anything, so there is nothing to keep. For the cloud signing step, the file travels over an encrypted connection and the output is kept for the site’s one retention window and then automatically deleted — the retention rule applies to every cloud output, signing included.

Can I sign a scanned contract? You can place a signature on any page, but a scan has no text layer, so neither side can search or verify the underlying text. Run OCR a PDF first — on-device recognition, free, no upload — if the file needs to be searchable.

---

Signing and returning a contract is a sequence, and each step protects a different thing: reading protects you, filling protects the process, the signature protects the agreement, and flattening protects what the other side actually sees. Keep all four in the browser except the one step — qualified signing — where the server earns its place.

Do It Directly

Ready to sign and return the file in front of you? open a PDF in your browser and read it page by page, fill a PDF form the blanks, then sign a PDF — all in your browser, free, no upload. Where the counterparty requires a qualified signature, sign a PDF with a digital certificate runs PAdES on the encrypted cloud path, and flatten a PDF locks the values before you return it.

Related reading

• Collect Signed Consents — the other side of the same job: building a form many people sign and return
• Redact an SSN From a PDF — contract packets often carry ID numbers; remove them before you share
• How Long Are My Files Kept? — the one retention rule behind the encrypted cloud signing step