Get a spreadsheet onto pages without splitting every table

The classic failure looks like this: a twelve-column report converts into a document where pages one to four contain the first seven columns and pages five to eight contain the remaining five, with no way to line them up. Nothing malfunctioned. Nobody told the converter where the page boundaries should be.

A grid has no pages

A spreadsheet is an unbounded grid. It scrolls in both directions and has no concept of where one page stops and the next begins. A PDF is a sequence of fixed rectangles.

So conversion has to cut the grid up, and the settings that control that cut do most of the work. The spreadsheet conversion tool renders supported XLSX sheets into a searchable multi-sheet PDF, and these are the decisions worth making before you export.

Define the print area. Without one, the converter uses the entire used range, which includes that formula you left in cell BQ4000 three months ago. The result is dozens of near-empty pages. Restricting the area to the data you actually want removes the majority of surprise output.

Fit to one page wide. This is the setting that prevents horizontal splitting. Scaling everything down to fit the page width keeps each row intact on a single page, so a reader can follow a row from start to finish. Allow the height to run to as many pages as needed — vertical splitting is fine, because rows continue naturally.

Choose landscape for wide data. Landscape gives roughly 40 percent more width and is usually a better answer than shrinking type to fit portrait.

Repeat header rows. Set the top row to repeat on every page. Without it, page four is a wall of numbers with no column labels.

Watch the scale

"Fit to one page wide" solves splitting by shrinking, and shrinking has a limit. Below about 60 percent scale, printed output becomes genuinely hard to read, and below 50 percent it is not worth printing at all.

If you are hitting those numbers, the answer is less data rather than more shrinking:

• Hide columns that do not need to be in the report — internal codes, working columns, audit fields.
• Shorten header text so columns can be narrower.
• Split the report into two documents by column group.
• Reconsider whether a table is the right presentation. Twenty columns of numbers is often a chart wearing a disguise.

Formatting that survives

Generally: cell values, number formats, fonts, colours, borders, merged cells, and column widths carry across. Conditional formatting usually renders as the resulting appearance rather than as a rule.

What needs checking:

• Formulas become values. A PDF stores the displayed result. That is normally the point, but it means the recipient cannot see how a number was derived.
• Column width truncation. A cell whose text is wider than its column may render as #### or clip, exactly as it does on screen.
• Comments and notes may not appear, and if they do, they may not be where you expect.
• Charts should render, but check their positioning relative to page breaks.
• Very long text in a cell can be cut rather than wrapped, depending on the cell's wrap setting.

Multiple sheets

Decide deliberately which sheets are included. Common surprises:

• Hidden sheets. Frequently contain working data, lookup tables, or older versions, and they are hidden for a reason.
• Sheets with a single stray value. Produce a page containing one number.
• Sheet order. The output follows tab order, which may not be reading order.

Give each sheet a footer identifying it, so a printed page separated from the pack can be placed. The header and footer guide covers doing that consistently across a finished document.

Related conversions

• The source is a CSV rather than a workbook. Use the CSV tool instead; the CSV guide covers delimiter and encoding checks that matter more for raw exports.
• You need to go the other way. Pulling a table out of an existing PDF is a harder, inference-based problem, described in the PDF to Excel guide.

A final observation worth making: workbooks are where organisations keep their most concentrated sensitive data — payroll, pricing, customer lists, forecasts. Converting one is a routine act that would, through an upload-based service, disclose the entire dataset rather than the report you meant to share. Rendering locally keeps the grid on your machine and sends only the pages.