How to Write a Book Description for Amazon (Step by Step)

A good Amazon book description opens with a one-line hook, shows the stakes (fiction) or the promise (nonfiction), and ends with a clear reason to buy. Keep it to a few short paragraphs, format it so it's easy to scan on a phone, and stay well under KDP's 4,000-character limit. The steps below take you from a blank field to a finished, formatted description.

What you need before you start

Have these ready before you open the description field in KDP:

• Your genre and the books you're shelved next to. Pick three or four recent bestsellers in your category and read their descriptions. You're learning what readers in that genre expect, not copying.
• A one-sentence summary of your book. If you don't have one yet, write a logline first. It becomes the backbone of your description.
• Your main character and their problem (fiction), or your reader and their problem (nonfiction). You need to know whose story this is and what's at risk.
• The comparable titles or reader promise you want to signal. For example, "for fans of slow-burn small-town romance" or "for new managers who've never run a meeting."
• A plain text editor. Draft outside KDP so you don't lose work and can count characters.

The description is sales copy, not a summary. It's close to a back-cover blurb, and much of the same craft applies. If you've already written one, start from it. Our guide on how to write a book blurb covers the shorter print version.

Step 1: Write a hook for your Amazon description

The hook is your first line. On the product page, Amazon shows only the opening of your description before the "Read more" link, so this line has to earn the click.

A strong hook does one of these things:

• States a situation with a twist. "The ferry left with forty-one passengers. It arrived with forty-two."
• Names a specific problem the reader has. "You've read the productivity books. Your inbox still owns your mornings."
• Introduces a character at a turning point. "Mara has kept the lighthouse lit for eleven years. Tonight, someone else turned it off."

Write five to ten versions. Then cut every word that doesn't add tension or clarity. Avoid opening with the character's name and backstory ("Jane Smith grew up in a small town…"). That's setup, not a hook.

Avoid vague praise of your own book, too. "A gripping, heart-pounding thriller" tells the reader nothing they can picture. Show what makes it gripping instead.

Step 2: Show the stakes or the promise

This is the second paragraph, and it answers the reader's question: why should I care?

For fiction: show the stakes

Stakes are what your character loses if they fail. Use this pattern:

1. Who the protagonist is (one or two details, not a biography).
2. What goes wrong (the inciting event).
3. What they must do about it.
4. What happens if they fail.

Keep it to the first act or so. Readers want the setup and the danger, not the ending. Don't reveal twists from the second half.

In romance, the stakes are usually emotional: why these two people shouldn't be together, and what each risks by trying. Mysteries and thrillers put the stakes on time, danger and who might be next.

For nonfiction: state the promise

Nonfiction buyers want to know what changes for them after reading. Use this pattern:

1. Name the problem in the reader's own words.
2. Name what they've already tried that didn't work (optional, but it builds trust).
3. State what the book gives them, as specifically as you honestly can.
4. List three to six concrete takeaways, often as bullet points.

Be specific, and don't overpromise. "A weekly planning method that fits on one page" is better than "transform your life." Never claim results you can't stand behind.

Step 3: Structure the rest of the description

Once you have the hook and the stakes or promise, the remaining parts are short. Here's how the full structure usually breaks down:

