Why does my content not fit the page width?

This is one of those problems that feels like a bug and is actually a decision — one made silently, on your behalf, by whatever produced the PDF.

You have a wide table, or a spreadsheet with a lot of columns, or a document with a chart that runs past the margin. You convert it to PDF and the right-hand side is missing. Somewhere later in the file, usually after all the "real" pages, the missing columns appear on their own — orphaned from the row labels that gave them meaning.

The mismatch at the heart of it

Word processors and spreadsheets and web pages are all comfortable being wider than a screen. You scroll. A spreadsheet in particular has no width at all in any meaningful sense; the grid simply goes on.

A PDF page has a fixed width. A4 is 210mm. Letter is 8.5 inches. That is not a preference, it is the definition of the page.

So converting from one to the other forces a decision: what happens to content wider than the paper? There are only three possible answers.

1. Cut it into strips and put each strip on its own page.
2. Scale it down until it fits.
3. Clip it and lose whatever falls outside.

Most converters, and Excel by default, choose the first. It is the least destructive — nothing is lost — but it is very often the least useful, because a table sliced vertically is no longer a table.

Why strip-cutting exists at all

It is a printing convention, and it made sense when printing was the point. You would print the strips and tape them together across a desk, or file them in order and read across. Wide-carriage printers and continuous stationery were normal.

Almost nobody does that now. The PDF is read on a screen or emailed, and a reader who has to open pages 12 through 15 side by side to reconstruct one table is being asked to do something unreasonable.

The default outlived its reason.

The fix, and the mistake people make with it

The fix is scaling — option two. It is usually called fit to width or fit to one page wide.

Here is the important part. Fitting the width is not the same as fitting the whole sheet onto one page, and confusing them is what produces those horrible PDFs where four hundred rows have been compressed onto a single sheet in unreadable type.

Two independent settings:

• Fit to 1 page wide — scale horizontally so all columns fit across.
• Fit to N pages tall — leave this unlimited.

Together they say: never cut the table sideways, but use as many pages downward as it takes. The type shrinks only as much as the width requires, and the document stays readable.

Excel to PDF, ODS to PDF and CSV to PDF all default to this, because for real documents it is nearly always the right answer.

How much shrinking is too much

Scaling is not free. There is a point where fitting the width makes the text too small to read, and at that point no setting rescues you.

Rough guidance for a portrait A4 page:

If you are in the last row, the honest answer is that the document is trying to do too much on one page. Which brings us to the other fixes.

Rotating the page

Landscape gives roughly 40% more width — 297mm instead of 210mm on A4. For a wide table that is frequently the difference between cramped and comfortable, and it costs nothing except height.

Use landscape when the content is wide and not very long. Avoid it when the document is mostly prose, because long lines of text in landscape are genuinely harder to read — the eye loses its place returning to the start of the next line.

Using bigger paper

A3 is twice the area of A4. If the PDF will be printed on A3, or read on a large screen, this solves width problems outright.

The catch is obvious: most people print on A4 or Letter, and an A3 PDF sent to an A4 printer gets scaled down anyway — you have simply moved the shrinking to the other end, where you have no control over it.

Fixing it at the source

Often the best fix is not a converter setting at all.

Set a print area. A spreadsheet's used range includes that note you typed in column AR and forgot about. The converter has no way to know it is not part of the report. Selecting your real range and setting it as the print area removes the problem completely, and it is the single most effective thing on this list.

Auto-fit the columns. A date column 30 characters wide is stealing space from a description column that needs it. Auto-fitting narrows the whole sheet for free before any scaling is needed.

Delete apparently-empty columns. A column with a single space in row 300 is not empty and counts toward the width.

Split the table logically. Some tables are two tables that got merged. If columns 1–8 are the order and 9–20 are the shipping detail, two documents may communicate better than one wide one.

The same problem in Word

Word documents hit this too, usually with a table that was built while the page was in landscape and then the page was changed, or one pasted from a spreadsheet.

The symptom differs slightly: rather than being cut into strips, the table's last columns simply run past the right margin and off the paper. That is option three — clipping — and it is the destructive one.

Word to PDF scales an over-wide table back onto the page rather than letting it run off. Worth knowing, because clipping is silent: the PDF looks fine until someone notices a column is missing entirely.

A quick way to check before you send

Whatever you converted, look at the last page of the PDF before sending it. Orphaned strips end up there, and thirty seconds of checking has saved a lot of people from sending a report with a quarter of its columns hidden at the back.