A table on paper is a different object
A spreadsheet is something you interrogate. You sort it, filter it, widen a column, follow a formula back to its inputs. A printed table is something you read once, in the order it was laid out, on a page that cannot be resized. Almost every bad printed table is a spreadsheet that was sent to paper without anyone deciding what the reader was supposed to take from it.
So the first decision is not a setting. It is which rows and which columns actually need to travel. A working sheet has forty columns because you needed them while you were working; a reader needs the six that carry the answer.
Your browser writes the file
The data is laid out as a table, the table opens in a new tab, and the browser's print dialogue appears. Choosing Save as PDF as the destination produces the file. Nothing is uploaded and nothing downloads on its own, and if no new tab appears at all, a pop-up blocker stopped it — allow pop-ups for the site and run it again.
That also means the print dialogue's settings decide the result: paper size, orientation, margins, whether shading prints, and whether the browser adds its own header and footer to every sheet.
Every comma is a column boundary
Each line becomes a row, and each comma in that line ends a cell. The first line becomes the heading row. That is the whole rule, and it is worth knowing exactly, because it explains the one failure people hit.
A value containing a comma splits into two cells and pushes the rest of the row out of alignment. Smith, John is two columns, not one. Spreadsheets normally protect such values by wrapping them in quotation marks, and quotation marks are not interpreted here — they will print as characters. Before pasting, replace commas inside values with a dash or a space, or reorder the column so the comma is not needed.
Two related traps come from the export rather than the data. Spreadsheets in much of Europe write CSV with semicolons, because the comma is the decimal separator there; a semicolon file arrives as a single wide column. And a figure exported as 1,250 is a thousands separator that will be read as a column break, so export or retype those without it.
Prepare the data, not the layout
Every improvement worth making happens in the text before it is pasted.
- One heading row, at the top. Merged title rows, blank spacer rows and a second heading halfway down all become ordinary data cells.
- Shorten the headings. A heading is a label, not a sentence; long ones force narrow columns for everything else.
- Round the numbers. Six decimal places consume width and nobody reads them on paper.
- Sort it into the order it should be read. There is no sorting once it is a document.
- Fill or mark the empty cells. A blank prints as nothing, and a reader cannot tell "zero" from "not measured".
Fitting a wide table on a page
Portrait A4 holds roughly six to eight columns of ordinary text before cells start wrapping into unreadable stacks. Landscape holds about half as many again, and switching orientation in the print dialogue is usually the cheapest fix available.
If it still does not fit, the answer is fewer columns rather than smaller type. Split the table into two related tables, or drop the columns that only matter to whoever built the sheet. Reducing the scale below about 80% produces something technically complete and practically unreadable.
The settings that change the output
Turn off the browser's headers and footers. Otherwise every sheet carries a URL and a timestamp that have nothing to do with your report.
Turn on background graphics if you want the shaded heading row to print. It is off by default, and with it off the heading row prints as plain bold text.
Check the paper size. It follows your system locale — A4 in most of the world, US Letter in North America — and a table built for one loses an edge on the other.
One structural limit is worth knowing before you print something long: the heading row appears once, at the start. Browsers repeat a table's heading across pages only when the markup marks it as one, and a flat table like [msm_tool slug="csv-to-pdf"] produces does not. For a table running past a single page, that is a reason to split it deliberately rather than let it run.
Read the last page before you send it
Use the preview panel in the print dialogue, which shows what the file will contain. Check the page count, check that a row has not split across a page break, and check the final page — a table that ends with two orphaned rows is worth tightening.
Then look at the numbers themselves in the finished file. Alignment, currency symbols and decimal places print exactly as they were typed, because none of the spreadsheet's formatting travels with pasted text. If the figures matter, they are the thing to read twice.