Last reviewed by Robert Prime — May 2026
Introduction
A beta reader is a genre fan who reads your near-finished manuscript and tells you what's working and what isn't — before you spend on an editor. Done well, three to five beta readers catch most of the structural issues a developmental editor would flag, and they catch them for £0-£50 instead of £1,500+.
Done badly, beta reads waste your time and produce contradictory advice you can't act on. This guide is the version that works.
Where beta readers fit in the workflow
The standard indie workflow:
- Draft complete
- Self-edit pass (read aloud, ProWritingAid)
- Beta readers (3-5 people, 4-6 weeks)
- Revise based on beta feedback
- Developmental editor (optional, depending on budget)
- Revise
- Copy edit
- Proofread
- Publish
Skipping beta readers is fine if you can afford a developmental editor for every book. Skipping the editor and replacing them with beta readers is also fine for some authors. Skipping both is how you end up with 3-star reviews mentioning "needs editing".
How many beta readers and what kind
3-5 betas is the sweet spot. Fewer than 3 and feedback is too narrow. More than 7 and the conflicting feedback becomes paralysing.
The right mix:
- 2-3 genre fans — readers who buy and read this kind of book. They tell you whether the book delivers on genre conventions.
- 1-2 craft-aware readers — other authors, writing-group members, English teachers. They spot structural issues genre fans accept.
- 0-1 target-demographic outliers — if your book is about disability and your other betas are able-bodied, include a disabled reader. If your book is set in Yorkshire and your betas are all London-based, include a Yorkshire reader. Outliers catch authenticity issues.
Avoid: your spouse, your parents, your best friend — they'll be too kind. Family beta reads destroy more books than help.
Where to find beta readers
Free routes:
- Your newsletter list. If you have one. Ask in your launch-prep email: "I'm looking for 5 beta readers — interested?" High-quality respondents because they already like your writing.
- /r/BetaReaders subreddit — active community, established etiquette, free.
- Goodreads "Beta Reader Group" — large group, mostly free.
- Facebook groups: "Beta Readers and Critique Partners" — UK and US groups, free.
- StoryOrigin — author-swap platform, free tier. You read other authors' books in exchange.
- Critique Partners. Reciprocal — you read theirs, they read yours. Best for serious feedback because the other writer understands craft.
Paid routes:
- BetaBooks (betabooks.co) — £20-£50/month — manages beta reading workflow with chapter-by-chapter feedback.
- Reedsy — paid beta readers, £100-£300 per book. Higher quality but you're paying.
- Critique services like Manuscript Wishlist or similar — £50-£200 per round.
For most first-time authors: 3-5 free beta readers via Reddit, Goodreads, or genre Facebook groups is the right starting point.
The brief — where most authors fail
Asking "What did you think?" produces useless feedback. Asking specific questions produces actionable feedback.
A good beta brief:
Project info:
- Title, genre, word count, comp titles (so they know what they're reading)
- Target audience (age, sub-genre fans)
- Where you are in the process — "this is a 4th draft, looking for big-picture issues, not typos"
Timeline:
- When you'll send the manuscript
- When you need feedback by (give 4-6 weeks)
- How to deliver (Google Doc with comments, email document, BetaBooks platform)
Specific questions — pick 5-10 from this list:
- Where did the story drag for you? Mark the chapter or scene.
- Where did you lose track of who someone was?
- Did the protagonist's actions make sense at every point?
- Did the antagonist feel motivated, or like a cardboard cut-out?
- Were there scenes you skim-read? Mark them.
- Was the climax earned? Did the setup pay off?
- Did the romance / subplot satisfy?
- Did the ending feel like a real ending?
- Anything you predicted too easily?
- Any twist that felt cheap or unearned?
- Genre-specific: for thriller, was the suspense building? for romance, did the chemistry land? for fantasy, was the magic system consistent?
- Did anything pull you out of the story (modern slang in historical, anachronism, factual error)?
- Where would you stop reading if this wasn't a beta read?
- Would you recommend this book to a friend who reads [genre]? Why or why not?
Pick 5-10. More than that and betas check out.
One open question at the end:
"What's the one change you'd make to this book?"
That one question often surfaces the deepest issue.
What NOT to ask
- "Did you like it?" — useless. Almost everyone says yes to avoid hurting feelings.
- "Did you spot any typos?" — that's a proofreader's job, not a beta's. Betas focus on story.
- "Should I change X?" — leading question. Get their honest reaction first, then decide.
How to deliver the manuscript
- Google Doc with comment access — most popular. Betas mark inline.
- Microsoft Word with Track Changes — works if your betas are Word users.
- PDF with sticky notes — fine for less tech-savvy betas.
- BetaBooks platform — best for serious beta reads with multiple readers; chapter-by-chapter feedback.
Always: include the brief at the top of the document. Always: thank them in advance.
What to do with the feedback
Read all feedback before making any changes. Wait 2-3 days after reading before deciding what to change — initial reactions distort judgement.
Then:
1. Sort by frequency.
- 3+ betas flag the same issue → almost always fix it
- 2 betas flag → consider seriously
- 1 beta flags → consider, but it might be personal preference
2. Sort by impact.
- Structural issue (saggy middle, weak ending) → fix even if hard
- Scene-level issue (confusing chapter, weak dialogue) → fix
- Sentence-level issue → save for copy edit
3. Resist defensiveness.
- Your gut reaction to bad feedback is "they didn't read it carefully" or "they don't get the genre". Sometimes true. Usually defensive.
- Sit with the feedback for a few days. Re-read the relevant section. If three readers got confused at the same place, the section is the problem, not the readers.
4. Don't try to please every beta.
- Some feedback contradicts other feedback. Pick the version that serves your book best.
- Betas are unpaid genre fans, not the book's directors. You make the final call.
How long beta reading actually takes
A typical 90,000-word novel: 4-6 weeks beta period.
- Week 1: betas read first half
- Week 2-3: betas finish
- Week 4-6: betas write up feedback
If you give betas 2 weeks, you'll get rushed, surface-level feedback. If you give 8+ weeks, half of them will forget and not deliver.
What you owe the betas
- A thank-you. Always.
- A free finished copy when the book launches.
- Credit in the acknowledgements if they want it (some prefer not to be named).
- Reciprocity if reading-swap. Read their work back with the same care.
- Realistic expectations. Don't ask betas to be editors, copy editors, or proofreaders.
What you don't owe:
- Promises to act on every comment
- A free ARC for life
- A defense of your choices
UK considerations
- UK reader expectations differ on slang, setting, idiom. UK-set fiction is best beta-read by at least 2 UK readers. US-set fiction by UK authors should include at least one US beta.
- UK Society of Authors has a beta-reader recommendation network for members.
- Alliance of Independent Authors (ALLi) has weekly beta-swap threads on the member forum.
- Pay-for-beta services are GDPR-relevant. If you collect beta reader emails, you're a data controller. Use a privacy policy.
Common mistakes
- Sending a too-early draft. Betas should see a near-final draft. A first draft with obvious issues wastes their time and yours.
- Sending to too many betas at once. 3-5 is enough. 10+ produces conflict you can't act on.
- Vague brief. "Let me know what you think" gets useless feedback. Be specific.
- Asking for line-edits. Betas aren't paid editors. Don't ask them to fix prose.
- Arguing with feedback. Your book benefits when you listen, not when you defend.
- Not following up. Some betas vanish. Send one polite reminder; replace them if no response.
- Treating betas as free editors. They're early readers, not professionals. Adjust expectations.
The bottom line
3-5 beta readers, 4-6 weeks, specific brief with 5-10 targeted questions, no family/friends, sit with feedback before acting, fix only what 3+ betas flagged plus the high-impact things you privately agree with.
A good beta round saves you 40-70% of what you'd otherwise pay a developmental editor to find. A bad beta round wastes everyone's time. The difference is the brief.
Frequently asked questions
How much should I pay beta readers?
Free is fine for friends-of-genre. £20-£50 thank-you (gift card) is generous for free betas. £100-£300 for paid beta services. Don't pay individuals for beta reads — that crosses into "review-for-pay" territory which is dangerous on Amazon.
What if betas all hate the book?
That's useful — uncomfortable but useful. Either the book has fixable issues you should address before publishing, or you're in the wrong genre for these readers. Either way, better to know now than after 50 negative reviews.
Can the same betas read book 2, 3, 4?
Yes — and they should. Building an ongoing beta team across a series saves time per book and produces consistent feedback.
Should I beta-read the book myself first?
Yes — self-edit pass before sending. Sending a draft with obvious typos and structural issues wastes the beta's time.
What about sensitivity readers?
Different role — see the dedicated guide. Sensitivity readers focus on representation accuracy; betas focus on story.
