Convert PDF Form to Excel on Mac: One Row per Filled Form

To convert a PDF form to Excel on a Mac, put every filled copy of the form into one batch and ask for one row per form, with one column per field you need: the respondent’s name, the date, each answer, and the checkboxes as plain values. Export to Excel, then check that the sheet has as many rows as you had forms. If every copy is a fillable PDF and you already pay for Adobe Acrobat, its Merge data files into spreadsheet command reads the field values directly. For anything printed, signed and scanned, flattened or mixed, you need a tool that reads the page.

The Mac app for that second case is ignitai. It reads each page with Apple’s on-device text recognition, and an AI builds the table your plain-English instruction describes. One instruction covers the copy someone filled in on screen, the one they printed, signed and scanned, and the one they photographed with a phone. The page images stay on your Mac; only the recognized text goes to ignitai’s servers, where the spreadsheet is built.

The forms come back in a pile: forty registrations for a training day, a month of client intake forms, every supplier’s new-vendor form. Each holds the same dozen answers, and the usual way to get them into rows is two windows side by side and an afternoon of typing.

In this guide12 sections

Fillable, flattened or scanned: check what you have

Open one form in Preview and click into an answer.

Fillable. The answer sits in a form field you can edit: the cursor appears inside the box. The values live in the PDF’s form data, separate from the printed page, and that form data is what Acrobat’s merge reads.
Flattened. The answer is printed onto the page and can’t be edited. A form goes flat when someone uses Print to PDF, when many systems export it, and often when an e-signature service returns the completed copy.
Scanned or photographed. The form was filled in on paper. The PDF holds a picture of the page, usually with no text layer at all.

A real stack usually holds all three. A merge built on form fields handles the first kind and returns nothing for the other two; reading the page handles all three the same way.

Why a form breaks PDF-to-Excel converters

A converter built for tables looks for a grid. A form doesn’t have one:

Labels and answers sit side by side. “Name:” followed by a line with the answer on it; “Date of birth” above a row of boxes. A grid tool returns labels and answers alternating down two columns, or every line of the page in one column, and one form becomes thirty rows.
One form should be one row. You want form 17 to be row 17, with its answers across. Grid converters work the other way round, page in and rows out, so a three-page form becomes three disconnected fragments.
Checkboxes carry meaning but no words. “Vegetarian ☐ Vegan ☒” holds one fact. A tool that only copies text either drops the tick or turns the row of boxes into noise.
Not every copy is the same revision. Last year’s version put the phone number on page one; this year’s moved it to page two. A template or zone-based extractor needs a new mapping for each revision, and a stack that mixes them breaks it.

Convert PDF forms to Excel on Mac with ignitai

Gather the filled copies. Born-digital and scanned PDFs can go in the same batch. Photos of paper forms run as a batch of their own, because on Mac a drop that mixes PDFs and image files imports only the PDFs. For capture quality on paper copies, see the scanned-PDF walkthrough for Mac.
Drag the forms onto the ignitai window, open them with ⌘O, or right-click them in Finder and choose Open With. Paper forms still on your desk can come in through File ▸ Import from iPhone or iPad, which scans them with your iPhone’s camera.
Describe the row. A prompt is required, so the Convert button stays disabled until you type one. Start from the Form starter or write the instruction out:

“One row per submitted form. Columns: form_date, full_name, organization, email, phone, session, dietary_requirement, needs_parking, signed. Take each value from the answer written next to or under its printed label, never the label itself. For a group of checkboxes, write the label of the ticked box; for yes/no boxes, write yes or no. Leave a cell empty if the form leaves it empty. If a form runs over several pages, keep it on one row. Dates as YYYY-MM-DD.”

