guideStep 4 of 20

Keeping your manuscript safe when you share it

The moment you start handing your manuscript to strangers — betas, ARC readers, swap partners — the same worry shows up: what if someone steals it? It’s worth taking seriously, but not worth losing sleep over. Here’s what you’re actually protected by, and the handful of easy steps that let you share with peace of mind.

The reassuring part first: your work is copyrighted automatically the moment you write it down. In the UK, the US and most of the world, you own the copyright to your book the instant it exists in a fixed form — you don’t have to register anything, pay anything, or add any symbols to be protected. Someone copying your manuscript is infringing your rights from day one.

Some countries offer optional registration that gives you extra legal muscle if you ever had to take someone to court — in the US, for example, you can register with the Copyright Office — but that’s a bonus, not a requirement for owning your work. The details vary a lot by country, and I’m not a lawyer, so treat this as the general shape of things and check your own jurisdiction. Your national copyright office is the place to do that — the UK’s guidance and the US Copyright Office are good starting points if either applies to you.

The honest reality: outright manuscript theft is rare. The far more common “problem” is just a draft getting forwarded further than you intended. The steps below are mostly about preventing that — casual oversharing — which is easy and worth doing.

Locking down a Google Doc

The simplest free way to share is a Google Doc, and you can make it much harder to copy:

  1. Set people’s access to Viewer or Commenter — never Editor.
  2. Click Share, hit the gear icon, and untick “Viewers and commenters can see the option to download, print, and copy.”
  3. Share with specific Google accounts, not “anyone with the link.”
  4. Set an access expiration date so old copies don’t drift around forever.

That turns off downloading, printing and copy-paste straight out of the document, which is the most likely way text leaks. Google’s own walkthrough is here.

Be honest with yourself about what this does, though: it stops casual copying, not someone determined with a phone camera or a screenshot key. Nothing fully prevents that — and the same is true of every published book on Amazon. It’s a deterrent, not a vault.

Platforms built for sharing safely

If you’d rather not wrangle a pile of Google Docs — and for bigger beta or ARC rounds you really wouldn’t — there are tools designed for exactly this. They let readers read in the browser only, with no download at all, plus access controls and feedback collection in one place:

  • StoryOrigin — its Beta Copies feature serves your manuscript chapter by chapter in the browser (no download), collects per-reader feedback, and lets you set or revoke access anytime. The beta tool needs the standard plan (around $10/month), and the same platform handles ARC delivery later.
  • BetaBooks — purpose-built for beta reading: share the manuscript, track who’s read what, and triage all the feedback in one dashboard instead of a hundred email threads. Free for one book and three readers, paid tiers above that.
  • BetaReader.io — browser and app reading with no downloads, plus genuinely useful analytics showing exactly where readers slowed down or dropped off. It also has a reader marketplace, handy if you’re starting with no audience. Free for one manuscript and three readers.

For the later ARC stage, BookFunnel and StoryOrigin both deliver files with per-reader watermarking baked in — but that’s a story for the ARC guide.

One note if you write under a pen name: check how a platform handles author identity before you commit, since some tie everything to one account or charge per pen name. Keeping a pen name properly separate is its own consideration.

Watermarking and good habits

Whatever you use, a few small habits go a long way:

  • Watermark each copy. Put the reader’s name or email in the footer of their copy, with a line like “Confidential review copy — please don’t share.” If anything ever leaks, you can trace it to a person — and just knowing that keeps most people honest.
  • Never send your master file. Share a copy, always, so a stray edit or deletion can’t touch your working manuscript.
  • Keep a list of who has which copy, so you can revoke access cleanly when the round ends.
  • Add a copyright line to the first page — © 2026 Your Name. All rights reserved. It does nothing legally you don’t already have, but it signals you’re paying attention.

None of this should make you precious about sharing. The feedback a good beta round gives you is worth far more than the small, mostly theoretical risk — so protect sensibly, then send it out and listen.

With your manuscript polished by your own passes, pressure-tested by beta readers, and shared safely, there’s one money question left in this phase: which kind of professional editing, if any, is actually worth paying for — and how to get it cheaply. That’s next.