Google Docs is a perfectly good place to write a book, and a poor place to finish one. It can produce a clean, well-structured manuscript. It cannot produce a validated EPUB with a proper chapter menu, or a print interior with mirrored margins and a gutter, because it was never built to.
So the job in Docs is not to make the book look finished. It is to make the structure unambiguous — what is a chapter, what is a paragraph, what is a scene break — so that whatever turns it into a publishing file can read it without guessing. That is a short list of habits, and here they are.
GOOGLE DOCS
↓
heading styles on chapter titles
↓
paragraph indents, not tabs or blank lines
↓
page breaks between chapters
↓
File → Download → Microsoft Word (.docx)
↓
FORMATTER
↓
Kindle · EPUB · print interior
1. Style chapter titles as headings
This is the one that matters most, and the one most manuscripts get wrong.
Select the chapter title, then Format → Paragraph styles → Heading 1. On a keyboard, Ctrl+Alt+1 on Windows or ⌘+Option+1 on a Mac.
What you must not do is select the title and make it larger, bold and centred by hand. The two look identical on your screen. They are completely different underneath: one is a heading, which a converter recognises as a chapter and turns into an entry in the ebook's chapter menu; the other is a paragraph that happens to look large, which becomes nothing.
If the built-in Heading 1 looks wrong to you — it is blue, and large — do not fight it by formatting each title. Style one the way you want, then Format → Paragraph styles → Heading 1 → Update 'Heading 1' to match, and every heading in the document follows. The look is irrelevant anyway; it is replaced entirely when the book is formatted. Only the structure survives.
Use Heading 2 for sections within a chapter, if a non-fiction book has them. Keep the levels consistent: every chapter title Heading 1, every subsection Heading 2, nothing skipped.
2. Indent paragraphs with a style, not the Tab key
A first-line indent is the normal way to mark a new paragraph in a book. Set it once for the whole document rather than pressing Tab at the start of each one.
Format → Align & indent → Indentation options, then under Special indent choose First line and enter 0.5. Apply it to Normal text, and every paragraph gets it.
Tabs at the start of paragraphs are the second most common thing a formatter has to clean out of a manuscript. Blank lines between paragraphs are the first. A book does not have space between paragraphs; that is a convention from web pages and emails, and a converter that finds both an indent and a blank line has to guess which you meant.
3. Set line spacing, but do not obsess over it
Format → Line & paragraph spacing. Double spacing is what an agent expects in a submission manuscript and is comfortable to write in. For a book that is going straight to publication it does not matter at all, because the spacing is set fresh by whatever formats it — an ebook's spacing is chosen by the reader, and a print interior's is chosen by the typesetter.
Set it to whatever you like writing in. It will not survive.
4. Break chapters with a page break, not with Enter
A new chapter starts on a new page. Put the cursor at the end of the previous chapter's last line and use Insert → Break → Page break, or Ctrl+Enter.
Do not press Enter until the text drops onto the next page. That works exactly until you edit anything above it, at which point every hand-made break in the rest of the book is in the wrong place. A page break is a single, explicit instruction that survives editing.
Strictly, a heading styled as Heading 1 is enough on its own — a formatter starts a new page at every chapter heading regardless. The page break is for you, so the document reads like a book while you work on it.
5. Mark scene breaks with a visible symbol
Within a chapter, a change of scene is traditionally marked by a blank line. That is a problem in a book, because a blank line at the bottom of a page is invisible, and so is one at the top of the next. The reader turns the page and has no idea the scene changed.
Put a symbol on its own line instead: a #, or * * *, centred. A formatter
recognises it as a scene break and replaces it with whatever the book's
design uses; a blank line is just a blank line, and may be stripped out as
one of the many stray blank lines a manuscript accumulates.
6. Leave the margins and the page size alone
Docs has margin settings and a page size. Neither transfers to the finished book. An ebook has no page; a print interior has a trim size and margins that depend on the page count, which nothing in Docs can compute. Set them for your own comfort while writing and forget them.
The one thing worth knowing is that Google Docs cannot do mirrored margins — a wider inside margin on the left page and the right page alternately, which is what a bound book needs. That alone rules it out as the final step for a paperback.
7. Export as a Word document
File → Download → Microsoft Word (.docx).
This is the file a formatter wants. Not the Google Docs link, not a PDF — a PDF has already thrown the structure away and turned your headings into pictures of headings — and not the EPUB that Docs will also offer to download.
On that last option: Docs can download an EPUB, and it will open. But you get no say in the navigation or the metadata, no validation, and the chapter menu is exactly as good as your heading styles and no better. It is a reasonable way to read your own draft on a phone. It is not a file to upload to a store.
Why Docs alone does not finish the job
Because finishing a book is a different job from writing one, and it involves things Docs does not have.
An ebook needs a navigation document — the literal list of links that becomes the chapter menu — real metadata, and a pass through a validator before a store will accept it. A print interior needs a trim size, margins that mirror across the spread, a gutter that widens with the page count, chapters opening on the right-hand page, and page numbers that know about all of that. A submission manuscript needs a header line and a precise, plain layout that agents recognise on sight.
None of these are Docs' fault. They are typesetting, and a word processor is not a typesetter. What Docs can do — and does well, if you use the seven habits above — is hand over a manuscript whose structure is so clear that the typesetting can be done without a single guess. That is worth more than any amount of making it look nice.
Where the exported DOCX goes next depends on what the book is for: the manuscript formatter if you are submitting to agents, the Kindle formatter or EPUB formatter for an ebook, and the print book formatter for a paperback interior. All four read the same structure you have just set up.
Menu names are as they appear in Google Docs at the time of writing. Google moves things occasionally; the settings themselves have not changed in years.