Name the columns you need, not every field on the form; a 40-field form rarely needs 40 columns. Save the instruction, and it’s one click away when the next pile arrives.
Check the page count, then Convert. Before the run starts, ignitai shows how many pages it will use and how many you have left. Each file shows its status as the batch runs, and a notification arrives when the spreadsheet is ready.
Check the table in ignitai. Rows are numbered, so the first check is free: forty forms in, forty rows out. If a column came back empty, ignitai says so, which usually means the field name in your instruction doesn’t match the form’s wording. Original Pages keeps every form a click away to compare against.
Export to Excel. Amounts and counts are real numbers in the Excel file, so they total the moment it opens; the header is bold and the columns fit their content. Corrections happen in Excel or Numbers.

There is no filename column. Filenames never leave your Mac, so batch output can’t say which file a row came from. Ask for something printed on every form instead: the respondent’s name, an application or member number, a reference in the header. A returned form with no identifying answer is worth catching anyway.

When the answers live only in the fields. If Original Pages shows a form’s boxes empty while Preview shows the answers, those answers exist only as form data. Make a flat copy first: in Preview choose File ▸ Print, then Save as PDF from the PDF menu, and convert the copy.

Big piles and the page allowance. The plan includes 80 pages a week, up to 320 a month; unused weekly pages don’t carry over. Forty three-page forms is 120 pages, more than a week’s allowance, so read the page count ignitai shows before the run and buy extra pages while subscribed for the rest. Packs run from 5 pages to 1,050, and bought pages never expire. Prove the instruction on one form of four pages or fewer before the full run. If every copy ends with pages of terms and conditions, those pages count too, so leave them out where that’s easy.

Get ignitai on the App Store — free download; your first document (up to 4 pages) converts free with Sign in with Apple, and one subscription covers iPhone, iPad, Mac, and Vision Pro.

Repeating sections: one table per run

Some forms carry a list inside them: an order form with line items, a job application with three previous employers, a claim with several expenses. Each run produces one table, so choose the grain per run:

One row per form for the fixed fields, with the instruction above.
One row per line for the list, with the form’s identifying answer repeated on every row: “One row per item ordered: order_reference, customer_name, item_code, description, quantity, unit_price, line_total. Repeat order_reference and customer_name on every row. Skip empty item lines.”

The shared reference joins the two tables afterwards with XLOOKUP. An order form behaves much like a purchase order once it’s in rows, and the purchase-order guide covers the line-level checks. Expense claim forms are the same pattern again, handled in the expense-report workflow.

Check the sheet before anyone uses it

Row count. Forms in, rows out. A form split across two rows, or two forms merged into one, shows up here first.
Blanks in required fields. Filter each column the form marks as required for empty cells and open those forms in Original Pages. Either the respondent skipped the field or the instruction missed it.
Checkbox columns. A tick is a mark, not a word, so treat checkbox columns as the ones most likely to need correcting. Compare a handful against the original pages before you trust a count built on them.
Duplicates. People submit twice. =COUNTIF(B:B,B2)>1 on the identifying column flags repeat submissions.
Totals. Where a form prints its own total, as order forms and expense claims do, add up its line rows and compare.

What the sheet is for

Registrations and sign-ups. Headcounts by session, dietary counts for the caterer, the parking list, all from one sheet.
Vendor and customer onboarding. Legal name, address, contact and payment terms in columns, ready for the accounting system’s import template. Tax forms with fixed, numbered boxes need box-by-box handling of their own; the W-2 guide shows that approach.
Inspections and checklists. One row per inspection with pass or fail per item; filter for the fails.
Paper surveys. Scan the stack, ask for one row per respondent with ratings as numbers from 1 to 5 and free-text comments in a column of their own, and a pivot gives you the averages.
Applications and intake. A comparison sheet of applicants, or a client list built from the intake forms.

Other ways to get form data into Excel

