AcroForm Text Field Flags Form Data (XFDF)
XFDF twin of the acro-text-field-flags form data - the same field names and values as the FDF, in Adobe's XML representation. Convert one into the other and the result must be byte-comparable field for field.
<?xml version="1.0" encoding="UTF-8"?>
<xfdf xmlns="http://ns.adobe.com/xfdf/" xml:space="preserve">
<f href="acro-text-field-flags.pdf"/>
<fields>
<field name="plain_text"><value>Ordinary single-line field</value></field>
<field name="comb_reference"><value>AB123456</value></field>
<field name="multiline_notes"><value>First line of the sample note. Second line.</value></field>
<field name="masked_value"><value></value></field>
<field name="locked_value"><value>LOCKED-SAMPLE-1</value></field>
<field name="max_length"><value>SAMPLE</value></field>
</fields>
</xfdf>
Specifications
- Format
- XFDF (XML forms data)
- Bound To
- acro-text-field-flags.pdf
- Fields
- 6
- Checkbox Encoding
- Yes / Off
What is a .xfdf file?
XFDF (XML Forms Data Format) is the XML representation of PDF form data — the modern, human-readable successor to binary FDF. It records each field name and value as XML elements and references the source PDF, making it easy to generate, diff, and transform with standard XML tooling. It is widely used to pre-fill and extract data from AcroForm PDFs.
How to use this file
Use an example XFDF to test XML-based PDF form-data import/export, pre-filling AcroForms from a server, and parsing form submissions with ordinary XML libraries.
How to use this file for testing
“AcroForm Text Field Flags Form Data (XFDF)” is a deterministic Novus Examples fixture for Form testing, PDF form filling, AcroForm, Form parsing. HTML and PDF form files for testing scrapers, autofill, validators, and PDF form fillers across real-life use cases.
Documented properties for this file: 6 fields · XFDF (XML forms data). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
This form is fictional SAMPLE content for tooling tests (autofill, scrapers, PDF fillers). It is not an official government, bank, or clinic form. Open the HTML offline or fill the PDF in any viewer; the demo submit path never stores data.
Related files
- htmlConsent Form Template (HTML, SAMPLE)A minimal fictional marketing-consent HTML form — for privacy UX and scraper tests.
- pdfFillable Form (AcroForm)A one-page PDF with a six-field AcroForm (full_name, email, phone, date, subject, comments) — a fixture for testing form fillers, parsers, and field extraction.
- csvPayment Test Cards (CSV)A reference list of well-known payment TEST card numbers (Visa, Mastercard, Amex, Discover, JCB, Diners) with sample CVV and expiry. These are published test values that pass the Luhn check but are not real accounts — for testing payment forms and card validators. Never use real card data.
- pdfSignature Block PDF (fillable)A one-page agreement with a signature line and fillable AcroForm fields for the signer's name and date. A fixture for testing form-field detection, filling, and signature-workflow tooling.
Generated by generation/forms_p7.py. Free for any use, no attribution required — license.