Batch fill PDF forms without turning documents into cloud records
A batch is valuable only when failures are visible. FormBatch Local validates the template, fills each row separately, keeps recoverable failures from stopping other rows, and includes a row report in the ZIP.
The free workflow generates the first PDF. Batch export is a $9 one-time downloadable build, not a subscription.
Generate a free preview →What the ZIP contains
Every successful row becomes a PDF named from the chosen recipe. formbatch-report.csv lists the source row number, output filename, completion status, and a diagnostic message for failed rows. It does not copy the source row's values.
Why rows are isolated
A dropdown may contain an unavailable choice, a checkbox may have an ambiguous value, or the form font may lack a character. One failure should not discard 99 valid documents. The batch records the problem and continues.
Memory guardrails
Browser-local work removes upload and storage costs, but the browser still holds generated files before creating the ZIP. Each batch therefore supports at most 500 rows and an estimated 250 MB of source-PDF multiplication. These are safety limits, not billing meters.
Good batch inputs
- A final AcroForm template with stable field names.
- UTF-8 CSV with unique headers and one output record per row.
- Dropdown and radio values that match the PDF's actual options.
- A filename recipe containing a stable identifier, not only a person's name.
Bad batch inputs
- Scans, flattened pages, XFA, encrypted PDFs, or documents needing signatures.
- Data that requires calculation, interpretation, translation, or OCR.
- Unreviewed sensitive exports on a shared computer.