When the data you need is trapped in a document — a PDF report, a scanned list, a photographed table — getting it into a spreadsheet usually means a tedious afternoon of retyping. The Docyield document-to-CSV converter removes that step. Upload a PDF or an image and it reads the tabular content inside, reconstructs the rows and columns, and gives you back a CSV file you can open in Excel or Google Sheets straight away.
The reason "document to CSV" is harder than it sounds is that documents don't store tables as tables. A PDF places characters by coordinate; an image is just pixels. Neither knows where one column ends and the next begins, which is exactly what a CSV needs. Docyield rebuilds that grid — reading the text with OCR when the file is a scan or photo, then working out the cell boundaries — so the CSV genuinely lines up instead of collapsing into one mangled column.
Turning document data into spreadsheet rows
Drop a file onto the converter and Docyield reads it — directly from the text layer of a native PDF, or via OCR for a scan or image. It then finds the tabular regions, decides where the columns sit, groups characters into cells, and orders them into rows. The output is comma-separated data with one record per line, in the shape a spreadsheet expects on import.
Because the converter understands the table rather than just the characters, things that normally break a paste survive intact: cells that wrap onto two visual lines stay in one column, and rows that continue across pages are joined rather than scattered. A long multi-page list becomes one continuous CSV.
Why this beats retyping or copy-paste
Copying a table out of a PDF viewer rarely lands cleanly — values jump columns, multi-line cells split, and numbers arrive as text your formulas won't add. From an image, copy-paste isn't even an option; you're stuck typing. Either way you're doing the alignment work by hand and inviting transcription errors.
Reconstructing the table at the source fixes this once. Columns stay aligned because the converter knows where they are, numbers stay numeric, and each row maps to a single CSV line. The time you'd spend repairing a paste goes into actually using the data.
From scattered formats to one tidy table
Much of the appeal here is consolidation. The same underlying data often reaches a team in mismatched containers — a PDF from one supplier, a scanned sheet from another, a photographed list from a third — and the goal is a single, comparable table regardless of how each arrived. Because the converter reads all of them and returns the same row-and-column CSV, you can stack the results into one spreadsheet without first reconciling three different formats by hand.
That uniformity is what makes the downstream work possible. Once everything is CSV with aligned columns, you can append files, dedupe rows, run the same formulas across the lot, and load it all through one import routine. The messy variety of the inputs stops mattering at the moment of conversion, which is usually the whole reason a team reaches for a document-to-CSV step in the first place.
Who converts documents to CSV
- Finance and ops teams pulling figures from reports and statements into working sheets.
- Buyers and merchandisers turning supplier price lists and catalogues into importable tables.
- Researchers extracting tabulated data from PDFs and images for their own analysis.
- Admins digitising paper forms and printouts photographed on a phone.
- Anyone handed a document who needs its numbers in a spreadsheet, fast.
Accuracy and the inputs that help
Output quality tracks input quality. A digital PDF with selectable text converts almost perfectly; a clear scan or photo converts well; a blurry, low-contrast, or skewed image is harder because OCR has to recover the characters before any table logic runs. Sharp focus, even lighting, and the page filling the frame all make a visible difference.
Docyield doesn't fill gaps with guesses. A cell that's blank in the source stays blank in the CSV, and genuinely ambiguous layouts — borderless tables, heavily merged cells — are the ones most worth a quick glance against the original. For the small fraction of files that need it, that review is far cheaper than a misplaced column surfacing later in your analysis.
Messy tables and mixed content
Real documents seldom hold a single neat grid. They interleave prose with tables, merge header cells, nest sub-totals, and sometimes set two tables side by side. Docyield concentrates on the tabular regions and keeps the row-and-column relationships intact, so a merged header or a wrapped description doesn't shove every following value one cell to the left.
When a document contains several distinct tables, the data is returned in a consistent order so you can split it after import. Throughout, the aim is a CSV that behaves predictably in your spreadsheet or import script — not one that opens but quietly corrupts a column.
Making the CSV import without surprises
The last mile of any "to CSV" job is the import, and a few familiar quirks cause most of the trouble: a value that contains a comma, a cell with a line break, a code whose leading zeros get stripped, or a thousands separator that demotes a number to text. Docyield produces CSV that quotes fields when needed, so an embedded comma or newline doesn't shunt every column to the right, and it keeps numbers numeric so your formulas add them up rather than concatenating them.
When a column is really an identifier — a part number, an account reference, a postcode — format it as text in your spreadsheet around import time, since spreadsheets are eager to reinterpret such values as numbers or dates. If a row ever looks off, the cause is nearly always something in the source layout, so keeping the original document open beside the CSV for a quick side-by-side is the fastest way to confirm what happened.
Other formats and handling volume
CSV is the default, but the same extracted data is available as JSON, Excel (XLSX), or XML from the result view. CSV suits pivot tables and database loaders; XLSX keeps typed numbers and dates for spreadsheet work; JSON suits code. They're all serialisations of the same result, so switching tabs costs nothing, and one upload can feed both a database loader and a colleague's spreadsheet.
The free converter processes one document at a time, which covers most one-off jobs. When you need to convert documents regularly — many a month, on a schedule, or from your own software — the Docyield API and batch dashboard run the identical extraction with webhook delivery, so what you test here is what you get at scale. The dashboard tracks each file's status and lets you re-run any that need another pass, turning a recurring conversion into a dependable pipeline rather than a manual chore.
How to convert a document to CSV
- 1Upload your file — drop a PDF or image (PNG, JPG, WEBP) onto the box above, or click to choose one.
- 2Wait a few seconds while Docyield reads the content and rebuilds the table structure.
- 3Review the extracted rows and columns and spot-check anything against the original.
- 4Keep the CSV tab selected (the default), or switch to JSON, Excel, or XML instead.
- 5Download the CSV or copy the text, then import it into Excel, Sheets, or your database.
Frequently asked questions
Processing documents at scale?
Batch upload, an extraction API, and webhooks for 100+ documents a month.