When a PDF converts to Excel and every value lands in one column, usually column A, the converter read the page as a stream of loose text instead of as a table. It never rebuilt the vertical boundaries between columns, so each line of the document dropped into a single cell. This happens most on PDFs with no ruled gridlines, on scanned pages, and with basic tools that only pull the raw text out of the file. The fix is to use a converter that detects the table structure, or to split the single column back apart inside Excel.
It is one of the most common complaints about PDF to Excel conversion, and it is fixable in a few minutes once you know what caused it. Here is why the columns collapse and three reliable ways to get them back.
Why does a PDF convert to Excel all in one column?
A PDF does not store a table the way a spreadsheet does. There are no cells, rows, or columns inside the file. What looks like a table is really a set of characters placed at fixed positions on the page, sometimes with drawn lines painted on top. When you convert that page, the tool has to reconstruct the grid by measuring the gaps between the characters and any lines it can find. A converter that skips that step and simply reads the text stream in reading order writes each visual line into one cell, and everything stacks up in column A.
You will see this most often in three cases. The table has no visible borders, so there are no lines to guide the split. The document was scanned, so it is an image with no selectable text at all. Or the tool you used is a plain text extractor rather than a table converter, so it was never trying to find columns in the first place.
Fix 1: use a converter that detects the table, not just the text
The cleanest fix is to run the file through a converter built to find the table. Drop the PDF into the PDF to Excel converter at the top of this page and it measures the spacing and any ruling lines, works out where each column starts and ends, and writes every value into its own cell. Instead of one tall column, you get the same grid you saw on the page, with numbers kept numeric so you can total and sort them right away. For pages that are mostly a single table, the PDF table extractor is tuned for exactly that job.
This solves the problem at the source, because the column boundaries are rebuilt during the conversion rather than guessed at afterward. It is also the only approach that scales past a page or two, since splitting columns by hand gets tedious fast.
Fix 2: split one column into many with Text to Columns
If you already have a file with everything in column A and you do not want to reconvert, Excel can break it apart. Select the column, open the Data tab, and choose Text to Columns. Pick Delimited if the values are separated by a consistent character such as a space, tab, or comma, then tell Excel which character to split on and preview the result. Pick Fixed width instead when the columns line up at the same character position on every row, which is common with monospaced financial printouts, and drag the break lines where each column should start.
Text to Columns works well on simple data, but it has real limits. It splits on every occurrence of the delimiter, so a text field that contains a space, like a vendor name, gets torn into several columns. Numbers written with a thousands separator can break in the same way. And it cannot help at all if the rows do not share a consistent structure. When the data is messy, reconverting with a table aware tool is faster than fighting the split by hand.
Fix 3: for a scanned PDF, run OCR first
If the PDF is a scan or a photo of a document, there is no text inside the file for any converter to read, only pixels. A text only tool will return a blank sheet or a jumble, and Text to Columns has nothing to work with. The page has to be read by optical character recognition first, which turns the image into actual characters, and only then can the grid be rebuilt. A converter with built in OCR does both steps in one pass, reading the scan and mapping the recognized values into columns. If your source is a scan, this is usually the real reason the columns collapsed.
How to stop it happening in the first place
Prevention is mostly about the source file. When you have a choice, export the report directly from the system that produced it rather than printing it to PDF, because a direct export keeps the text and often the structure. If you are handed a PDF, prefer a table aware converter over a generic "PDF to text" tool. And when a table has no borders, a good converter still handles it, but a scan of that same borderless table is the hardest case, so scan at a higher resolution if you control that step. Keeping the numbers aligned and preserving the formatting during conversion saves the cleanup entirely.
When the single column is actually correct
Not every one column result is a bug. If the source really is a single list, a column of account numbers, a list of names, or a set of line items with no amounts beside them, then one column is the right answer and nothing is broken. The problem is only a problem when the original clearly had several columns of data side by side and they ended up stacked. If you are unsure, look at the PDF: count the columns you can see, and that is how many the spreadsheet should have.
The short version
Everything landing in one column means the tool read text instead of a table. Reconvert with a converter that detects the grid, split the column with Text to Columns for simple data, and run OCR first if the file is a scan. For anything past a page or two, reconverting with a table aware tool is faster and cleaner than splitting by hand. Teams that process sensitive or high volume documents often move this off the desktop entirely and hand it to software built to read documents at scale, so the columns are right the first time.