Skip to main content

Beta readers and editors

Letting beta readers and editors into a book without handing over the text, and sorting out what they send back.

Other people in your manuscript

A book stops being private the day someone else reads it. These answers cover that stretch: letting readers in without letting them rewrite anything, collecting what they say, and folding an editor's changes back into the tool you actually write in. Each starts with Google Docs, Word, or Scrivener as they are.

Two of them are about trust rather than workflow. One covers what to do when Google restricts a manuscript it has flagged. The other asks whether the company holding your draft is training AI on it, and how to check for yourself.

The thread is control. Who can change the text, who decides which changes stay, and where the only copy lives are separate questions, and each page says plainly which of them a setting answers and which it leaves open.

The answers

Try it on your own manuscript

Nothing is metered: as many projects as you like at any length, the outline and minimap to move through them, drafts and markup mode for revising, snapshots to return to, sheets and timelines beside the page, and export to DOCX, PDF, EPUB, HTML, Markdown, plain text and Fountain. Bring in what you have already written and read it back as a book.

The Cloud plan is $18 a month, or $172.80 a year, and adds backup, sync across your devices, sharing a manuscript for review, and publishing your work as a web page — the readers and collaborators you invite do not need a paid account of their own. Tabularia is in Public Beta and shipping steadily; the release notes record what has landed.