Convert CSV to PDF
A CSV has no page. A PDF is nothing but pages, so the conversion has to decide where the rows break and what happens to columns that do not fit the width. Narrow files come out looking like a report; a file with thirty columns needs a landscape page or a smaller subset before it is worth printing.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeDrop your CSV file here, or click to browse
Up to 50 MB. Deleted automatically after 30 minutes.
What it does
- Rows are paginated across as many pages as needed
- Quoted fields containing commas stay in one cell
- Wide files may overflow the page width and need trimming first
How to use CSV to PDF
- 1
Upload the CSV
With or without a header. Quoting rules are applied, so a field containing a comma is not split.
- 2
Rows are laid onto pages
The table flows down the page and continues onto the next, so a long file becomes a multi-page document rather than one impossible page.
- 3
Check the width before printing
Count your columns. Beyond roughly a dozen, a portrait page runs out of room and the result is cramped or clipped.
How it works
The CSV is parsed into rows and fields with proper quoting, then laid out as a table on a page. The layout engine measures the columns, allocates width, and flows rows onto successive pages until the data runs out.
Pagination is the part a CSV has never had to think about. A file is just lines; a document has a page height, and something has to decide where one page ends and the next begins.
The width problem
This is the only real failure mode. Page width is fixed, so the more columns a file has, the less room each gets. Up to about a dozen columns the result reads like a report. Beyond that the type shrinks and the table becomes something nobody will actually read.
The fix is upstream: decide which columns a reader needs and remove the rest before converting. A printed table is a summary, not an export.
Why convert data to a page format at all
Because some destinations only accept documents. Filing systems, printed appendices, signed records and email to people who should not edit the numbers all want a PDF. It is also the format that looks the same everywhere, which a CSV emphatically does not: open the same file in two applications and the delimiters, encodings and column types can all be interpreted differently.
What is given up
Everything that made it data. There are no types, no sorting, no filtering and no calculation in a PDF table, and extracting the rows back out is harder than it should be. Send the CSV or an XLSX alongside if the recipient may need to work with it.
Wide files are the whole problem
A CSV has no page. It is as wide as it needs to be and nothing complains. A PDF has a fixed page, and the columns have to fit on it.
Something must give, and it is worth knowing which. Columns may be narrowed until the text wraps, the table may continue onto further pages side by side, or the overflow may simply be cut. Any of the three can be the right answer depending on the file, and none of them is what you would have chosen if you had been asked.
For anything over about eight columns, look at the result before sending it. If it is unusable, the practical fix is to cut the columns you do not need from the CSV first — a PDF is a delivery format, and a delivery copy is allowed to contain less than the source.
Examples
A 300-row order list for filing
Six columns fit comfortably, and the rows flow across pages the way a printed report should. This is the shape of file the conversion handles best.
A wide analytics export
Twenty-eight columns cannot be readable on a page. Cut the file down to the columns that matter before converting, or convert to XLSX instead and let the reader scroll.
Frequently asked questions
Why did my wide CSV come out unreadable?
Because a page has a fixed width and a spreadsheet does not. A CSV with thirty columns has to be compressed into the same space as one with five, so the type shrinks and the columns crowd. There is no setting that fixes this, only a change of input: remove the columns nobody will read, or keep it as a spreadsheet where a reader can scroll sideways.
Are rows split across pages?
The table flows onto as many pages as it needs, so a long file becomes a multi-page document and no rows are lost. What a PDF cannot do is what a spreadsheet does automatically, which is repeat the header at the top of each page unless it has been told to. Check the second page before printing a long file for a meeting.
Should I convert to PDF or to XLSX?
PDF if the file is going to be printed, filed, signed or sent to someone who must not change it. XLSX if the recipient is going to work with the data, because a PDF table is text on a page and getting it back into rows and columns is genuinely awkward. The mistake worth avoiding is sending a PDF to someone who needs to calculate on it.
Further reading
- The Same Table Was Three Times Bigger as JSONCSV writes each column name once, at the top. JSON writes it again on every single row. On a table of any size that is not a subtlety — it is the dominant term, and it explains both why the conversion inflates and why it barely matters over the wire.
- The Three Invisible Bytes at the Start of Your CSVYour CSV has a column called `id`. Your code looks for a column called `id`. It is not there. Print the header and it says `id`. The problem is three bytes at the very start of the file that no editor displays, that Excel on Windows once needed, and that half the software in the world now has to work around.