Most first novels start in Google Docs. It's free, it's already open in a browser tab, and it autosaves so reliably that losing work is nearly impossible. None of that is a compromise. The compromise shows up later, once the document is 40,000 words long and every piece of structure you have is something you built by hand.
Setting up a Google Docs manuscript correctly from the start
The single biggest mistake writers make in Docs is formatting by feel: selecting a line, bumping the font size, hitting bold. It looks fine in the moment and falls apart by chapter twelve, because nothing about it is consistent or reusable. Use Docs' built-in paragraph styles instead.
- Chapter titles: apply the Heading 1 style, not a manually resized line. This gives you a working table of contents and, later, lets any tool that imports the file detect chapters automatically.
- Body text: set Normal text to 12pt Times New Roman or Courier New, double-spaced, with a first-line paragraph indent set through Format > Paragraph styles rather than by pressing Tab. Manuscript convention exists for a reason: it's what agents and formatting software expect.
- Scene breaks: a centered line reading
***is the standard marker within a chapter. Type it consistently, since it's also the marker most import tools look for later.
Keeping chapters and scenes organized in one long document
Docs has no native concept of "chapter" or "scene." Everything lives in one continuous file, which is fine at 5,000 words and genuinely difficult to navigate at 90,000. Two things help: the document outline panel (View > Show outline), which reads your Heading 1 styles and builds a clickable sidebar, and a consistent naming convention if you split the manuscript across multiple files, something like Book Title - Part 1.docx rather than a folder of files named "draft," "draft 2," and "draft final."
Neither of these solves the underlying problem. You're still tracking structure in your head and re-creating it with formatting conventions, not working with chapters and scenes as things the software actually understands.
Where Google Docs formatting quietly breaks down
Three failure points show up almost every time, once a manuscript gets long enough.
Font and size drift. A paste from another document, a autocorrect quirk, a moment of manual formatting eleven chapters ago: over tens of thousands of words, small inconsistencies accumulate and become genuinely hard to find, let alone fix, by scrolling.
Indent inconsistency. Tab-based indents and style-based indents look identical on screen but behave differently on export, and mixing the two across a manuscript produces a file that looks wrong the moment it's opened somewhere else.
No clean export path. Download as .docx or PDF and Docs carries every one of those small inconsistencies straight into the file. There's no formatting pass built in, no way to catch what's already gone wrong before it lands in an agent's inbox or on Amazon's upload page.
Signs you've outgrown Google Docs for your manuscript
A few concrete signals, not vague dissatisfaction, tend to mean it's time to move:
- You have a separate document, spreadsheet, or app just to track character details and can't remember which one has the current version.
- You've scrolled for a full minute looking for a scene you know you wrote.
- You've caught inconsistent formatting during a read-through and had no idea how far back it started.
- You want to outline, reorder scenes, or build out a fictional world, and you're doing it in a second app because Docs has nothing built for it.
What to do once you've outgrown it
The good news is that a well-structured Google Docs manuscript, one using real Heading 1 styles for chapters and consistent *** scene breaks, is exactly what a dedicated writing app needs to import cleanly. Quillen reads a .docx file, turns every Heading 1 into a chapter, and turns every *** or ### line into a scene break automatically, carrying your bold and italic formatting with it. The setup habits from the first section of this guide aren't wasted effort if you switch; they're what makes the switch painless.
Common questions
Can you actually write a whole novel in Google Docs?
Yes. Plenty of published novels were first drafted in Google Docs. It has no length limit that matters for a manuscript, and it autosaves as you type. What it lacks is structure: chapters, scenes, characters, and formatting all have to be built and maintained by hand.
How do I stop my chapters from losing formatting in Google Docs?
Use Docs' built-in paragraph styles (Heading 1 for chapter titles, Normal text for body) instead of manually bolding and resizing text. Manual formatting is the main reason spacing and fonts drift over a long document, and it's also what makes chapters easy to import into other software later.