Tables are the one formatting element that can make a nonfiction book look authoritative or amateurish within seconds. If you write workbooks, textbooks, business books, or any nonfiction title that presents data, learning how to format tables in a book correctly is not optional — readers judge your credibility by how your tables look before they read a single cell. Our complete guide to how to format a nonfiction book covers the whole interior; this guide zooms in on tables alone, for print and eBook.
By the end, you will know the width rules for tables on a 6×9 print page, the cell font sizes that stay readable, how to style and repeat header rows, when to split a long table or turn it sideways, which borders and shading look professional, how to caption and number tables, why complex tables break in reflowable eBooks, and a proofing checklist to run before you upload.
Quick answer: A print table must fit inside the text block (about 4.5 inches wide on a standard 6×9 page), use 9–10pt type inside cells, repeat its header row on every page, and keep borders light and consistent. An eBook table must be simple — few columns, no merged cells, short cell text — because reflowable formats resize unpredictably on small screens. When a table is too complex for reflow, convert it to an image as a last resort, with full alt text describing the data.
In this guide
- Table Width Rules for a 6×9 Print Book
- Font Sizing and Spacing Inside Cells
- Header Row Styling Readers Can Scan
- Repeating Header Rows Across Pages
- Splitting Long Tables Across Pages the Right Way
- Borders and Shading: Less Is More
- Landscape Tables for Wide Data
- Table Captions, Numbering, and Footnotes
- eBook Reflow: Why Complex Tables Break on Kindle
- Accessibility and the Pre-Publish Table Checklist
- Frequently Asked Questions
- Conclusion: Tables That Look Traditionally Published
Table Width Rules for a 6×9 Print Book
The first rule when you format tables in a book for print is simple: the table must never cross the page margins. On a standard 6×9 paperback with 0.75-inch outside margins and a gutter allowance for the binding, your text block is roughly 4.5 inches wide. A table that bleeds into the margin looks broken at a glance, and print-on-demand prepress checks will not catch it; the error sails straight into the finished book.
Start by deciding how many columns you truly need. Most readable print tables use three to five columns; beyond six, cells become cramped no matter what you do. Give the first column — usually the label column — the most room, and keep numeric columns narrow. If your data needs more columns than 4.5 inches can hold, do not shrink the type below 8pt to force it in. Simplify instead: shorten column headers, move units into the caption, or split the table in two. Books built around heavy data deserve a larger trim size, as our guide to formatting textbooks for self-publishing explains.
One more print-only trap: the gutter. On the bound edge, the inner margin effectively grows, and a centered table can drift toward the spine after trimming. Keep every table fully inside the text block, and review the exported PDF in a two-page spread view before you approve the file.
Font Sizing and Spacing Inside Cells
Body text in most books is set at 10.5–11.5pt, but table cells work better one step smaller: 9–10pt is the professional standard for cell text, with headers at the same size in bold. At 9pt, a serif face like Garamond stays crisp on paper; below 8.5pt, letters blur and older readers give up. Match the table font to your body font — a sans-serif table inside a serif book is a deliberate style choice, not a mistake, but only when applied consistently to every table.
Cell padding matters as much as type size. Give every cell at least 3–4pt of space above and below the text and 4–6pt on the sides, so numbers never touch the gridlines. Right-align numeric columns (or align them on the decimal point) and left-align text columns; align each header exactly like the data beneath it. Turn off automatic hyphenation inside tables — a hyphenated word wrapping across a gridline is nearly unreadable. Never let the software shrink type to fit: “AutoFit to Contents” produces uneven columns and cramped type. Set column widths manually, set the type size once, and make the content obey your grid.
Header Row Styling Readers Can Scan
The header row is the part of the table readers read first — scanners check the column headers before deciding whether the table deserves their time. Make headers unmissable: bold type, a light shaded background (10–15% gray), and wording that says what the column contains in plain language. “Q3 Revenue ($000s)” beats “Rev” every time.
Keep header text short but complete, and avoid stacking two rows of headers with merged cells when one row will do — merged header cells are the single biggest cause of eBook table failures later. If a column needs a unit, state it in the header once instead of repeating it in every cell below. Skip heavy fills or white reversed type on dark backgrounds unless your book prints in full color; in black-and-white print, reversed type can fill in and turn muddy. A light tint with dark bold text stays readable in every print mode and every eBook theme, including dark mode.
Repeating Header Rows Across Pages
Any table longer than one page needs its header row repeated at the top of every continuation page — without it, readers must flip back to the first page to remember what each column means. In Word, select the header row, open Table Properties, go to the Row tab, and check “Repeat as header row at the top of each page.” In InDesign, designate the header rows in the table setup.
A repeated header must be an exact copy: same shading, bold type, and borders. Set the header style first and the repeat second — restyling the first header by hand afterward can leave continuation rows mismatched. Verify in the exported PDF, where the repeated row should appear on every continuation page, styled identically. Then add a small continuation cue so readers never wonder whether they are looking at a new table: either repeat the caption with “(continued)” or add a thin rule above the repeated header. Pick one convention and use it for every long table in the book.
Splitting Long Tables Across Pages the Right Way
Tables longer than a page must break, and where they break is a design decision. Let the table flow naturally across the page boundary — never force a manual page break that strands one or two rows alone at the bottom or top of a page.
What you must never do is split a table by cutting it into two separate tables and styling each by hand. Two tables drift out of sync — column widths shift, shading changes, and the eBook version becomes two unrelated objects. One table object, one set of styles, one caption, flowing across pages: that is the professional standard, and it is the only structure that survives conversion to eBook formats intact. The caption appears once, above the table’s first appearance; continuation pages get the “(continued)” cue, never a second full caption with a new number.
Borders and Shading: Less Is More
The cleanest book tables use the fewest lines: a top rule, a bottom rule, and a rule beneath the header row. That classic style works because alignment does the work gridlines would otherwise do. Vertical rules between every column are visual noise; readers follow columns easily when alignment is consistent. If a dense table genuinely needs vertical separation, use light 0.5pt gray rules rather than black.
Shade sparingly: a header-row tint plus alternating row tints at 3–5% gray for tables longer than about ten rows. Never use saturated colors — they turn to mud in black-and-white print, and most paperbacks still print in black and white. If your book sells in both color and black-and-white editions, proof every shaded table in grayscale; elegant amber striping in color can become unreadable gray-on-gray. And design tables to remain perfectly readable with zero shading — borders and bold headers alone — because some reading apps ignore background colors entirely and dark mode can invert them unpredictably.
Landscape Tables for Wide Data
Some tables are simply wider than 4.5 inches, and no simplification fixes them: financial statements, comparison matrices, timetables. The professional print answer is a landscape page. The table sits on its own page, rotated 90 degrees, while the page number and running head stay in portrait position. Keep landscape pages rare — more than a handful feels disorganized — and face them all the same direction so readers turn the book one way.
In Word, insert a section break, switch that section to landscape orientation, place the table, then break back to portrait for the following text. Caption the table as usual, and mention it in the body text (“see Table 5.3 on the following page”) so readers know to turn ahead. For eBooks, landscape pages do not exist — a reflowable file has no fixed pages or orientations. A table that needs landscape in print almost always needs redesigning for eBook: split it into two tables, transpose rows and columns, or convert it to an image. Plan both versions from the start rather than discovering the problem during conversion.
Table Captions, Numbering, and Footnotes
Every table gets a caption, numbered by chapter: Table 3.1, Table 3.2, and so on. By print convention the caption sits above the table (figures go below; tables go above). Style every caption identically — bold “Table 3.1” followed by a regular-weight descriptive title — and keep a running list so numbers never skip or duplicate. Reference each table by number (“see Table 4.2”); a table nobody refers to should be cut.
Footnotes belong directly under the table, not at the bottom of the page. Use superscript letters or symbols inside cells, then list the notes in 8–9pt type beneath the table’s bottom rule, before the body text resumes. Put the source on the final line — “Source: …” — so no reader ever wonders where the numbers came from. If your tables need back-matter entries, our book index formatting guide covers how indexers handle tabular material. Decide your conventions in chapter one and enforce them to the last page: mixed caption styles and wandering footnotes chip at the reader’s trust.
eBook Reflow: Why Complex Tables Break on Kindle
A reflowable EPUB or Kindle file has no fixed page width. The reader controls the font size, the margins, and the screen — from a phone to a tablet — so your table must survive being squeezed into a narrow column of text at the largest font setting. Merged cells, nested tables, rotated text, and fixed column widths are the four great breakers of Kindle tables. Each renders differently across devices, and “it looks fine in my Kindle app” proves nothing about anyone else’s screen.
The reflow-safe table is deliberately boring: four or fewer columns, no merged cells, short cell text, one header row, simple top, bottom, and header rules. Build every eBook table to that spec, even if the print version is fancier. Test at the largest font size on the smallest preview device in Kindle Previewer; if the table survives that combination, it survives everything. Our comparison of eBook formats explains which file types your tables travel through on the way to readers. When a table cannot be simplified — a wide financial statement, a dense comparison matrix — convert it to an image as a last resort: export at 300 DPI, keep it around 1200px wide, write full alt text describing the data, and caption it as a figure so the numbering stays honest. Image tables are invisible to screen readers beyond their alt text, which is exactly why this is the last resort, not the first.
Accessibility and the Pre-Publish Table Checklist
Accessible tables are simply well-built tables: a real header row (not just bold text in the first row), a logical reading order from left to right and top to bottom, and no information carried by color alone. In EPUB, proper header cells let screen readers announce each cell’s row and column context. If you export a table as an image, the alt text must convey the data itself — “table image” helps nobody.
Run this checklist on every table before you upload your files:
- Every table fits inside the text block, with nothing crossing the margins.
- Cell text is 9–10pt, headers are bold, and no type anywhere in a table drops below 8.5pt.
- Multi-page tables repeat an identical header row on every page, with a “(continued)” cue.
- Borders are consistent: top, bottom, and header rules only — no stray gridlines, no mixed weights.
- Tables are numbered Table X.Y with captions above, and every table is referenced by number in the body text.
- Footnotes and sources sit directly under the table in 8–9pt type, never at the page footer.
- eBook tables tested at maximum font size in Kindle Previewer; complex ones simplified or converted to images with genuine alt text.
Frequently Asked Questions
Conclusion: Tables That Look Traditionally Published
Tables do not have to be the part of your book you dread. Fit them inside the text block, keep cell type at a readable 9–10pt, repeat your headers, restrain your borders, number and caption everything, and simplify ruthlessly for eBook reflow. Do that consistently and your tables will look like they came from a traditional publisher — the impression that sells nonfiction.
Tables that look traditionally published
ArrowUpz formats every table in your book — print-perfect widths, repeating headers, reflow-safe eBook tables, and consistent captions — so your data looks like it came from a traditional publisher.
Basic Formatting — $97 per book
Professional Formatting — $147 per book
Premium Formatting — custom quote




