Why is Google Docs so slow on my long novel?

Where the lag comes from

A Google Doc runs inside a browser tab, and the tab holds far more than your sentences. It carries comment threads, open suggestions, and the live spelling and grammar pass over every page. At a few thousand words none of that is noticeable. Past a hundred thousand, writers report letters appearing a beat after the keys are pressed, scrolling that stutters, and a long wait before the document will take input at all.

Much of that weight can be shed without moving the book anywhere.

Making the document lighter

1. Go pageless. Choose File → Page setup and pick Pageless. Docs stops drawing page breaks, headers, and footers, which is work a drafting session does not need. Switch back before you print.
2. Stop checking as you type. Under Tools → Spelling and grammar, switch off the spelling and grammar suggestions. Run a check on purpose at the end of the day instead.
3. Clear old suggestions and comments. Tools → Review suggested edits offers Accept all and Reject all; resolve comment threads you have finished with. Make a copy first if an editor's marks are still worth keeping.
4. Test without extensions. Open the document in a private or Incognito window, where most extensions are off. If typing is suddenly quick, a grammar checker or similar add-on is reading every keystroke; switch it off for Docs.
5. Shrink big images. Photographs and mood boards pasted at full size add up. Resize them before inserting, or keep them in a separate reference document.

Chrome's own Task Manager (More tools → Task manager) shows whether the Docs tab or something else is eating the memory, which is worth a glance before blaming the book.

When it is still slow: split it

The dependable remedy is holding less text in one document. Tabs keep chapters apart for navigation, but they still live in a single file, so do not count on them for speed. Separate documents per act or per chapter, numbered so they sort (01 Arrival, 02 The Crossing), stay light however long the book grows.

That trade has a cost. Search, word counts, and reading straight through now stop at each file's edge. One file or one per chapter weighs it, and if Docs has refused to take any more text at all, see Google Docs says my book is too large.

In Tabularia

Tabularia lays out the stretch of manuscript in front of you rather than the whole book, so the layout work for the page on screen does not grow with the book. Its own browser benchmark measured that visible-window layout across manuscripts from 10,000 words up to 1,000,000. The novel stays one document; the Outline takes you to any chapter, and setting the Working Scope to Current Chapter closes the canvas up to that chapter when you want less in view. Spellcheck is a switch in Writing Tools if you prefer to draft without underlines.

Three limits are worth knowing before you move:

• That benchmark measured layout on screen, not how long a project takes to open. A very long manuscript still has work to do when it first loads.
• There is no live co-editing. Sharing for review needs the Cloud plan, and a collaborator marks up a draft you send rather than typing alongside you.
• The route in is File → Download → Microsoft Word, then an import. Text and headings come across with your comments and footnotes; tables and images in a DOCX are left out, and the import names each one it dropped.