If you searched this you probably need the answer right now. The quick answer is below, free tools and paid tools that will get one PDF into Excel inside five minutes. But if you are converting PDFs to Excel regularly as part of your workflow, that is a sign of a bigger problem worth solving properly, and the rest of this guide covers what that looks like and what it costs.
For a single PDF, you need the converter, not a pattern. The three options that actually work, in order of effort:
Open Excel. Data tab. Get Data. From File. From PDF. Pick your PDF, choose the table(s) you want, load. Available in Microsoft 365 desktop versions. Good for PDFs with cleanly structured tables. Skip the third-party tool entirely if this works for your PDF.
File. Export To. Spreadsheet. Microsoft Excel Workbook. Save. Best result on PDFs that were created from properly tagged source documents. Adobe is also the best option for scanned PDFs because the OCR engine is genuinely good.
Smallpdf, ILovePDF, and Adobe's own free online converter (Acrobat web) handle one-off conversions for free, with monthly limits before they push you to upgrade. Google Drive plus Google Docs also works: upload the PDF, open with Google Docs, export to Sheets. Decent OCR, free.
Three common causes. First, the PDF was scanned (an image, not a document), so the converter needs OCR; switch to Adobe Acrobat Pro or a web tool with OCR. Second, the table in the PDF is actually a series of text lines with spaces between them; the converter cannot tell where columns end. Open in Adobe Acrobat, use the recognise table tool to mark the structure manually. Third, the PDF has multiple tables on one page; convert one table at a time using the table-selection in Adobe or Excel's Power Query editor.
The interesting question is not how to convert one PDF. It is what to do when "convert PDF to Excel" has become a recurring task on somebody's job description. The pattern shows up in nearly every UK SME.
The bookkeeper converts supplier invoices to Excel to reconcile them. The finance director converts bank statements to Excel for the management pack. The buyer converts supplier price lists to Excel to update the stock system. The compliance officer converts insurer schedules to Excel for the client summary. In each case, the PDF is coming out of one system and the Excel is going into another. The conversion is the bridge.
The bridge is the problem. Every conversion is a chance for errors to creep in: typos in copy-paste, decimals in the wrong place, line items missed. Every conversion is also time, usually 10 to 30 minutes per document. At 20 documents a week, that is a day a week somebody spends converting PDFs. At 100 documents a week, you have a full-time conversion role nobody intentionally hired.
The honest fix is not a better converter. It is an automation that reads the PDF and lands the structured data straight in the destination system, without the Excel intermediate at all. The conversion was a workaround for the lack of integration. Automate the integration and the conversion goes away.
These are illustrative shapes drawn from UK SME workflow patterns. The fixed-quote bands are the real ranges we quote for builds of this shape; the workflows described are the patterns that fit each context.
Profile: a 200-client practice processing 5,000 to 8,000 supplier invoices a month for the book. The bookkeeping team converts the PDFs to Excel as a staging step before posting to Xero or QuickBooks. The shape that fits: a direct PDF-to-accounting-system automation that skips Excel entirely. The deeper guide is PDF data extraction for business. Typical band: £6,000 to £12,000 fixed quote. Expected outcome: 4 to 6 hours a day of conversion time saved across the team.
Profile: quarterly supplier price lists arriving as PDFs. The buying team converts them to Excel, edits the mark-ups, and uploads to the stock system. Each cycle takes 2 to 5 days. The shape that fits: automated price-list ingestion with a human approval step on flagged changes. Typical band: £5,000 to £10,000 fixed quote. Expected outcome: the quarterly cycle turns into hours rather than days.
Profile: policy schedules from a dozen insurers arriving in a dozen formats. Account handlers convert each to Excel to produce client summaries. The shape that fits: direct schedule extraction into the broker management system, removing the Excel step. Typical band: £7,000 to £15,000 fixed quote. Expected outcome: reduces the misreads that cause client-policy mismatches.
Profile: engineering change notices, BOM updates and customer drawings arriving as PDFs. Engineers extract the relevant data into Excel for stock and production systems. The shape that fits: automated extraction into the BOM system, with engineer approval on changes. Typical band: £8,000 to £18,000 fixed quote. Expected outcome: removes the Excel handoff and the version-control errors that follow it.
Profile: property managers processing gas safety certificates, EPCs, deposit protection certificates and contractor invoices. Each one is converted to Excel for the property file and the compliance tracker. The shape that fits: direct extraction into the property management system. Typical band: £6,000 to £14,000 fixed quote. Expected outcome: removes the Excel intermediate and surfaces the expiry-date risks automatically.
| Option | Best for | Real cost |
|---|---|---|
| Excel built-in PDF import, Google Docs OCR | One-off conversion, occasional use | Free |
| Smallpdf, ILovePDF, Adobe online | 5 to 20 conversions per month, single user | £5 to £15 / month |
| Adobe Acrobat Pro | Daily PDF work, OCR needed, single user | £17 / month |
| Docparser, Mindee, Klippa | 50 to 500 same-format PDFs per month, basic integration | £30 to £300 / month |
| Rossum, ABBYY FlexiCapture | 1,000+ varied PDFs per month, enterprise workflow | £600 to £5,000+ / month |
| Custom build with extraction layer | Direct PDF-to-system, owned workflow, no Excel intermediate | £4,000 to £25,000 one-off |
The mistake to avoid: buying an enterprise PDF tool to handle a recurring conversion workflow, when the better answer is to remove the conversion from the workflow entirely. If your PDFs are coming from a known set of suppliers, and the Excel is going into a known downstream system, you do not need PDF conversion at all. You need direct integration with a human approval step. The full pattern is covered in the data extraction guide.
The opposite mistake: trying to automate everything when 80% of your PDF conversion is one-off and ad-hoc. If your team is converting one or two PDFs a week, Adobe Acrobat Pro for £17 a month is the right answer. Automation makes sense at volume and at frequency, not at convenience.
Paying for an enterprise tool to handle a 30-PDF-per-month workflow. Rossum, ABBYY and Hyland are built for the 5,000-document-per-month volume. At SME volumes, they are massively over-built. Start with Docparser or a custom build, both an order of magnitude cheaper.
Building Excel macros to clean up the converted output. If the conversion produces messy Excel and you write a VBA macro to clean it, you have built half an extraction pipeline using the wrong tool. The macro will break the next time the PDF layout changes. Replace it with an extraction layer that handles the layout variation natively, and the maintenance burden drops to zero.
Keeping the Excel intermediate "for the audit trail". The Excel intermediate is the opposite of an audit trail. It is an unversioned, ungoverned, easily-edited copy of data that exists in two systems. The audit trail you want is: PDF in, structured data in destination system, retained PDF linked to the data, all timestamped, all immutable. The Excel is what you have when you have not designed an audit trail.
Most engagements that start with "we are converting PDFs to Excel every week" end without Excel in the workflow at all. We look at where the PDFs come from, where the Excel goes, and design a direct path between the two systems with a human approval gate where it matters. The Excel becomes optional, used by people who like Excel for analysis, not required as a data-passing step.
The build itself is usually three to five weeks for a focused single-source automation, six to ten weeks for a multi-source, multi-system build. We work on your environment, integrate with Xero, QuickBooks, Sage, HubSpot, Salesforce, and most custom databases. The PDFs are retained, indexed and searchable. The structured data lives in the destination system. A user-facing dashboard shows what came in, what went out, what got flagged for review.
If your problem is the recurring conversion, the natural next read is the data extraction guide, which covers the underlying patterns in more depth. The same delivery shape underpins our AI implementation work and the ongoing tech partnership where we run, maintain and improve the system.
If you have a single PDF and you want it in Excel right now, three options work in under five minutes. Open the PDF in Adobe Acrobat (Pro or DC), choose Export to Excel, save the .xlsx. Use Microsoft Excel itself: Data tab, Get Data, From File, From PDF (in Microsoft 365). Or use a free web tool like Smallpdf, ILovePDF or Adobe's free online converter. Accuracy is best on PDFs with properly tagged tables, less good on scanned PDFs and PDFs where the table is actually an image.
Free options: Microsoft Excel's built-in PDF import (Data > Get Data > From File > From PDF, requires Microsoft 365), Smallpdf free tier (limited monthly conversions), ILovePDF free tier, Adobe's free online tool, and Google Docs (upload the PDF to Google Drive, open with Google Docs, then export to Sheets). All work for single occasional conversions. None scale to high-volume business use, which is what most people who Google this question actually need.
Most PDFs are not designed to be converted. The PDF format describes how a document looks on a page, not how data is structured. When the PDF was created from a tagged source (a Word document with a real table, an Excel file exported as PDF) conversion works well. When the PDF was scanned, photographed, or created from a system that draws table lines as graphics rather than as a table structure, the converter has to guess where columns start and end. Headers split across lines, merged cells, footnotes and watermarks all confuse the conversion.
Free tools handle a single PDF at a time, with basic accuracy on well-structured documents. Business-grade tools (Docparser, Rossum, Klippa, Mindee) handle hundreds of PDFs per month, learn the layouts of your common documents, extract specific fields rather than whole tables, integrate with your accounting or CRM system, and surface low-confidence fields for human review. The price difference reflects the integration value: free tools save five minutes; business tools save five hours per week.
Probably not. If your team is doing PDF-to-Excel conversion as a regular weekly task, that is a signal of a bigger workflow problem worth solving properly. The PDFs are usually coming from a system (supplier invoices, bank statements, insurer schedules, expense receipts) and the Excel is usually going into another system (accounting, CRM, stock control). The conversion is the bridge between two systems that should talk to each other directly. Automating the bridge (£4,000 to £9,000 fixed-quote build) typically pays back inside 6 to 12 months on saved time, and removes the conversion errors that compound silently.
Yes, but you need OCR (optical character recognition) as part of the conversion. Adobe Acrobat Pro handles this well. Free tools vary; Smallpdf and ILovePDF both offer OCR on paid tiers. Google Drive's OCR is decent and free. For business volume, the better answer is a dedicated extraction tool that combines OCR plus AI understanding rather than pure conversion: Rossum, Mindee, Klippa or AWS Textract handle scanned business documents at production quality.
If converting PDFs has become part of someone's job description, the real answer is probably not a better converter. Tell us where the PDFs come from and where the data needs to land. We will tell you honestly whether automation is worth it.
Email oliver@digitalsignet.com