Part	Fiction	Nonfiction	Typical size
Hook	A situation, twist or character at a turning point	The reader's problem in one sharp line	1–2 lines, often bold
Stakes or promise	Who, what goes wrong, what's at risk	What the book gives the reader	1–2 short paragraphs
Proof or texture	Tone, setting, tropes readers look for	Bulleted takeaways, author's relevant experience	3–6 bullets or 1 paragraph
Positioning	"For fans of…", series info, heat level or content notes	Who the book is for (and who it isn't for)	1–2 lines
Call to action	"Start reading today" or similar	"Scroll up to get your copy" or similar	1 line

A few notes on the later parts:

• Tropes and comps help fiction. Readers search for things like "enemies to lovers" or "locked-room mystery." Naming them is useful if your book truly delivers them.
• Author credentials help nonfiction. One line on why you're qualified is enough. The full story belongs in your author bio. See how to write an author bio.
• Keep the call to action short. One line. It's a nudge, not a speech.

You don't need every part. A literary novel might be hook, two paragraphs and nothing else. A practical guide might be hook, one paragraph and a list.

Step 4: Decide how long your Amazon book description should be

KDP's description field allows up to 4,000 characters. That's a ceiling, not a target.

Most effective descriptions use a fraction of that space. Aim for something a reader can take in within a few scrolls on a phone:

• Fiction: often 150–300 words. Enough for a hook, stakes and positioning.
• Nonfiction: often a bit longer, because bullet points of takeaways add length without slowing the reader down.

These ranges are common practice, not an Amazon rule. Look at the bestsellers in your category and match what readers there are used to.

Two practical points:

• Character counts may include formatting. If you add HTML tags, they can count toward the limit. Leave a buffer.
• The opening matters most. Since only the first part shows before "Read more," your hook and first stakes line are doing most of the selling. A long description with a weak opening still loses.

Step 5: Format your book description with HTML on KDP

A wall of plain text is hard to read. KDP lets you add basic formatting to the description, either through the editor in the description field or by using a limited set of HTML tags.

At the time of writing, KDP's help pages list supported tags that include:

• <b> and <strong> for bold
• <i> and <em> for italics
• <u> for underline
• <p> for paragraphs and <br> for line breaks
• <h4>, <h5>, <h6> for small headings
• <ul>, <ol> and <li> for bulleted and numbered lists

Larger heading tags, colors, fonts, links and images aren't supported. KDP updates its tools from time to time, so check the description formatting page in KDP's help section before you publish.

Here's a simple formatted structure:

<p><b>The ferry left with forty-one passengers. It arrived with forty-two.</b></p>
<p>First paragraph of stakes...</p>
<p>Second paragraph of stakes...</p>
<ul>
<li>A locked-ship mystery</li>
<li>A dispatcher who trusts numbers more than people</li>
</ul>
<p><i>For fans of twisty, small-cast thrillers.</i></p>

Formatting tips that help readers:

• Bold the hook. It's the line you most want read.
• Use short paragraphs. Two to four sentences each.
• Use bullets for nonfiction takeaways, not for fiction plot points.
• Use italics sparingly, for a tagline or comps line.
• Don't bold everything. If every line shouts, nothing stands out.

If you'd rather not type tags by hand, paste your text into the KDP description formatter and copy the formatted result. After you save, open the live product page on both desktop and phone to confirm the formatting displays the way you expected.

Step 6: See what a finished description looks like

Here's a complete example for an invented thriller, so you can see every part working together.

The ferry left with forty-one passengers. It arrived with forty-two.

Ines Kovač has dispatched the overnight ferry from Split to Ancona for six years. She counts every ticket, every car, every crew shift. Numbers don't lie. People do.

So when the morning manifest shows one extra passenger and no one aboard admits to being that person, Ines does what no one asks her to do. She starts asking questions. Within a day, a crew member is missing, the ship's camera footage has been wiped, and the ferry company wants the whole thing filed as a clerical error.

Ines has seventy-two hours before the ship sails again with the same crew. If she can't find out who walked off that ferry, and why, she won't be the only one counting the passengers who don't come back.

• A tight, locked-ship mystery
• A heroine who trusts spreadsheets more than people
• Short chapters and a ticking clock

For readers who like small-cast, twisty thrillers set somewhere you can almost smell the sea.

Start reading tonight.

Notice what it does: a hook with a twist, a character in two lines, the inciting event, a deadline and a consequence. The bullets add texture, the comps line positions it, and it ends quickly.

A nonfiction version follows the same shape. For a book on meal prep for night-shift nurses, the hook might be "Your shift ends at 7 a.m. Your body thinks it's dinnertime." Then a short paragraph on the problem, and bullets with what's inside: the weekly prep plan, the break-room snacks, the grocery list.

If you're stuck on a first draft, the book blurb generator can give you raw material to rework into your own voice. If you write your book with Inkora, the publishing kit includes a draft description alongside keywords and BISAC categories, which you can edit before pasting into KDP.

Step 7: Add it to KDP and improve it over time

1. In your KDP Bookshelf, open the book's details page (eBook or paperback).
2. Paste or type your description into the description field and apply your formatting.
3. Save and continue through the rest of the setup. Our Amazon KDP publishing guide walks through every field.
4. After the book is live, check the product page on a phone and a computer.

You can edit the description after publishing. Changes go through KDP's review again, so allow time before they appear. That makes the description one of the easiest things to test. If your book gets page views but few sales, rewrite the hook first, since it's the part most readers actually see.

Make one change at a time and give it a few weeks. Then compare your sales and page reads in your KDP reports.

The description works alongside your other metadata. Keywords and categories bring readers to the page, and the description persuades them once they're there. See how to choose KDP keywords for that side. Inkora's Publishing Hub has a step-by-step KDP checklist so you don't miss a field, though you upload and publish in your own KDP account.

Common problems and fixes

The description reads like a plot summary. Cut everything after the first act. Rewrite each paragraph around one question: what's at risk? If a sentence doesn't raise tension or explain the stakes, delete it.

The hook is buried in the second paragraph. Many first drafts warm up before getting to the good part. Look for your strongest line, wherever it is, and move it to the top.

The formatting shows up as raw tags on the product page. This usually means a tag isn't supported or isn't closed properly. Check that every <p>, <b> and <li> has a matching closing tag, remove any tags outside KDP's supported list, and save again.

KDP rejects or flags the description. KDP's content and metadata guidelines restrict things like contact details, time-limited promotions and price mentions in the description. Read the current guidelines in KDP's help pages, remove anything that breaks them, and resubmit.

It's too long and you're close to the limit. Remove adjectives first, then backstory, then duplicate bullet points. A shorter description with a sharp hook nearly always reads better than a full one.

It sounds like every other book in the genre. Generic phrases ("a thrilling ride," "you won't be able to put it down") blur together. Replace them with one specific detail only your book has: a setting, a job, a rule, a line of dialogue.

Sales didn't change after you rewrote it. The description may not be the problem. Check whether your cover, price, categories and early reviews match what readers in your genre expect. Change one thing at a time so you can tell what helped.

Write the hook first, the stakes or promise second, and cut the rest down to what earns its place. Format it for a phone screen, check the live page, and treat the description as something you can keep improving after launch.