Skip to main content

Private browser tool

PDF Form Data Export

Export PDF form data from existing interactive fields to JSON or CSV. You can also import a JSON object keyed by field name and save an updated PDF; this workflow does not extract answers from a scanned form.

Preparing the interactive workspace…

Your document processing stays in your browser.

Read and update existing interactive field values

Move PDF form answers into a structured local file

An interactive form stores field identifiers and values separately from the page artwork. This tool reads supported fields so you can inspect their answers or reuse a carefully prepared set of values. Field names must match when importing JSON. It is a form-data workflow, rather than OCR, field creation or a visual document editor.

1

Open the interactive PDF

Choose an unlocked PDF with existing fields. Review the field list and types; a printed-looking blank box in a scan is not necessarily an interactive field.

2

Export the current values

Download JSON for a field-name-to-value object or CSV for field, type and value columns. Multiple selections are joined in the CSV; keep JSON when preserving their array structure matters.

3

Prepare matching JSON updates

Use the original field names as keys. Keep checkbox values as JSON booleans and multi-select values as arrays. Unknown names are ignored and omitted fields retain their current values.

4

Save and review the PDF

Import the JSON object, inspect the controls and save the updated document. Check important answers in a PDF reader because unsupported or invalid field updates can be skipped.

Formats, limits and tradeoffs

Accepts one PDF up to 150 MiB. There is no explicit page-count cap. Supported values include text, checkboxes, dropdowns, option lists and radio selections; unsupported field types may have no exported value.

Import accepts a JSON object, not CSV, FDF or XFDF. It updates existing identifiers and does not rename fields, create new fields or flatten the result. Standard-font appearance generation can limit non-Latin text.

When this tool helps

Inspect answers before a handoff

Export current values and check whether expected fields were completed. Review the PDF itself as well; the data export is not a visual rendering.

Reuse a matching form layout

Import checked JSON into another copy with the same field identifiers. Confirm the field types and choices before assuming similar-looking forms are compatible.

Review data in a spreadsheet

Open the CSV to compare field names and values. Remember that multiple selections are represented as joined text rather than separate spreadsheet columns.

Troubleshooting

My JSON values did not appear
Check exact field names, valid choices and value types. Unknown keys do not create fields, and individual updates can be skipped when a PDF field rejects them.
A checkbox stayed checked
Use the JSON boolean false to clear it. A text string such as "false" is a different value and can be interpreted as truthy.
Privacy

Process on your device

The browser reads fields, applies JSON values and creates downloads locally. PDF bytes and form answers are not uploaded for processing. Exported answer files contain the data you chose to save.

Browser-first
Browser workflow
No desktop app
Frequently asked questions

PDF Form Data Export FAQ

Select a question to view the answer.

No. A scan needs OCR or manual transcription; this tool reads existing interactive fields.

The current import workflow accepts a JSON object only.

No. JSON keys must match existing field names; unknown names are ignored.

This workflow does not intentionally flatten them. Verify the saved copy in the PDF reader used by your recipient.