Microsoft Word documents can contain interactive elements like content controls, legacy form fields, and ActiveX controls that behave differently when the document is converted to PDF. A dropdown list that works in Word may become a static text label in the PDF. A date picker control may disappear entirely. Converting Word to PDF while preserving these interactive elements requires specific settings that are not enabled by default in most export workflows. Getting these settings right ensures that forms, templates, and structured documents remain functional after conversion.
Key Takeaways
Word content controls, including rich text fields, dropdown lists, date pickers, and checkboxes, can be preserved as interactive PDF form fields during conversion, but only when the correct export option is selected. Legacy form fields from older Word documents require different handling than modern content controls. The conversion settings that preserve interactive elements are buried one level deeper than the standard Save As PDF option, and many users do not know they exist.
The Difference Between Content Controls and Legacy Form Fields
Content controls were introduced in Word 2007 and are the modern way to add structured, interactive elements to documents. They include rich text boxes, plain text boxes, dropdown lists, date pickers, checkboxes, and repeating sections. Each content control has properties that define its behavior, such as whether it can be deleted, whether it locks after editing, and what placeholder text it displays. When converting to PDF, content controls can be mapped to equivalent PDF form fields, preserving their interactive behavior.
Legacy form fields are an older technology from Word 2003 and earlier. They include text fields, checkboxes, and dropdowns, but they lack the properties and styling options of content controls. Word still supports legacy form fields for backward compatibility, and many templates created years ago still use them. When converting a document with legacy fields to PDF, you must enable a different set of conversion options than you would for content controls. A document that mixes both types of fields requires both sets of options to be enabled.
Enabling Interactive Field Preservation During Conversion
Some Word templates use content controls that are linked to custom XML data stored in the document. When these linked controls are converted to PDF, the XML data connection is severed because PDF forms do not support external data binding. The fields become static form fields with their current values baked in. If your workflow relies on XML-linked content controls, you will need to either accept static field values in the PDF or redesign the form to use standard, non-linked content controls before conversion.
The standard Save As PDF command in Word creates a static PDF where all interactive elements are flattened to their current appearance. A dropdown list will show whatever value was selected when the document was saved, and the reader cannot change it. To create a PDF with working form fields, use File, Save As, and select PDF from the format dropdown, but before clicking Save, click the Options button in the Save As dialog. In the Options panel, under the "Include non-printing information" section, check "Create bookmarks using Headings" and, critically, check "Document structure tags for accessibility." Then, under the PDF options, select "Best for printing" and ensure "Bitmap text when fonts may not be embedded" is unchecked.
For content controls specifically, there is an additional setting that is not in the Options dialog. Before saving, go to File, Options, Advanced, and scroll to the "Preserve fidelity when sharing this document" section. Check "Save form data as delimited text file" to ensure that data entered into content controls is preserved in the PDF's data structure. This setting makes the difference between a PDF where form fields look interactive but lose their data when saved, and one where filled-in values are permanently stored in the document. WukongPDF's PDF Forms conversion tool automatically detects Word content controls and legacy fields during upload and preserves them as working PDF form elements without requiring manual option configuration.
What Happens to Each Type of Content Control
Rich text and plain text content controls become editable text fields in the PDF. The field size in the PDF matches the control size in Word. Placeholder text from the Word control becomes the field's tooltip in the PDF. Dropdown list controls become PDF dropdown fields with the same list items. Date picker controls become text fields in the PDF. The date picker calendar interface does not carry over to PDF because PDF form fields do not have a native date picker widget. Checkbox controls become PDF checkbox fields. Picture content controls become static images in the PDF and are not interactive. Repeating section controls are not supported in PDF forms and are either flattened or split into separate fields.
ActiveX controls are a special case. These controls, which include option buttons, spin buttons, and scroll bars, are not standard form elements and do not convert to PDF form fields. They are either rendered as static images of their current state or omitted from the PDF entirely, depending on the conversion settings. If your document relies on ActiveX controls for interactivity, you will need to redesign the form using content controls before converting, or accept that those elements will not be functional in the PDF version.
Testing the Converted PDF Before Distribution
If the form includes calculated fields such as a total that sums the values of other fields, test the calculation in the PDF after conversion. Not all PDF form field calculation scripts survive the Word-to-PDF conversion. Simple arithmetic usually transfers correctly. Complex formulas with conditional logic may need to be re-created in the PDF editor after conversion.
A final verification step that catches subtle issues is to fill out the PDF form completely with test data in every field, save it, close it, and reopen it on a different device or in a different PDF reader. Form data that saves and displays correctly in one reader but not another indicates a compatibility issue with the PDF form field format. Remediating this before distributing the form to hundreds of recipients is far less expensive than dealing with lost form data after the fact.
If the PDF form will be filled out by recipients on mobile devices, test the form on both an iPhone and an Android device before distributing it. Mobile PDF readers vary in their support for interactive form fields. A dropdown list that works perfectly in Adobe Acrobat Reader on desktop may not respond to taps on a mobile device. If mobile compatibility is essential, simplify the form by replacing dropdown lists with text fields wherever possible, as text fields have the broadest compatibility across platforms.
After converting, open the PDF in at least two different readers and test every interactive field. Click into each text field and type a value. Select each dropdown option. Check and uncheck each checkbox. Save the filled form, close it, and reopen it to confirm that the data persists. Pay particular attention to fields near page breaks. A content control that straddles a page break in Word may split into two non-functional fragments in the PDF. If you find split fields, adjust the page break position in the Word document and convert again.
If a field does not work in the PDF, the fastest fix is usually to delete the content control in Word and re-create it, then convert again. Content controls can accumulate formatting artifacts, especially in documents that have been edited by multiple people over a long period. A freshly created content control converts cleanly. An old one that has been copied, pasted, and reformatted many times may carry hidden formatting that interferes with the PDF conversion.
Frequently Asked Questions
Can I add new form fields to the PDF after converting from Word? Yes, most PDF editing tools allow you to add text fields, checkboxes, dropdowns, and signature fields to an existing PDF. This is useful when the Word document contains text labels that should be form fields but were not set up as content controls before conversion. Adding fields directly in the PDF editor is often faster than returning to Word, converting the labels to content controls, and re-exporting.
Why do my Word form fields look different in the PDF?
PDF form fields use the PDF viewer's built-in field rendering, which does not perfectly replicate Word's formatting. Font size, field border style, and background color may shift slightly. This is normal and cannot be completely eliminated. The field data, dropdown values, and checkbox states are preserved correctly even when the visual styling changes.
Can I convert a password-protected Word document to an interactive PDF?
Yes, but you must enter the password to open the document in Word before converting. The resulting PDF will not inherit the Word document's password protection. If you need the PDF to be protected as well, apply PDF security settings after conversion using a separate protection tool.
What is the best format for a Word document that will be converted to an interactive PDF?
Use the DOCX format, not the older DOC format. DOCX stores content controls and their properties in a structured XML format that converts more reliably to PDF form fields. If you have a legacy DOC file with form fields, save it as DOCX first, verify that all fields still work, then convert to PDF.