Filled PDF forms in. One spreadsheet out.
Drop a stack of the same filled form - registrations, applications, W-9s - and get one row per form, one column per field. Free, no signup.
Carbon copy → grid
Drop your filled forms - one row appears per form
Filled PDF forms, plus .fdf and .xfdf exports. Up to 200MB each.
Digital forms are read in your browser and never uploaded.
No forms at hand?
Riverbend 10K registrations
6 digital forms
Vendor tax forms
5 forms, one scanned
Fifty filled forms, one comparison table
The forms come back one at a time - a registration here, an application there - and the real task is lining all of them up side by side. One row per form, one column per field, so you can sort, filter, and compare.
Ops and events
Customers email back filled registration and intake forms all week; the answers need to become rows in one sheet.
Grant and admissions review
Dozens of applications with the same questions - the answers belong in a grid so reviewers can compare across candidates.
AP and finance
Vendor W-9s arriving for onboarding: legal name, TIN, and entity type into the vendor master and 1099 prep.
Fictional samples, free to reuse: Whitfield (PDF) · Raman (PDF) · Alvarado (PDF) · Osei (PDF)
One grid, even when the forms don't match
Mismatched field sets, a malformed file in the batch, a hundred forms at once, scanned forms with no digital fields left - here is how each one is handled.
Situation
This tool
Acrobat Pro
Forms with different fields
Handled - columns are the union of every field seen
Every form must have the exact same fields
One unreadable file in the batch
Becomes an error row; the rest keep going
One bad file can abort the whole export
Around a hundred forms at once
Digital forms are read in your browser, so the batch is effectively uncapped
Users report crashes and empty (0-byte) CSVs near 100 files
Scanned or flattened forms
Falls back to reading the page image when there are no digital fields
Digital form fields only
Where it runs
Digital forms never leave your browser
Desktop app, buried in Prepare Form mode
Price
Free, no signup
A paid Acrobat Pro subscription (around $20 to $30 a month)
Drop the forms, get the spreadsheet
No Power Automate flow, no Python script with a PDF library, no recorded Acrobat action - drop the forms here and the fields land in a spreadsheet. When it is a recurring job rather than a one-off, that is what a DocuPipe workflow is for.
Digital forms never leave your browser
A filled PDF form stores its answers in a form layer this page reads with your browser's own PDF engine - no upload, which you can verify in your network tab. Only a scanned or flattened form, which has no digital fields left to read, is uploaded, and only after you switch that on.
From the blog
Your browser can read a filled PDF form
A raw filled registration form, the grid it became, and why the batch never has to leave your machine.
Read the postQuestions people ask about form data
Yes. This runs in a browser tab with nothing to install and no subscription. Acrobat Pro hides the same job inside Prepare Form mode and charges for it; here you drop the forms and get the spreadsheet.
Yes - that is the whole point. Each filled form is one row, and the columns are the union of every field name seen across all your forms, so nothing gets dropped even when the forms are not identical.
Excel's Get Data reads visible page tables, not the values typed into form fields. A fillable form stores its answers in the form layer, which Get Data ignores - so you get the blank template text back, not the filled-in answers. This tool reads the form layer directly.
It requires every form to have the exact same fields, chokes when one file in the batch is malformed, and users report crashes and 0-byte CSV files once the batch gets near a hundred forms. Here a bad file becomes a single error row and the rest of the batch finishes.
Yes. If you already exported form data from Acrobat as a .fdf or .xfdf file, drop it here and each field lands in the grid. Those files are parsed in your browser and never uploaded.
When a form has no fillable fields left - it was printed and scanned, or flattened on save - turn on "Read scanned & flattened forms" and that file is read on our servers instead. Those are capped at ten per run; digital forms stay unlimited.
A checkbox becomes Yes or No. A radio group or dropdown becomes the option that was selected. Multi-select lists become the selected options joined together. Each lands in its own column.
No. Forms with different field sets are merged into one grid as a union of columns - a field only some forms have simply stays blank on the rows that do not have it. Acrobat requires identical forms; this does not.
Digital PDF forms and .fdf/.xfdf files are read entirely in your browser and never leave your machine - you can confirm it in your network tab. Only scanned or flattened forms are uploaded, and only after you turn that on.
Digital forms are read locally, so the batch is effectively uncapped - a soft limit of about a hundred keeps the page responsive. Scanned or flattened forms are limited to ten per run and 200MB per file.
Yes. A DocuPipe workflow runs the same extraction on every form that lands - by email, API, or folder sync - and appends each one to a spreadsheet or your own system automatically.
Run it at scale
Forms arrive every day.
DocuPipe runs this same extraction on every form that comes in - by email, API, or folder sync - and delivers each one to your spreadsheet or system, no drag-and-drop required.
Free tier included. Takes about a minute to set up.
SOC 2 certified · ISO 27001 · HIPAA compliant · Encrypted in transit and at rest · Never used to train models