How to Add a Signature Field to a PDF Form

A signature field is a specific PDF form field designed to capture a signature, either an electronic signature drawn or typed in the moment, or a digital signature backed by a cryptographic certificate. Adding one cleanly is the difference between a form recipients can sign and a form they have to print, sign, and re-scan. This guide walks through adding signature fields to a PDF form.

What a signature field actually is

The PDF spec defines a /Sig form field type. When clicked in a compatible reader, it triggers the reader's signing workflow:

• Adobe Acrobat / Reader prompts for a digital ID or asks the user to draw/type/upload a signature
• Other readers (Foxit, PDF-XChange) have similar prompts
• Some readers do not implement signing, in which case the field appears as a placeholder

A filled signature field carries:

• The signature appearance (the visible drawing/text)
• Optionally, a cryptographic signature (if signed digitally) that verifies the signed bytes match what was signed
• Metadata about the signer (name, time, certificate chain for digital signatures)

For background on the broader signing landscape, see digital signatures vs electronic signatures and how to sign a PDF online.

Tools that add signature fields

Adobe Acrobat Pro. Tools → Prepare Form → Add Field → Signature. Click and drag to place.

Foxit PDF Editor. Form → Add Form Fields → Digital Signature Field.

PDF-XChange Editor. Form → Add Signature Field.

LibreOffice. Limited signature field support; better through dedicated PDF tools.

Browser-based. Docento.app supports placing signature fields in the browser.

Programmatic. PDFKit, iText, pikepdf with low-level field manipulation support signature field creation. Useful for templated forms.

Step-by-step in Acrobat Pro

1. Open the form
2. Tools → Prepare Form
3. Click the Signature Field tool
4. Click and drag where the signature should appear
5. Properties dialog opens
6. General tab:
   • Name: meaningful internal name (customer_signature, witness_signature)
   • Tooltip: text for accessibility ("Customer signature")
7. Signed tab:
   • Nothing happens when signed, most common
   • Mark as read-only: All fields, locks the entire form after signing
   • Mark as read-only: Specific fields, locks specific fields
   • This script executes when field is signed:, custom JavaScript
8. Appearance tab:
   • Border, fill, font choices
   • Usually a subtle border so the field is visible but does not dominate
9. Close

Where to place signature fields

Standard layout conventions:

• Bottom right of the document, for primary signatures
• Two fields (signer + witness) side by side for documents requiring witness signatures
• Multiple fields through the document where each section requires acknowledgment
• Centered at the end for simple sign-here documents

The field's bounding box should be roughly the size of a typed name plus a small drawing, around 200 × 60 points (2.8 × 0.83 inches) is a common default.

Including the signature date

It is conventional to have a date next to the signature. Two approaches:

1. A separate date field (text or date) the signer fills manually. Pre-populate with the current date if possible.
2. An auto-populated date that fills when the signature is added. Use the signature field's "Sign" JavaScript event to populate.

For digital signatures, the signing time is stored cryptographically in the signature object, the visible date is for human readability.

Read-only after signing

A common pattern: when the customer signs, lock everything else so they cannot edit after.

In Signature Properties → Signed tab:

• Mark as read-only: All fields except these → check the fields the signer can still edit (typically none)
• Mark as read-only: Just these → check the specific fields you want locked

For a form where multiple parties sign sequentially:

• Signer A's signature locks the seller's fields but not the buyer's
• Signer B's signature locks everything

Plan the locking workflow before building the form.

Lock specific fields, not the whole document

A signature can lock specific fields rather than the entire form:

• The customer fills personal information
• The customer signs
• After signing, the personal information fields are locked
• The reviewer can still edit the "Approval" field elsewhere on the form

This pattern is common in approval workflows. Set the locking behavior in Signed tab → Mark as read-only: Specific fields.

Multiple signature fields

Forms requiring multiple signers:

1. Add one signature field per signer
2. Name them clearly: signer_customer, signer_witness, signer_company_rep
3. Set tooltips that match the visible label
4. Plan the order, does signer A need to sign before signer B can?
5. If sequential signing is required, lock fields between signatures so signer B sees what signer A agreed to

For a counter-signed contract:

