Approaches compared

Step by step — build the mailto: submit PDF form

1. Author the form layout in Word, InDesign, or Acrobat. Add fields for the data you want to collect: text, checkboxes, dropdowns, dates.
2. Open in Acrobat Pro. Tools → Prepare Form. Acrobat detects form fields automatically and lets you adjust their properties.
3. Add a Submit button. Drag a button onto the form. Right-click → Properties → Actions → Add Action → "Submit a form". URL: `mailto:your@email.com`. Export format: FDF.
4. Add instructions text below the button: "Click Submit to email your answers. If submit does not open your mail client, save the file and email to <your address>."
5. Test end-to-end by filling the form in Acrobat Reader and clicking Submit. Confirm your mail client opens with the FDF attached. Test also in Acrobat Mobile and the most-common browser viewer to know the failure modes.

Receiving and parsing the submitted data

FDF arrives in your inbox as an .fdf email attachment. Two paths to use it. First, import back into the original form: open the empty form in Acrobat Pro, File → Import → Form Data, select the FDF, the form populates with the user's answers. For one-off review, this is fast. Second, parse programmatically: a small Node.js or Python script reads each FDF attachment, extracts the field/value pairs, appends to a spreadsheet or database. For recurring submissions, the script-based path automates the data aggregation; without it, FDF processing is manual.

For organisations expecting more than a handful of submissions per month, the FDF email-based workflow does not scale — the manual import step becomes the bottleneck. Switch to a real form platform (Google Forms, JotForm, Typeform) that aggregates submissions automatically. The PDF mailto: workflow is a good stopgap for low-volume scenarios and a fallback when corporate IT prohibits third-party form services.

Privacy considerations for PDF form data

FDF submissions carry whatever the user typed — including potentially sensitive information (SSN, payment data, health info). Treat the inbox receiving FDFs as you would treat a database of the same data: access-controlled, encrypted at rest, retained only as long as needed, deleted when no longer required. For GDPR-regulated processing (EU recipients filling EU residents' data), the lawful basis for collection and retention period must be documented; FDF in a personal email inbox is generally not a defensible setup for any volume of sensitive data. For PII-bearing forms, either move to a real form platform with appropriate data-processing terms or implement an IT-managed mailbox with retention and access controls.

Related reading

• Create a fillable PDF: form design fundamentals.
• Send a contract for e-signature: when signing is the form interaction.
• PDF compatibility: which viewers support form actions.
• PDF for HR: form workflows in onboarding contexts.
• PDF Pro vs free: form design is genuinely Pro territory.

FAQ

How does the PDF mailto: action work?

A PDF form can include a submit button configured with the mailto: action. When clicked, the recipient's default mail client opens with a new message addressed to your email, with the form data attached as FDF (Forms Data Format) or the full filled PDF. The recipient hits Send, you receive the data. The advantage: no server infrastructure needed — the PDF itself drives the submission. The constraint: the recipient must have a configured mail client (most desktop users do; many mobile users do not), and PDFs opened in browsers may not honour the mailto: action. Reliability varies by recipient setup.

How do I set up the mailto: action in Acrobat Pro?

Open the PDF in Acrobat Pro. Tools → Prepare Form. Add a button to the form. Right-click the button → Properties → Actions tab → Add Action → "Submit a form". Set URL field to `mailto:your@email.com`. Configure Export Format: FDF (just form data, smaller), PDF (entire filled PDF), or HTML (web-form-style). Save. Test by filling the form in Acrobat Reader and clicking submit — the mail client should open with your data attached.

Why does the submit button do nothing when the user clicks it in their browser?

Browser-based PDF viewers (Chrome, Edge, Firefox, Safari built-in) deliberately do not execute PDF form actions for security reasons. The mailto: action only works in dedicated PDF readers (Acrobat Reader, Foxit, PDF Expert). For broad-audience forms, this is a significant limitation — many users now open PDFs in browsers by default. Workarounds: provide both a submit button and clear text instructions ("If submit does not work, save this PDF and email to..."); or accept the limitation and use a web form (Google Forms, Typeform) instead of a PDF form.

Is the FDF format readable, or do I need a tool to open the submitted data?

FDF is a text-based format that any PDF reader can import back into the form it came from — open the original empty form, File → Import → Form Data, select the FDF, the form populates with the user's submitted values. For programmatic processing, FDF parses with libraries like pdf-lib (JavaScript), PyPDF2 (Python), or qpdf (command line). For one-off processing, importing back into the empty form is fastest. For high-volume submission collection, parse FDF programmatically into a spreadsheet or database.

When should I use a real form platform instead of a PDF form?

Five signals to switch. First, more than ~10 submissions per month — the manual FDF processing gets tedious. Second, mobile recipients common — browser-based PDF viewers do not honour submit actions. Third, complex conditional logic (fields appear based on prior answers) — PDF JavaScript handles this but with limits; web forms do it natively. Fourth, file upload required (resume, photo) — PDF forms cannot accept file attachments. Fifth, you want data aggregation and analytics — Google Forms, Typeform, JotForm provide dashboards out of the box. For simple one-off PDF forms with desktop recipients, the mailto: action remains a serverless solution worth knowing.

Citations

1. ISO 32000-1:2008 — "Document management — Portable document format" — §12.7 (Interactive Forms).
2. Adobe — FDF specification documentation.
3. RFC 6068 — "mailto:" URI scheme specification.
4. Adobe Acrobat Pro — Prepare Form feature documentation.