Preview, Validation, and Export
Use this page after your PDF and CSV are loaded and your overlays are mapped. Preview is the fastest way to catch placement problems, blank data, header-row mistakes, and overflow before a larger export run.
If you are validating supported native PDF form fields, also read Work with native PDF forms (AcroForm).
Why Preview Matters
One correct row is not enough. Bulk Fill can only show you the real output for the row you are inspecting, so preview is where you confirm the configured layout still holds up across short values, long values, blanks, and edge cases.
What To Check In Preview
When you move through rows in the Data tab, confirm all of these:
- the value appears in the correct location
- the text field is not blank unless the source cell is blank on purpose
- long text still fits the available space
- dates, amounts, and labels look readable
- mapped QR and barcode overlays render for the rows that should contain them
- native dropdown fields choose the expected visible option text
- native radio groups choose the expected option token
- any header row is handled the way you expect
If row 1 contains headers for your own reference, preview will show those headers as data. That is expected under the current contract.
Mapped QR and barcode overlays are resolved from the current row only. If the row has a blank or invalid value for that code format, Bulk Fill skips that overlay for that row instead of failing the whole row preview or export.
Validate Native PDF Form Output
If the current PDF uses supported native form fields, validate those fields as their own checklist before you trust the batch:
- confirm text appears in the intended native field
- confirm each checkbox reflects the intended checked or unchecked state
- confirm each dropdown resolves to the intended visible option
- confirm each radio group resolves to the intended option token
- review any native-field warnings before you export the full batch
- confirm whether Flatten form fields should be enabled for the final output
This is the point where native form fill starts to feel operationally complete. Treat it like a real output review step, not a minor UI detail.
Recommended Validation Workflow
- Preview one normal sample row.
- Preview one row with longer or less predictable values.
- Preview any row that contains blanks or unusual formatting.
- Confirm whether row 1 is real data or a header row you plan to exclude.
- Export one preview PDF before the full batch.
If you use mapped QR or barcode overlays, include at least one row where the code should render and one row where the input is blank or malformed so you can confirm the skip behavior is acceptable.
If you use native dropdown mappings, include:
- one row whose CSV value exactly matches a visible dropdown option
- one row with a blank CSV value if blanks matter in your workflow
- one row with a value that should fall back to editable text, if the PDF dropdown itself is editable
If you use native radio mappings, include:
- one row whose CSV value exactly matches a radio option token
- one row with a blank CSV value if clearing the group matters in your workflow
- one row with a value that should warn and skip because it does not match any radio option token
If you use native checkbox mappings, include:
- one row that should check the box
- one row that should leave it unchecked
- one row with an invalid token if you want to confirm the warning path before the full batch
Export Options To Review
Before you export, review the options that affect output:
- In the Export tab:
- Flatten form fields: turns editable PDF form fields into static content on supported non-XFA PDFs
- In the More menu:
- Include stickers: keeps sticker overlays in the output
- Include signer details: adds signer details when available
Validate these settings before you trust the batch.
If Bulk Fill shows an XFA notice when the PDF opens, native form fill is not
available for that PDF. You can still export overlay Fields, text, QR codes,
and barcodes, but Flatten form fields stays unavailable for that XFA
document.
Export Preview Vs Export Batch
Export preview
Use Export preview when you want one output PDF for the current row. This is the safest first check before a large run.
Mapped QR and barcode overlays only export in preview when a current row is selected and that row resolves to a valid value.
Native dropdown mappings follow the same row-safe model as other native PDF fields. A non-editable dropdown with an unmatched non-blank CSV value warns and skips that field, while a blank CSV value without a blank visible option is a silent no-op.
Native radio mappings also follow the same row-safe model. A blank CSV value clears the radio group, while a non-blank unmatched value warns and skips that field.
Export batch
Use Export batch when the preview looks correct and you are ready to process multiple rows. You can export:
- all rows
- a range of rows
- specific picked rows
The Batch Export modal also includes a collapsed Custom filename (optional)
section. Open it when you want to choose up to 3 CSV columns to add after the
row number in each exported PDF filename. Each menu and the sample filename
preview follow the current preview row, so options read like Column 1: Carter and the sample filename updates as you move between rows. This is
optional and helps downstream file naming and organization while keeping the
existing row prefix on every exported PDF.
If your CSV includes a header row, use a range that starts at row 2 or leave row 1 out of the selected rows.
Rows with blank or invalid mapped QR/barcode values can still export as partial results when the rest of the row is valid.
Rows with native dropdown or radio mismatches can also export as partial results. The warning summary in preview, batch export, or public manifests tells you which native field needs review.
What Happens After Export
Smaller exports usually start downloading right away. Larger exports may switch to a time-limited download link. Either way, you should still validate a few outputs after the export starts.
If Exported Results Do Not Match Preview
Go back in this order: