Google Docs vs Scrivener: What I Use (and What I’d Recommend to Writers Who Hate Chaos)
When two tools go to war...
Affiliate notice: If you decide to buy Scrivener via the link in this post, I may earn a small commission. It won’t cost you anything extra. I only recommend tools I’ve actually used—and occasionally sworn at.
Let’s compare two tools that couldn’t be more different:
Scrivener (the writing cockpit) vs Google Docs (the virtual napkin I sometimes publish from)
I’ve written books, serials, and digital guides in both. I’ve published from both. And I still use both—depending entirely on the type of chaos I’m managing.
Here’s what they do well, what they don’t, and how I decide which one gets the job.
Google Docs
Simple, free, and just got a little more powerful.
What It Does Well:
New: You can now export EPUB files directly—ideal for Kindle publishing with zero extra software
New: Google Docs now supports tabs, letting you keep outlines, drafts, and notes in one window
Auto-saves to the cloud across all devices
Easy to share with editors, collaborators, or that one friend who still uses “track changes” as a threat
Great for Substack content, short fiction, novellas, and writing that’s going live soon
What It Doesn’t:
Longform structure is a mess—you’ll be scrolling forever
No built-in version control or scene manager
Formatting quirks (page breaks, footers, indents) appear when you least expect them
No plotting tools, corkboard, or goal tracking
Collaboration is good, but chaotic if too many people are in it at once
Scrivener
Designed for writers who need control, structure, and multiple colour-coded subplots.
What It Does Well:
Split your project into scenes, chapters, and acts—then move them around like digital index cards
Keep research, drafts, timelines, and notes in one place
Visual views: corkboard, outliner, and label/tag filters
Customisable word count goals and deadlines
Compile/export system creates publish-ready files (with patience)
One-time purchase (no subscription)
What It Doesn’t:
Cloud sync exists—but only via Dropbox and it’s... fragile. Treat it like an unreliable uncle.
No real-time collaboration
Mobile version (iOS only) is limited
The learning curve for the compile function is steep—you’ll get there, but not before googling “why is Scrivener trying to destroy my life”
How I Actually Use Them
I plot big fiction projects in Scrivener. If it’s got multiple POVs, a twist at chapter 17, or a moodboard, it’s in there.
I draft and publish novellas, guides, and Substack content in Google Docs—it’s faster, simpler, and integrates with everything.
When I want to format a novella for KDP in an afternoon? Google Docs.
When I want to build an interconnected fiction universe across 3 stories and two timelines? Scrivener.
Thinking of Getting Scrivener?
You can grab it via my affiliate link here. It’s a one-time purchase (no subscriptions), and if you like structure, scene boards, and neatly tagged chaos—it’s worth it.
I only recommend tools I use. This one’s helped me write better fiction, plan launches, and feel like I vaguely have my life together.
You can also have a look at my No Fluff Guide to Scrivener HERE.
Or How I Published My First Novella Using Google Docs Guide HERE.
If you just need to get a novella online and send out a post by Friday, Google Docs has everything you need—including EPUB export now. You might even get away with the same file for KDP.
Want my templates for both? They’re available for paid members.
And if you’ve ever used Google Docs to format a book with 12 tabs open and a feral hope it would all just “sort itself out”, you're not alone.
— H.J.