• Customer signs first → locks the customer-side fields
• Company representative signs second → locks the company-side fields
• Both signatures are part of the final document

Visible vs invisible signatures

The signature field can have:

• A visible signature, the field shows the signer's name, drawing, date, etc.
• An invisible signature, the cryptographic signature is in the file but no visible signature appears on the page

Most legal documents use visible signatures. Some compliance workflows prefer invisible signatures (the signature is verifiable but not visually present). The PDF spec supports both.

For signature appearance customization (logo + name + date format), use the signer's identity in their reader; tools like Acrobat have a "signature appearance" gallery the user can pick from when signing.

Validating signatures after they are placed

Once a signature is added, anyone opening the file can verify it:

• Acrobat: clicks the signature, sees who signed, when, and whether the document has changed since
• Other readers: similar UX

If the document is modified after signing, the signature is marked as invalid in the reader. This is the security feature of digital signatures, tampering is detectable.

For more on detection, see how to detect tampered PDFs and certified PDFs explained.

Certified vs signed

A signed PDF carries a signature on a field. A certified PDF is signed at the document level (one signature for the whole file) with strict rules about what modifications are allowed afterward:

• No changes (form filling locked)
• Form filling allowed (signature stays valid after form fills)
• Form filling and annotations allowed

Use certification when you are the originator of a template and want to allow controlled modifications by recipients. See certified PDFs explained for the deeper concept.

Common gotchas

Field placed but signer cannot click. The field is below another element. Bring to front in Form Editing mode.

Signature placed but does not save. Some browser-based PDF viewers do not support saving signed forms. Recipients must use a real PDF reader for signing.

Field name conflicts. Two signature fields with the same name behave as one. Use distinct names.

Required attribute. Setting "Required" on a signature field means the form cannot be submitted without it. Combined with submit JavaScript, this enforces the signature.

Visual appearance varies by reader. A signature drawn in Acrobat looks one way; the same signature in Foxit may look slightly different. The cryptographic signature is the same; the visible appearance is the reader's interpretation.

Tagging for accessibility. Signature fields need a tooltip describing what the user is signing. Screen-reader users cannot see the visual context. See PDF/UA accessibility standard explained.

Mobile signing. Adobe Acrobat Reader mobile and most major iOS / Android PDF apps support signature fields. Verify in the readers your audience uses.

Form data without a signature. A form submitted with signature missing should be flagged. Use submit-time JavaScript to check that the signature field has a value.

Practical recipe

For a simple customer-signs-here form:

1. Open the PDF in Acrobat Pro / Docento.app
2. Tools → Prepare Form
3. Add a signature field near the bottom right
4. Name it customer_signature
5. Tooltip: "Customer signature"
6. Properties → Signed tab → Mark as read-only: All fields
7. Add a text or date field next to it for the signature date
8. Add a "Submit" button if applicable
9. Save the form

Distribute to the customer. They sign in their reader; the form locks; they save and return.

For a counter-signed contract (two parties):

1. Two signature fields: signer_party_a, signer_party_b
2. Each marked to lock its respective party's fields when signed
3. Party A signs first → A's fields lock; B can still edit
4. Party B signs second → B's fields lock; document is fully signed
5. Final file has both signatures

Integrating with signing services

For high-volume or compliance-sensitive workflows, dedicated signing services (DocuSign, HelloSign, Adobe Sign, etc.) handle the legal and audit trail:

• Upload the PDF (with or without signature fields)
• Define signer order and field assignments
• The service emails signers, captures signatures, and produces a signed file with an audit trail
• The signed PDF lands back in your hands

For ad-hoc one-off signing, signature fields in a PDF are sufficient. For business-critical workflows with multiple signers and audit requirements, a signing service is worth the cost.

Takeaway

Signature fields turn a PDF form into something signers can complete entirely in their reader, without printing. Plan field placement, locking behavior, and signer order before adding fields. Acrobat Pro, Foxit, and Docento.app all support placing signature fields. For the legal context, see is it legal to sign documents electronically and e-signature laws around the world; for the technical mechanics, see digital signatures vs electronic signatures. For end-to-end signing workflows beyond simple field placement, consider whether a dedicated signing service fits your compliance needs.