Getting Word to Behave for Print
Microsoft Word was never designed for book-length typesetting, but people do it anyway. I've spent more years than I care to count watching people export perfectly usable manuscripts from Word and then realize halfway through the print-on-demand proof that their chapter headings are shifting, their page numbers are wrong, and their margins have collapsed somewhere between section 3 and section 4. The core issue is that Word is a word processor, not a typesetter. It handles layout reactively rather than procedurally. When you add two paragraphs to chapter 7, every page number after that point recalculates. In a proper typesetter like InDesign or even LaTeX, your text flows but your pagination structure is defined differently. Word just moves everything downstream and hopes nothing breaks.
What Typesetting In Microsoft Word Selfpublishing Actually Looks Like
Here's what the workflow generally involves: you take your manuscript, apply consistent styles to headings and body text, set your trim size and margins, manage your page breaks manually, and export to PDF. That's it. The entire pipeline is Word-native. No external software required beyond a PDF printer driver if your Word version doesn't export natively. For a 60,000-word novel in 5.5 x 8.5 trim, you're typically looking at roughly 200 to 230 pages depending on font choice. If you pick Garamond at 11 points with 13-point leading, you'll land closer to the higher end. Times New Roman at the same size gives you more text per page because of its tighter proportions. This matters for your cover calculation. I use Styles exclusively. Every single paragraph in the document maps to either the Normal style or one of the Heading styles. This isn't optional advice, it's the single thing that prevents your table of contents from becoming an exercise in frustration. When you go to insert an automatic TOC in Word, it only pulls entries that are formatted with heading styles. If you've manually bolded and resized twenty-seven section headers instead of applying Heading 2, the TOC builder has nothing to work with.
The standard settings I start with are 1-inch margins all around for a 5.5 by 8.5 book, though some interior pages use 0.75 inches on the outer edges to save paper. Garamond 11-point body, 13-point line spacing, justified alignment with no hyphenation turned on for fiction. Hyphenation helps with justified text, but it also introduces inconsistent word breaks that can look ugly in a novel where rhythm matters.
Get the Full Details
The Page Number Problem Nobody Warns You About
I ran into a specific issue once that cost me roughly six hours of rework. I had a 320-page manuscript formatted correctly across front matter, body, and back matter. The front matter used lowercase Roman numerals (i, ii, iii) and the body used Arabic numerals (1, 2, 3). Standard practice. I inserted section breaks between the front matter and the body, set the page numbering to restart at 1 for the body, and everything looked fine in the Word document itself. Then I exported to PDF and uploaded it to CreateSpace. The proof came back with the Arabic numbering starting on page 3 of the actual print book instead of page 1. What had happened is that the section break I'd inserted was being counted as a blank page in the final imposition. Word had inserted an extra unnumbered page that the printer's binding process didn't account for, throwing off every subsequent page number in the front matter. The workaround was to remove the section break, insert a regular page break instead, and then use Format Pages > Starting Number on the page where the body begins. This tells Word to treat the new section as a continuation rather than a structural division, which prevents the phantom blank page from appearing in the final output. I also disabled "Strictly follow our online guide" in the print settings because that option forces Word to recalculate pagination based on its own assumptions about binding width, which is another common source of error.
Export Settings That Actually Work
When you go to File > Export > Create PDF/XPS Document, the default settings are almost always wrong for self-publishing. You need to click Options and select Minimize size for online publishing if you're sending to Amazon KDP, or select Standard if you're using IngramSpark or another printer that accepts high-quality PDFs. The difference is significant. The minimized setting compresses images aggressively and can degrade your cover art enough to cause rejection during the proofing stage. I always export at Standard quality and then run the PDF through Adobe Acrobat Reader to verify that all fonts are embedded and that there are no missing glyphs. Word sometimes substitutes fonts when you use less common characters like em dashes or special punctuation, and those substitutions don't always survive the PDF export cleanly. An em dash that looks correct on screen can turn into a box or a question mark in the printed version if the font substitution wasn't handled properly.
When Word Is the Wrong Tool
Let me be blunt about the limitations. Typesetting In Microsoft Word Selfpublishing works fine for text-heavy fiction and nonfiction books under about 350 pages. Once you hit that threshold, the document starts to slow down noticeably. Scrolling becomes laggy. The Styles pane takes longer to load. And the risk of corruption increases with file size. I've seen .docx files over 50 megabytes behave erratically, with formatting randomly resetting after a save cycle. If your book contains significant tables, charts, sidebars, or multi-column layouts, Word will fight you the entire time. Table formatting in Word is notoriously unstable across different PDF export settings. A table that looks perfectly aligned in the editor will shift its column widths in the exported PDF. This is a known issue and there's no real fix other than exporting tables as images, which degrades quality and makes the text inside them unsearchable. For any project with complex layouts, InDesign is the appropriate tool. It's not free, but it handles pagination, master pages, and text flow in ways that Word fundamentally cannot. The learning curve is steeper, but the output is consistently more reliable. If you're doing serious self-publishing work, investing time in InDesign pays for itself within the first project. Word should be viewed as a drafting and first-pass tool, not aprint-ready production environment.
The realistic assessment is that Word can produce acceptable results for simple books, but the margin for error is thin and the troubleshooting overhead grows exponentially with each added complication. Plan accordingly.
