Launch
What is a beta reader? Beta and ARC readers, explained
The readers before the readers — who does what between your draft and your launch, and how to use each without spending a penny you don't need to.
By Jamie Rand · Imprint Digital · 7 min read · Updated 27 July 2026
Between 'the manuscript is finished' and 'the book is launched' stands a small vocabulary of borrowed software jargon — alpha readers, beta readers, ARC readers — that every publishing forum uses and almost nobody defines. The short version: beta readers test your book before it is final, and ARC readers review it as it launches. Used well, the first group saves you an expensive edit's worth of blind spots and the second solves the coldest problem in self-publishing: a launch day with zero reviews.
This guide defines each role properly, shows where the paid professionals fit around them, and walks through running both rounds — including the questions that make beta feedback usable and the review-rules that keep an ARC round on the right side of Amazon.
What a beta reader actually is
A beta reader is a test reader: someone who reads your finished-but-not-final manuscript as a reader, not an editor, and reports the experience — where they were gripped, where they skimmed, what confused them, whom they rooted for. The name is borrowed from software's beta testers, and the analogy holds: they are not there to fix the book, only to tell you truthfully what it was like to read it. That is information you cannot generate yourself, at any price, because you know what every sentence was supposed to do.
Betas read after your own revisions and before professional editing — there is no point paying an editor per word to fix a subplot three beta readers could have told you to cut. They are traditionally unpaid volunteers (fellow writers, genre readers from your communities), exchanged rather than hired; paid 'beta reading services' exist, but what you are buying there drifts toward a manuscript critique, which is an editor's product. Our editing cost calculator shows what the professional passes cost — betas are how you make sure that money lands on a book that already works.
Alpha, beta, sensitivity, editor: who does what
The vocabulary, in order of appearance. An alpha reader sees the rough first draft, sometimes chapter by chapter as it is written — usually one trusted person who can read past the mess. Beta readers see the complete, self-revised manuscript. A sensitivity reader is a specialist beta: someone from a community your book depicts, checking authenticity and harm you cannot see from outside. All of these report experience.
Editors, by contrast, fix craft — developmental editors for structure, copyeditors for the line, proofreaders for the final pass — and they are paid professionals with a different job entirely. The sequence that wastes the least money runs: alpha (optional) → your revisions → betas → your revisions → professional edit → proofread → ARC readers. Each stage catches what the previous one cannot, and none substitutes for another.
Finding and briefing beta readers
You need three to five — enough that patterns emerge, few enough to actually process. One reader's opinion is taste; three readers stumbling at chapter seven is data. Find them where your genre's readers already gather: writing communities and critique-swap groups, genre forums and book clubs, your own early newsletter subscribers. The trade is usually reciprocal reading, and the best betas are readers of your genre, because they know what the promises are.
The brief makes or breaks the round. Give a deadline (three to four weeks is fair), and ask experience questions, not craft questions: Where did you stop reading, and why? What did you skim? Who did you care about, and when did you start? What did you think would happen? Was the ending fair? Never ask 'is it good?' — you will get kindness, which is useless. And when feedback arrives, the rule is: readers are almost always right about where a problem is and almost always wrong about how to fix it.
What ARC readers are — and the review rules
ARC stands for advance review copy (historically 'advance reading copy'): a free copy of the finished book given out before publication so that reviews exist when the book goes on sale. ARC readers are not testing the book — it is done — they are your launch's early audience, and their job, gently invited, is an honest review in launch week. Reviews are self-publishing's hardest currency: they unlock promo sites, reassure browsers, and feed every algorithm that matters.
The rules matter because Amazon polices reviews hard. You may give free copies; you may ask for an honest review; you may not pay for reviews, require a positive one, or review-swap with other authors. The accepted phrasing — 'I received an advance copy and am leaving this review voluntarily' — exists because it keeps everyone honest. Run it clean: a dozen genuine launch-week reviews beat fifty that get purged.
Running an ARC round
Numbers first: for a debut, twenty to fifty ARC readers is realistic, sourced from your newsletter, genre ARC communities and reader teams — expect roughly a third to half to actually review, which is normal and fine. Send copies four to six weeks before launch, remind once near the date, and make reviewing effortless: a direct link, a note that a line or two is plenty.
Most ARCs today are ebooks, distributed free through ARC platforms or direct files. But a short run of printed ARCs — a plain paperback with 'Advance Review Copy · Not for Sale' on the cover — still does what digital cannot: it gets photographed for social media, lands with bloggers and local press, and signals a book taken seriously. That is a classic short-run job; our guide to how many copies to print covers sizing it, and once launch day comes, KDP keywords makes sure the reviews you earned have a listing people can find.
Common questions
- What is a beta reader?
- A volunteer test reader who reads your finished-but-not-final manuscript and reports the reading experience — where they were gripped, confused or bored — before you pay for professional editing. They are readers, not editors: they find where problems are, not how to fix them.
- What is the difference between an alpha reader and a beta reader?
- Timing and state of the draft. An alpha reader sees the rough first draft, often as it is written, and is usually one trusted person. Beta readers come later, reading the complete manuscript after your own revisions, in a small group so patterns in their reactions are visible.
- What are ARC readers?
- Readers who receive a free advance review copy of the finished book before publication, invited to leave an honest review at launch. They are a marketing stage, not a feedback stage — the book is final — and they exist so your launch day has reviews instead of silence.
- Do beta readers get paid?
- Traditionally no — beta reading is a volunteer or reciprocal arrangement between writers and genre readers. Paid services exist, but at that point you are buying something closer to a professional critique, and it is worth comparing the price against a real manuscript assessment from an editor.
- How many beta readers and ARC readers do I need?
- Three to five betas — enough for patterns, few enough to process — and twenty to fifty ARC readers for a debut launch, expecting a third to half to actually review. Both numbers scale up with your newsletter, which is why authors build the list before they need it.
Plan your book with the free tools
Run the numbers, prepare your files and compare your options — then print with real UK book printers.