What to Check Before Sending a PDF: The Pre-Send Checklist

Most PDF disasters share a shape: nothing was wrong with the document — something was wrong with the file that left. Wrong export, stale draft, a comment balloon from review round two, a signature applied before someone "just compressed it." A two-minute pre-send pass kills all of it.

The checklist

Content (30 seconds)

• ☐Right version. The accepted draft, not the one still named DRAFT_v3.
• ☐Page order and orientation — every page, including the scanned signature page at the end (rotation fix if sideways).
• ☐Readability at 100% zoom — fine print, stamps, table digits. Aggressive compression has victims (quality checks).
• ☐Page count matches what you expect — a stray blank page from a print-area error embarrasses at the worst moment (Excel export traps).

Hidden layers (45 seconds)

• ☐Comments and tracked changes gone — and the accepted state is what you meant.
• ☐Attachments panel empty unless the attachments are deliberate (what rides along).
• ☐Metadata scrubbed — author, producer, timestamps appropriate for the audience (field guide, scrub guide).
• ☐Redactions actually redacted — search-test and selection-test if anything is blacked out (the full suite).

Delivery (45 seconds)

• ☐Size under the destination's limit — undershoot ~10% for portal re-processing; target-size compression takes the number as input.
• ☐Filename is the message you want sent — 2026-09-23_acme-contract_v4.pdf, not Untitled-3 (final).pdf (naming guide).
• ☐If password-protected: the password travels a different channel than the file (protection guide).
• ☐If signed: the signature is the last edit — verify the seal in a second viewer and send that exact file (order of operations).

Run it as a tool, not a memory exercise

Checklists work better when something else holds the list. BytesPDF Check Before Sending is exactly that — a pre-send walkthrough covering size limits, metadata, personal data, page order and redaction risks, running in your browser alongside the tools that fix each finding (Compare Versions to confirm you're sending the right draft, Secure Cleanup for the hidden layers, Compress to Target Size for the limits).

When the destination is a portal

Government, visa and lender portals add their own rejection taxonomy on top — per-file size caps, password policies, scan-quality checks. The destination-by-destination numbers live in the limits hub, and why visa portals reject compressed PDFs covers the legibility line you must not cross.

Contracts and filings: one more rule

For anything signature-bound the checklist compresses into a single ordering law — finalize, clean, size, protect, sign, send — written out once in send a contract as a secure PDF. Break the order and you get the broken-seal dialog; keep it and the file that arrives is exactly the file you approved.