On this page
Confirm that the PDF is interactive
A real PDF form stores named controls such as text fields, checkboxes, radio groups and dropdowns. Clicking a printed line in a flat PDF does not make it interactive.
A form studio should detect fields before asking for responses. If none are found, the document may be flat, scanned or built with unsupported XFA technology.
Complete fields against the original page
Use the page preview to understand the label, surrounding instructions and relationship between controls. A field navigator is useful for long forms, but it should remain synchronized with the visible document.
Move through required fields deliberately. Radio buttons usually allow one choice in a group, while checkboxes can represent independent confirmations.
Save a separate completed copy
Keep the source template unchanged. Export a new file with a recognizable name, then reopen it in the viewer the recipient is likely to use.
Verify dates, identifiers, selections and multiline responses at normal zoom before submitting the document.
- Confirm supported fields
- Complete required responses
- Review every page
- Export a separate copy
- Reopen and verify saved values
Put the workflow into practice
Arrange source documents, select the pages you need, and create one PDF locally in your browser. Review the result before choosing any optional next step.
Try Merge PDFFrequently asked questions
Clear answers before you merge
Why can I not type into some PDFs?
The page may contain printed boxes rather than interactive fields, or it may use unsupported XFA technology.
Will the original PDF be changed?
No. The workflow creates a separate completed copy.
Do saved fields remain editable?
Yes, unless the form is flattened afterward.
Should I flatten before submitting?
Only when the recipient requests a fixed copy and you have preserved an editable version.
