Page numbers on a PDF: margins, size and the details people miss

A page number is the smallest piece of typography in a document and the first place a reader notices sloppy work. Four decisions do most of the damage: where the number sits relative to the trim edge, how far it is from the text block, how big it is compared with the body text, and what it says. Get those four right and the numbering disappears into the page, which is the point.

Where the number goes, measured from the edge

Page geometry in PDF is measured in points: 72 to the inch, 28.35 to the millimetre. A4 is 595 × 842 points; Letter is 612 × 792. The number should usually sit inside a margin band of 12–18 mm (34–51 pt) from the trim edge, on the same baseline as the footer text if there is one.

The trap is measuring from the wrong edge. A 32 pt margin measured to the baseline of the number is not the same as 32 pt measured to the bottom of its descenders, and Helvetica's digits have no descenders at all - so the number appears to float slightly higher than neighbouring footer text set in the same size. If the document already has a footer, align to the existing baseline rather than to a round number; a 2 pt difference is visible when the two sit side by side.

UseMargin from edgeSizeWhy
Screen-only report24–32 pt10–11 ptComfortable without wasting vertical space
Print, unbound36–42 pt9–10 ptClear of the trim tolerance
Print, bound or stapled48–56 pt9–10 ptKeeps the number out of the gutter
Contract or invoice32–40 pt9 ptConventional, unobtrusive
Drawing set (A1/A0)60–72 pt12–14 ptRead at arm's length

Size, weight and contrast

A page number is navigation, not content. Set it one or two points smaller than the body text and in the same type family; a number in a different family reads as an accident. Pure black is usually too loud next to grey body text - a dark grey around 70–80 % black sits back without disappearing. The exception is a scan-heavy document where the page is a noisy image: there, plain black at a slightly larger size wins, because a grey number over scanner speckle becomes illegible.

Bold is rarely right. The number competes with headings when it is bold, and a bold digit at 9 pt looks heavier than a regular digit at 11 pt. If the number must stand out - a legal exhibit, for example - increase the size by one step rather than adding weight.

Baseline alignment is the real craft

PDF text is positioned by its baseline: the line the letters sit on, ignoring descenders. A layout program places a footer by computing the baseline from the bottom margin and the font's metrics. A fixed-margin stamper that has no access to those metrics will place its baseline at a fixed distance from the edge, which is close enough for most documents and visibly off for documents with an existing footer.

If perfect alignment matters, measure once: open the page in a reader that shows coordinates, note the baseline of the existing footer text, and use that value as the margin. In PDFNest the margin field is exactly this distance, so a document whose footer baseline sits at 38 pt gets 38 in the box.

Odd and even pages

In a bound document, the number conventionally sits on the outside edge: right on odd pages, left on even pages, or centred on both. Centred is the safe choice for anything that might be printed single-sided or read on screen, because it never lands in the gutter. Mirrored placement looks more professional in a book block and is more work: it is two passes, one for odd pages and one for even pages, and both passes must use the same size and baseline.

For a document that will be printed double-sided and bound, mirrored placement is worth the extra pass. For a report that will be emailed as a PDF, centred is almost always right, and it saves a step that is easy to get wrong.

What the number should say

Three formats cover nearly every case, and the choice depends on how the document is consumed.

  • Plain number. Quiet, conventional, best for reports and books where the total length is irrelevant to the reader. It also survives splitting a document into parts, because no page claims a total that later becomes wrong.
  • 4 / 12. Compact and unambiguous. Good for invoices and short documents where the reader may want to check nothing is missing. Cheap in space, and it reads correctly even in a thumbnail.
  • Page 4 of 12. Explicit, slightly bureaucratic, right for contracts, tender documents and anything where completeness is part of the point.

The "of 12" half has a cost: it is only true for the document as it exists now. Split that file and every part inherits a claim about a total it does not contain. If a document will be split, or is a chapter of a larger work, use the plain number and put the total in the table of contents instead.

Starting numbers, covers and front matter

Books and formal reports usually leave the cover unnumbered and start counting at 1 on the first text page, which means the cover is page 1 physically but carries no number, and the first visible number is 1 on physical page 2. That is what the "leave the first page unnumbered" option does here: the count still includes the cover, so the number set as the first value appears on the second physical page.

Front matter with Roman numerals and body pages with Arabic numerals needs two passes over two parts of the document. Splitting, numbering each part, and merging back in order is the reliable route - see splitting a PDF and merging. It also makes each part checkable on its own.

Rotated and mixed-size pages

A page carrying a 90-degree rotation value is displayed turned, so a number stamped in the page's own coordinate space appears sideways on screen. The number has to be counter-rotated and its anchor moved into the displayed corner, which is a coordinate transformation rather than a font setting. Any tool that ignores page rotation will put landscape numbers in the wrong corner of every rotated page - and rotated pages are common in scan batches, where a single sheet was fed the wrong way.

Mixed page sizes cause a different problem: a fixed margin from the bottom edge moves the number up or down relative to the text block when the page height changes. That is usually acceptable, since the number is anchored to the paper rather than to the text. It stops being acceptable when a wide landscape insert carries a number at the bottom centre while the portrait pages carry theirs at 32 pt from the edge - the jump is noticeable when flipping through.

Four mistakes worth checking before you send

  1. Double numbering. The document already has numbers burned into the page image. Adding a second set produces two numbers on every page. Zoom in: if the old number does not highlight when you select it, it is pixels and cannot be removed by a stamper.
  2. Numbers over content. A scan with almost no bottom margin puts the number on top of the last line of text. Increase the margin only after checking the page's lowest ink; some crops leave 10 pt of white space and nothing more.
  3. Wrong starting value. A chapter file that starts at 1 when it should continue from 147. If the document is part of a series, set the first number deliberately and note it in the file name.
  4. Inconsistent size across parts. Two batches numbered with different settings look like two documents stapled together. Keep the settings in the file name or a note so the next batch matches.

Frequently asked

Should the number be a link or plain text?

Plain text. Links on every page add file size and gain nothing in a document that already has a table of contents. If navigation matters, the outline is the better mechanism.

Why does my number sit lower than the footer text?

Almost always a baseline difference: the two were placed from different references, or one of them included descender space. Match the margin value to the existing baseline rather than to the margin box.

Can I number only the pages I added to a merged file?

Not directly. Split the merged file at the boundary, number the new part, and merge again. That keeps the original pages untouched and gives the new section its own numbering.

Related reading: shrinking a scanned PDF and naming archived bundles.

Written by the PDFNest team. Last updated November 19, 2026.

Open the numbering tool Merging and bookmarks All guides