Export from where the form was collected. If the form ran in Google Forms, Microsoft Forms or Jotform, the responses already exist as data, and each of them exports to a spreadsheet. That’s exact and free.
Acrobat’s Merge data files into spreadsheet. In paid Acrobat, All tools ▸ Prepare a form ▸ Options ▸ Merge data files into spreadsheet takes a set of filled fillable forms and writes their field values into one spreadsheet file, a row per form. The values are exact because nothing is read off the page. The columns carry the form’s internal field names, which can be as unhelpful as “Text7”, and flattened, scanned or photographed copies contribute nothing.
Excel for Mac’s Get Data. Power Query is under Data ▸ Get Data, but Excel for Mac has no From PDF connector; that one is Excel for Windows only. Even on Windows it imports grids, not label-and-answer layouts.
Copy and paste from Preview. One answer at a time, which is the job you were trying to stop doing.
Web PDF converters. They rebuild the page as a grid, so labels and answers come back interleaved, a sheet per form or per page.

The batch mechanics are those of any batch PDF-to-Excel run on Mac: one instruction, one table, every file consolidated.

On iPhone and iPad

iPhone. Paper forms handed in at a desk or an event: scan the stack with the camera in ignitai, tap the saved instruction, and follow progress on the Lock Screen and in the Dynamic Island. A notification arrives when the spreadsheet is ready.
iPad. Forms that arrive by email can be multi-selected in the Files picker or sent from Mail through the share sheet (there’s no external drag-and-drop into the app on iPad). Sort the finished table by any column, then select rows and copy them before you export.

One subscription covers iPhone, iPad, Mac and Vision Pro, and finished files open on your other devices after Sign in with Apple.

Personal data on forms

Forms usually hold personal data: names, addresses, dates of birth, sometimes health details or tax numbers. In this workflow the page images stay on your Mac. The recognized text of every page goes to ignitai’s servers, where the AI builds the sheet, and that includes fields you leave out of the instruction: leaving a column out keeps it out of the spreadsheet, not out of the text. The finished file is stored in your ignitai account until you delete it, and any file, or the whole account, can be deleted from inside the app. That’s less than handing whole files to a web converter, but it isn’t nothing. If the forms fall under HIPAA, GDPR or a client confidentiality agreement, check those terms before converting.

When not to use this

The responses already exist digitally. Export them from the form tool.
Every copy is fillable and you already have Acrobat. Merge them; reading the page adds nothing when the field values are there and the field names are usable.
The answers are handwritten. Handwritten forms are outside what this guide promises, because results depend on the hand. Convert one form first and compare the row with the page before you commit a stack.

Bottom line

To convert a PDF form to Excel on a Mac, drag every filled copy into ignitai together, ask for one row per form with the columns you need, checkboxes as plain values and a field that identifies each respondent, and export to Excel. Fillable, flattened, signed-and-scanned and photographed copies all go through the same instruction; repeating sections get a second run of their own. Then check the sheet against the forms: rows against copies, blanks in required fields, checkbox columns against the original pages. If every form is fillable and Acrobat is already on the Mac, its merge is the exact route. For every other pile, read the page.

FAQ

How do I convert a PDF form to Excel on a Mac?

Put every filled copy in one batch: drag the PDFs onto ignitai, ask for one row per form with one column per field you need, and convert to Excel. The pages are read on your Mac and only the recognized text goes to ignitai’s servers, where the AI builds the sheet. Then check that the sheet has as many rows as you had forms.

How do I extract data from multiple PDF forms into one Excel sheet?

Select all the filled forms and convert them in one batch with the same instruction; the batch comes back as one table, one row per form. There is no filename column, so ask for a field printed on every form, such as the respondent’s name or a reference number, to tell the rows apart. If every form is fillable and you already pay for Acrobat, its Merge data files into spreadsheet command reads the field values directly.

Can I convert a scanned paper form to Excel?

Yes, when the answers are typed or printed. Scan the forms with the camera in ignitai on iPhone, or on a Mac use File ▸ Import from iPhone or iPad, then use the same one-row-per-form instruction. Handwritten answers depend on the hand, so convert one form first (your first document converts free, up to 4 pages) and compare the row with the original page.