You've Already Written 60,000 Words. Here's What Actually Works With a Draft in Progress.

Most writing tools are built for people starting a book. You are not starting a book. You are two thirds of the way through one, it lives in a Google Doc that takes four seconds to scroll, and the thought of moving it anywhere fills you with a very specific dread: that you'll lose the formatting, lose the comments, or lose two weeks to setup and never get back to chapter nineteen.

So the question isn't which tool is best. It's which tool can take what you've already got and be useful by this afternoon.

The short answer

• Stay in Google Docs, add ProWritingAid if what you want is line-level editing help, not drafting help.
• Move to Scrivener if the problem is organization: one enormous file you can't navigate.
• Paste chunks into ChatGPT or Claude if you just want a second opinion on a scene and don't mind re-explaining your story every session.
• Novelcrafter if you'll happily rebuild your codex by hand in exchange for model control.
• Sudowrite if you want your existing manuscript read once and turned into something the AI can work from.

The dividing line is whether a tool ingests your draft or just sits next to it.

1. Google Docs plus a browser AI

What most people are already doing: draft in Docs, paste a scene into ChatGPT, paste the result back.

Works because there's no migration at all. Nothing to learn, nothing to move.

Stops working because every session starts from zero. You explain who your protagonist is, what happened last chapter, what your world's rules are, and you do it again tomorrow. At 60,000 words there is more story than you can reasonably paste, so the AI is always working from a fraction of your book and confidently contradicting the rest of it.

2. Scrivener

Import your manuscript, split it into chapters, and you've turned one unnavigable file into a structured project with a binder, a corkboard, and somewhere to keep research.

Works because it fixes the organizational problem completely and it's a one-time purchase.

Stops working because it does nothing with the content. Scrivener will hold your 60,000 words beautifully and has no opinion about them. If your problem is "I can't find anything," this is the answer. If your problem is "I've lost the thread of my own book," it isn't.

3. ProWritingAid

Runs over the draft you already have and flags the sentence-level stuff: echoes, pacing, overused words, dialogue tags, sticky sentences.

Works because it needs no migration and it's genuinely good at what it does. It also plugs into Docs and Word directly.

Stops working because it's an editing tool, not a drafting tool. It'll tell you the sentence is flabby. It won't help you write the next chapter.

4. Novelcrafter

A codex of characters and world elements alongside AI drafting, with your own model connected.

Works because you keep control over which AI you use, and the codex is a real structure rather than a pile of notes.

Stops working because the codex is yours to build. For a 60,000-word draft that means going back through it and entering everyone by hand, on top of setting up an API key.

5. Sudowrite

The one built around the assumption that you might already have a manuscript. There are three separate ways in, and picking the right one matters more than anything else in this article.

Import Novel

Point it at your manuscript and it does two things at once: brings the whole draft in, and builds your Story Bible from it. It reads the book and fills in characters, worldbuilding elements, and a detailed outline on its own.

• Optimized for documents up to 120,000 words
• Focuses on your five to seven primary characters
• Accepts .txt, .doc, .docx, .rtf, and .odt
• Takes a few minutes, up to about ten for a complex manuscript

Google Docs users: File → Download → Microsoft Word (.docx), then import that.

Worth knowing before you run it. Import Novel always creates a new project, deliberately, so it can't collide with a Story Bible you've already built. Characters you never named may come back with placeholder names. And a very long outline can end up saved as separate documents rather than inside the Outline section.

Import Scrivener

If your draft is already in Scrivener, you don't need to flatten it first. In Scrivener go to File → Back Up → Back Up To… and save the project as a .zip. In Sudowrite, click Import Novel and choose Import Scrivener. Your folders, documents, and structure are recreated as they were.

This is the least-known route into Sudowrite and the one that saves the most work, because it means the organizing you already did in Scrivener carries over instead of being redone.

Document Import

Sometimes you don't want any of the above. You have an existing project and you just want this one file inside it.

