What Is a Book Blurb?

Book BlurbProduct description

A book blurb is the short sales description on a book's product page — the 150 words that decide whether a shopper who found your metadata clicks buy or bounces. Good blurbs name the reader, promise one outcome, and end with proof. It is copywriting, not summary: sell the transformation, never the table of contents.

Shape: hook (reader + outcome) → stakes (cost of inaction) → proof → call to buy.

What job does the blurb do?

The blurb converts attention you already earned. Cover and title stop the scroll, categories and keywords deliver the shopper — and then the blurb has about fifteen seconds to turn interest into a purchase. Everything before it is discovery; everything after it is the buy button.

That narrow job explains what the blurb is not. It is not a synopsis: summarizing chapters answers questions nobody asked and spoils the curiosity that sells. It is not an author bio either — credibility belongs in one line near the end, not the opening. The blurb sells the reading outcome, and every sentence either sharpens that outcome or gets cut.

For short nonfiction the outcome is concrete — a system, a result, a finished asset. For fiction it is emotional — a situation the reader wants to live inside. Same structure, different currency: promise the transformation in the reader's terms, whatever the genre.

What structure do strong blurbs follow?

Open with a hook that names the reader and the outcome in two sentences. 'Freelancers who lose Fridays to admin' beats 'this book is about productivity' because the right shopper self-identifies instantly and the wrong one leaves — both are wins. Specificity filters before it persuades.

Raise the stakes next: what does staying stuck cost? A sentence on the price of inaction — lost clients, another year of clutter, the course that never becomes a product — gives the outcome its urgency. Then deliver proof in one line: your experience, your numbers of students or readers, or the method's track record, stated plainly without superlatives.

Close inside the book, not beside it. End with the first step the reader takes on page one, or the single question the book answers from chapter one. Shoppers buy beginnings they can picture, not endings they must trust — so sell the doorway, not the whole house.

BlockJobLength
HookName the reader and outcome1–2 sentences
StakesPrice the status quo1–2 sentences
ProofOne credible line1 sentence
DoorwaySell the first step1–2 sentences

How long should a blurb be, and how should it look?

Aim for 100–200 words for short nonfiction: long enough to make the case, short enough to read on a phone without scrolling. KDP allows far more description text than you should use — the ceiling is a technical limit, not a target. Shoppers skim; every paragraph beyond the third halves the readers who reach it.

Format for skimmers. Short paragraphs, one idea each, with the hook visible above the 'read more' fold on mobile. KDP descriptions accept basic HTML, so line breaks and bold do real work: bold the outcome sentence, break before the proof line, and let white space carry the rhythm. A wall of unbroken text reads as unfinished, whatever it says.

Write it last and test it first. Draft the blurb after the manuscript exists so every promise is checkable against real chapters, then read it aloud to one ideal reader before publishing. If they cannot repeat the promise back in their own words, the hook needs another pass.

An example: before-and-after for a budgeting workbook

Before: 'This comprehensive workbook covers budgeting fundamentals, expense tracking methodologies, and savings strategies across twelve detailed chapters with exercises.' Accurate, thorough, and utterly buy-proof — it describes the table of contents to a shopper who wanted a result.

After: 'Couples who fight about money: build one shared budget in a single weekend. Every chapter ends with a fill-in worksheet, so Monday starts with a plan instead of a argument. From a coach who has run budgeting workshops for 400 couples — open to the first worksheet and start tonight.' Same book, different physics: reader named, outcome dated, proof attached, doorway visible.

The rewrite rule is mechanical, not mystical. Swap each feature sentence for its outcome, attach one proof line, and end on page one. Run every blurb draft through that filter twice and the copy tightens itself.

Rewrite filter

Feature: 'Twelve chapters with exercises.' → Outcome: 'Every chapter ends with a fill-in worksheet, so Monday starts with a plan.' Feature: 'Comprehensive coverage.' → Proof: 'From a coach who has run budgeting workshops for 400 couples.'

What mistakes kill an otherwise good blurb?

Superlatives without evidence — ultimate, definitive, groundbreaking — train shoppers to disbelieve the next sentence too. One specific proof line outperforms five adjectives, and honest-scope copy converts the skeptical readers who actually buy nonfiction. If a claim cannot be checked, cut it.

Genre mismatch is the quieter killer: a playful blurb on a serious grief memoir, or corporate stiffness on a cozy mystery. Shoppers use tone as a quality signal, matching blurb voice against cover and A+ Content imagery. When the three disagree, the shopper trusts none of them.

Finally, the orphan blurb: copy written before the manuscript and never reconciled. Promises drift from contents, chapter counts change, and the doorway scene describes pages that no longer exist. Re-read the blurb against the finished files during your launch checklist pass — it takes ten minutes and catches lies you told yourself months ago.

  • Reconcile drafts with How to Create an Ebook so the blurb matches finished files.
  • Name the reader in sentence one — never open with 'this book'.
  • Trade every adjective for one checkable proof line.
  • Match blurb tone to cover and interior voice.
  • Reconcile the blurb against finished files before launch.
  • Keep it under 200 words unless the genre demands more.

Questions, answered

Turn one idea into a finished book

Free to start · No credit card · You own the output

← Back to the glossary