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.
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.
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.
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.
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.
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.
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.
Export current values and check whether expected fields were completed. Review the PDF itself as well; the data export is not a visual rendering.
Import checked JSON into another copy with the same field identifiers. Confirm the field types and choices before assuming similar-looking forms are compatible.
Open the CSV to compare field names and values. Remember that multiple selections are represented as joined text rather than separate spreadsheet columns.
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.
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.
Open another Fylvexa tool that works well with this task.
To enter values directly into existing supported form fields, use Fill PDF Forms and inspect the saved field appearances.