In a project, click Import in the editor's left bar and pick your file. It creates a single document with the full text, no limit on size, and leaves your Story Bible exactly as it was.

I've already got 60,000 words in Google Docs. Is there anything that can work with a draft I've already started?

Yes, and there are two genuinely different versions of "work with."

Sitting alongside your draft. ProWritingAid, Grammarly, and a browser AI window all do this. They read what you paste and give you something back. Nothing about your manuscript is retained between sessions.

Reading your draft into a structure. This is what Sudowrite's Import Novel does. Download your Google Doc as .docx, import it, and rather than a copy of your text sitting in a new editor, you get a project with a Story Bible already populated from your own book: your characters, your world, your outline, extracted from the 60,000 words you wrote.

The difference shows up on the next chapter you write. In the first version you're still the one carrying the whole story in your head. In the second, when you use Write in a chapter linked to the one before it, Sudowrite reads back through up to 25 linked chapters and up to 20,000 words of your actual prose before it generates a word. It isn't working from your summary. It's working from your book.

Realistic expectation for a 60,000-word draft: about ten minutes for the import, then thirty to sixty minutes reviewing what it extracted. It finds your main cast, not every walk-on. It will have opinions about your outline you disagree with. Fix those, and the setup is done for good.

What happens to my formatting and my comments?

Your text comes across. Google Docs comments and suggestions do not, because they're a Docs feature rather than part of the document text. If your revision notes live in comments, resolve or move them before you export.

The practical move is to keep the Google Doc. Nothing about importing removes it. Treat the original as an archive for a few weeks until you trust the new setup.

Can I get my work back out again?

Yes, and this is worth checking before you commit to any tool.

Sudowrite exports a whole project as a bundled .zip of every document, or as one merged .docx with your documents in the order they appear in the left bar. Individual documents and Story Bible sections can be exported too.

One thing to note: the project .zip export contains your documents, not your Story Bible. If you want the bible as well, export those sections separately.

Should I start a new project or keep writing in the old one?

If you're continuing the same book, import once and continue there. Splitting your draft across two tools is how the continuity errors start.

If you're on book three of a series and books one and two live elsewhere, import them as their own projects and put all three in a Series Folder. Projects in the same series folder share Characters, Worldbuilding, and Outline, and the AI can see them across books. That's what stops book three contradicting book one: not better notes, but book one's canon being visible while you draft book three.

FAQ

Can Sudowrite import a half-finished manuscript? Yes. Import Novel is built for works in progress specifically, including messy ones. The docs describe it as working from a partial manuscript, a complete one, or "a less-than-organized pile of notes." It creates a new project and populates the Story Bible from whatever you give it.

What file types can I import? Import Novel takes .txt, .doc, .docx, .rtf, and .odt. Scrivener projects come in as a .zip backup through Import Scrivener. Document Import handles single files into an existing project with no size limit.

What if my book is longer than 120,000 words? Import Novel is optimized up to about 120,000 words, so a longer manuscript is better split, or brought in with Document Import, which has no size limit, and paired with a Story Bible you build up as you go.

Will importing overwrite the Story Bible I've already built? No. Import Novel always creates a brand new project rather than writing into an existing one, precisely to avoid that. If you want a file inside a project you've already set up, use Document Import, which leaves the Story Bible untouched.

Do I have to start the book over? No. That's the entire point of importing rather than pasting. Your existing chapters are your chapters; the tool reads them and works from them.

The honest recommendation

If your draft is fine and your sentences are the problem, add ProWritingAid to what you already have and don't move anything.

If you can't find things, Scrivener will fix that this weekend.

If you've lost the thread of your own book, and what you actually want is something that has read the whole thing and can help you write chapter nineteen with chapters one through eighteen in view, importing is the step that gets you there.

Sudowrite starts at $10/month for Hobby & Student, and the trial doesn't ask for a credit card. Export your Google Doc as .docx, run Import Novel, and see what it makes of the book you've already written.