The Best Alternatives to Google Docs for Serious Writers

Google Docs is great at what it is: a collaborative document editor. For meeting notes, shared specs, and group editing, it’s hard to beat. But if you’re a writer—someone who actually writes for a living or as a craft—you’ve probably felt its limits.

No real organizational structure for long-form work, no way to manage multiple drafts without duplicating files, and version history that’s technically there but practically useless for tracking how a piece evolved. Google Docs treats your novel the same way it treats a grocery list.

So let’s talk about what else is out there.

Scrivener

The granddaddy of serious writing software. Scrivener gives you a binder-style structure where you can break your project into scenes, chapters, and notes, then rearrange them freely. The corkboard view is genuinely useful for planning, and research materials live alongside your drafts.

The downsides: it looks like it was designed in 2008 (because it was), the learning curve is steep, syncing between devices is fragile (Dropbox-based sync has burned plenty of people), and collaboration is essentially nonexistent.

Best for: Novelists and long-form writers who work solo and want deep organizational tools.

Ulysses

Think of Ulysses as the Mac-native writer’s editor. Clean Markdown-based writing, iCloud sync that actually works, and a library system that keeps everything in one place. The publishing features are solid too—you can push directly to WordPress or Medium.

The catch: it’s subscription-based ($6/month), Mac/iOS only, and its organizational model is still fundamentally linear. You write in sheets and organize in groups, so if you need to explore multiple directions for the same piece, you’re back to duplicating sheets and hoping you remember which is which.

Best for: Mac users who want a polished, distraction-free writing environment with good publishing workflows.

Notion

Notion isn’t really a writing app—it’s a workspace that people use for writing. The block-based editor is flexible, databases can track projects, and the collaboration features are strong. Some writers build elaborate dashboards for tracking submissions, deadlines, and word counts.

But writing prose in Notion feels like writing in a tool that was designed for project management…because it was. The editor is fine for short-form content but gets clunky for anything long, performance degrades with large documents, and there’s something about the infinitely nesting folders that encourages over-organizing instead of actual writing.

Best for: Writers who need to manage the business of writing (tracking submissions, organizing research) more than the writing itself.

iA Writer

This is the minimalist’s choice. iA Writer strips everything away: no formatting toolbar, no sidebars, just you and your text. The typography is beautiful, focus mode dims everything except the current sentence, and it handles Markdown natively while exporting to basically anything.

The limitation is the flip side of its strength—iA Writer is deliberately simple. No project management, no outlining, no way to see multiple drafts side by side. It assumes you know what you want to say and just need a clean place to say it. For first drafts and focused editing sessions, it’s excellent, but for the messy middle of figuring out what your piece actually is, you need something else.

Best for: Writers who value focus and simplicity above all else, especially for short-to-medium-form work.

What’s actually missing

The thing I kept noticing is that they all assume writing is linear. You start at the beginning, write to the end, revise, done.

Real writing doesn’t work like that. You write a paragraph three different ways, try a different opening, explore a tangent that might become the actual point. And in every tool above, doing this means either destroying previous work or managing a chaos of duplicated files and copy-pasted paragraphs.

This is why I’m building Quillium. The core idea is that you should be able to fork any sentence or paragraph—like a Git branch—and keep every version alive simultaneously, not as a mess of tabs but as a structured tree you can navigate. Write three different openings, keep all of them, and decide later—or don’t decide at all and let them coexist.

It’s a fundamentally different model from anything above, and it won’t be for everyone. But if you’ve ever lost a draft you liked because you wrote over it, or maintained a folder of files named intro_v2_alt_MAYBE.md, it might be worth a look.

I’m still in early development. If this sounds like the tool you’ve been waiting for, join the waitlist.