Writing a web serial in Google Docs: how far it goes

There is a particular Sunday that happens to serial writers. You are eleven chapters into an arc, you need to check what you said about a character's brother, and you cannot remember which of your 140 documents it was in. You spend forty minutes in Drive search. You do not write anything.

Nothing broke. Google Docs did exactly what it does. It just stopped being enough somewhere back around chapter sixty, and nobody sent a notification.

What Google Docs gets right

It is worth being honest about this, because most of the advice telling you to switch is written by people selling the alternative, and the case for staying is stronger than they admit.

Sharing actually works. You send a link. Your beta reader opens it. There is no account to create, no invitation to accept, no seat to pay for. Every other tool in this space, including ours, asks for more than that, and for a lot of writers it is the single feature that decides everything.

It is free, and it is not going anywhere. Writing tools come and go, and some of them take your work with them. Docs will outlive most of the companies telling you to migrate off it.

The editor is genuinely good. Autosave you never think about, revision history you never configured, comments and suggestions that work properly, and it runs on a Chromebook, a phone, and a library computer.

Collaboration is best in class. If you write with a partner, real-time editing in Docs is more reliable than almost anything purpose-built.

None of that is faint praise. If you are forty chapters into a serial and it is working, the correct advice is to keep going.

The setup that buys the most time

Before the argument for leaving, here is how to make Docs last as long as it can. This costs an hour once, and it is worth doing even if you never move.

One document per chapter, numbered with leading zeros. 007 - The Tideward Gate, not Chapter 7. Drive sorts filenames as text, so 10 sorts before 2 without the padding, and by chapter 100 your folder is unusable. Three digits from the start.

Number by tens if you are still drafting. 010, 020, 030. When you need a chapter between two others, it becomes 015 instead of renaming every file after it.

One index document, pinned to the top of the folder. A table: chapter number, title, one-line summary, POV character, and the date you posted it. This is the single highest-value document you will keep, because it is the only thing that answers "which chapter was that in" without opening anything. Update it when you post, not later.

A separate bible document, with one heading per entity. Use the outline pane, which is what makes a long reference document navigable at all. Keep it in the same folder.

Never let a chapter live in the same file as another chapter. The temptation to keep an arc together is strong and it ends badly, for reasons in the next section.

That setup will comfortably carry you to a hundred chapters. Plenty of finished serials never needed more.

The hard limit

There is one boundary in Google Docs that is not a matter of taste, and it surprises people who consolidated their chapters into one file.

A single Google Doc holds up to 1.02 million characters. That is Google's own published figure. In ordinary English prose, counting spaces, that works out to roughly 180,000 words.

For a serial at 2,000 to 2,500 words a chapter, that is somewhere between 72 and 90 chapters in one document. Not a soft slowdown. A ceiling.

You will feel it long before you hit it. Documents in the high hundreds of thousands of characters get slow to open, laggy to type in, and unreliable on a phone. The outline pane, the thing that made the document navigable, becomes a scroll of its own.

This is the one genuine gotcha, and it only bites the writers who did the natural thing and kept an arc together in a single file. One document per chapter, and you will never meet it.

Where it stops

The limit above is fixable. These are not.

Search finds files, not answers. Ctrl+F searches one document. Drive search finds every document containing "Ellis" and hands you a list of forty filenames. What you wanted was the sentence, and which chapter it was in, and what you had said about him before that. Three different questions, and the folder can answer none of them.

Order lives in filenames. Your chapter sequence is a naming convention held together by your own discipline. It works until the day you are tired and save something as Chapter 88 draft FINAL, and then it works slightly less.

Progress is per document. Docs will tell you the word count of the file you have open. It has no idea you have written 340,000 words this year, or that you averaged 4,100 a week until March and 1,800 since.

Revision history has no names. You can scrub a document's timeline, but you cannot say "compare this against what I posted", because nothing marked what you posted. For a serial, where the published version is the canon, that is the version that most needed marking.

Beta reader comments scatter. Forty documents, forty comment threads, no list of what is still open.

Each one of these is survivable. They compound, and what they compound into is that Sunday.

The problem no folder fixes

Here is the one that no naming convention, template or add-on has ever solved, and it is the reason this article exists.

A document says what is true. It cannot say when it became true.

Your bible has a heading for Ellis. Under it: Rank: Captain. That was accurate when you wrote it at chapter 20. At chapter 80 he was stripped of the rank in a scene you were proud of. The bible still says Captain, and it will keep saying Captain, because you only open it when you have forgotten something, and you have not forgotten that scene.

So the entry sits there quietly wrong until the day you check it for something else and believe it.

You can fight this in Docs. People do. They keep a changelog under each entity, or a dated bullet list, or a second table of "what changed when". It works for a while, and it decays, because every one of those is a discipline you are imposing on a tool that has no idea what a chapter is.

The question you actually need answered while writing chapter 81 is not what is true about Ellis. It is what was true about Ellis at chapter 80. A document cannot hold that, no matter how you format it. It is not a formatting problem.

There is more on the method itself, and on which facts are worth tracking at all, in keeping continuity straight past chapter 100.

When to move

Not at a chapter count. The number is different for everyone and depends on how many named characters you are carrying.

Three signals, and one is enough:

1. You have started avoiding scenes. Not because they are hard to write, but because they involve a character whose details you would have to go and look up. This is the expensive one, because it changes the story you tell.

2. You look things up more than once a session. Individually a two-minute tax. Across an arc it is most of a writing day, and it lands during drafting, which is the worst time to lose momentum.

3. A reader has corrected you twice. Once is a slip. Twice means the record you are working from is no longer reliable, and everything you write on top of it inherits that.

If none of those is happening, your setup is working. Go and write the next chapter.