Google Docs is lagging on my novel. What actually helps?

By Brenn and Lindsay, the two writers who built Inkling

You are not imagining it. Long manuscripts make Google Docs sluggish for a lot of writers. Here is what Google documents, what other novelists report, the fixes worth your time, and how to tell when it is time to move.

It usually starts small. A half-second pause after you type. A cursor that jumps. Then the day you open the manuscript and wait, and wait, while the page fills in. If your novel lives in one Google Doc and it has got long, you are in very good company, and there are things that genuinely help.

We will be careful in this post to separate what Google itself documents, what other writers report, and what is simply worth trying. The internet is full of confident fixes for this problem, and most of them are guesses.

Is it just me, or does Google Docs get slow on long novels?

It is not just you. Novelist Marie Brennan, writing about drafting a 182,000-word book with her co-author, put it plainly on her blog: Google Docs does not always cope well with very large files, and much above 50,000 words you can start having problems with lag. Their answer was to split the draft across nine files of three chapters each.

On the Mythic Scribes forum, a thread titled "Can Google Docs handle novels now?" has writers describing whole-novel files as annoying to load and splitting their books into one document per chapter. That thread is from 2017, and the complaint has not gone away: Google's own help community has a thread titled "Docs slows down at 90,000 words. Is there a workaround?", and writing-app makers now market against it. Dabble's comparison page says Google Docs can start to lag and even crash when a document becomes too long. (Dabble sells a competing app, so read that as a vendor's view. It also, fairly, credits Docs with free, effortless collaboration.)

Notice the numbers do not agree: 50,000 words for one writer, 90,000 for another. That is normal. How a long Doc behaves depends on your computer, your browser, your extensions, and what is in the file. There is no magic word count where everyone hits a wall.

What does Google itself say?

Less than you might hope, but two things are written down.

There is a hard size limit. Google's Drive storage help page says a Google Doc can hold up to 1.02 million characters. Most novels are well under that, so if your Doc is lagging, you have probably not hit the ceiling. You can check: Tools, then Word count, shows characters as well as words, according to Google's word count help page.

Google's fix for big files is to split them. Its "Fix common issues in Google Drive" page says that if a file is too big or close to the limit, you should divide the information into more than one file. The same page points at the usual suspects for slow loading: a weak internet connection, an out-of-date browser (it recommends Chrome and supports the two most recent versions of major browsers), and adblockers or security software interfering with Docs.

That is the official picture. Nothing in Google's help pages explains exactly why a 90,000-word Doc feels slower than a 9,000-word one, so we will not pretend to either.

What quick fixes genuinely help?

In rough order of how much evidence is behind them.

1. Split the manuscript. This is the fix Google recommends and the one novelists actually use. Per chapter keeps each file small. Per part, or a few chapters per file as Brennan did, keeps the splits at story-shaped places so you are not constantly jumping between files. A cheap version: move everything you have cut into a separate "cuts" Doc, and finished early chapters into an "Act One" Doc, so the file you are drafting in stays lean.

2. Test your extensions. Browser extensions that read the page as you type have to process the whole long document too. Grammarly says so about itself: its known-issues page states that documents of thirty pages or more may slow down Grammarly's performance. Turn your extensions off one at a time, reload the manuscript, and see whether the lag changes. If it does, you have found your culprit, and you can switch that extension on only when you need it.

3. Turn off grammar suggestions, and spelling suggestions too if you like. This is the most repeated tip online, and the evidence for it is thinner than its popularity. The documented case is a 2022 bug, covered by BleepingComputer, where a run of repeated words crashed Docs while grammar suggestions were on; the workaround was Tools, then Spelling and grammar, then unticking Show grammar suggestions. Google's spelling and grammar help page explains what those suggestions are (red underlines for spelling, blue for grammar). Whether switching them off speeds up your particular manuscript is something only a test will tell you. It costs nothing, and you can run a full check before you send the draft to anyone.

4. Check the boring things. Google's own list: a different network, an up-to-date browser, a cleared cache, and making sure an adblocker or security tool is not blocking Docs. Closing the forty other tabs does not hurt either.

5. Pageless, honestly. Many writers suggest switching to pageless format. Google's page setup help describes pageless as a layout choice: no page breaks, and no headers, footers or page numbers while it is on. We could not find any evidence that it makes a long Doc faster, or slower. If you are curious, try it on a copy (File, Page setup) and judge for yourself.

A note on document tabs. Since October 2024, Google Docs has had document tabs, and plenty of novelists now keep one chapter per tab. It is a genuinely tidy way to organize a book in one file. Google does not say tabs make a long Doc faster, so treat them as organization, not a speed fix. And one gotcha worth knowing now: when you download a tabbed Doc, Google's tabs help page says the default is the current tab only. Choose All tabs, or your backup is one chapter long.

What does splitting cost you?

Splitting works. It also quietly hands you a second job: being the librarian of your own book.

• No single word count. You add up chapter totals by hand, or keep a spreadsheet.
• No whole-book search. Finding every mention of a minor character means opening every file.
• Reordering is file surgery. Moving chapter 14 before chapter 12 means renaming files or cutting and pasting between Docs.
• Backups multiply. Twenty chapter files are twenty things to export. (If that worries you, our post on never losing a draft has a simple weekly habit.)

None of that is a crisis. Plenty of finished novels were written exactly this way. But if you notice you are spending real time managing files instead of writing, that is the signal.

When is it time to move to a tool built for long fiction?

Google Docs is free, it is everywhere, and nothing beats it for inviting a friend to comment. Those are real strengths, and if the lag is mild, the fixes above may be all you need. Consider moving when:

• You have split the book and miss having it in one place.
• You want chapters you can see, count and reorder as a set.
• You keep your character and world notes in yet more Docs, and flipping between files is breaking your concentration.
• The draft is past the point where you would be comfortable losing it to one account problem. (We wrote about that, calmly, in what happens if Google Docs locks your novel.)

Whatever you look at, ask the same four questions. Can it hold the whole book as chapters, with one total word count? Can I bring my draft in without retyping it? Can I export everything to Word whenever I like, including after I stop paying? And where does my text actually live? Scrivener answers those very differently from a web app, and our Scrivener post is honest about its strengths, including its one-time price. When you are ready to make the switch, we wrote a step-by-step guide to moving a novel out of Google Docs without losing anything.

Where Inkling fits

We built Inkling, so take this as one option, described plainly.

In Inkling a novel is a set of chapters, each on its own page, kept in order (you can move a chapter up or down), with the whole book's word count on the novel itself. Your writing saves to your account as you type. Beside the chapters you get a character builder, a storyboard for scenes, people and places, and word count goals. You can export a story as Word, plain text, or a PDF, or the whole novel as one Word manuscript or a Google Doc with a tab for every chapter.

The honest gaps: Inkling has no real-time co-writing, so if you draft side by side with a partner, Google Docs still wins. It cannot read a .docx file yet. And it is a subscription after the trial: 14 days to experience the full writing desk, build worlds, and be creative, with no card to start, then $9 a month (or $72 a year). If the trial ends and you do not subscribe, nothing is deleted, the desk goes read-only, and you can export any story to Google Docs. See pricing for the details.

If your Doc is lagging today, though, start with the free fixes. Split the file, test your extensions, try the grammar toggle. Then get back to the chapter you were in the middle of.