After copying a description into KDP, compare the entered text with the accepted copy and inspect its formatting through the available editor controls. Use only supported formatting, check the current character count, and review the content restrictions separately. A description that looked correct in a writing app may need adjustment in the publishing field.
Preserve an accepted copy before transferring it
Save the approved wording in an identifiable file or record before pasting it into the publishing interface. Include the edition and revision date so it can be compared with the manuscript it describes. This gives the author a reliable reference if the transfer changes spacing, emphasis, or punctuation, or if an older draft is copied by mistake.
Separate wording approval from formatting approval. A description can have accurate content while still displaying poorly in its destination field. Conversely, attractive formatting can conceal an obsolete promise. Keep both review questions visible so a visual cleanup does not become an excuse to rewrite accepted facts without checking them against the book.
Use the destination’s supported formatting
KDP provides a description editor and supports a limited set of basic HTML formatting. Consult its current list rather than assuming that all formatting from a word processor or website can be carried over. Use only the presentation needed to make the description easy to read, and avoid importing an entire page design into a field intended for book copy.
A source document may contain visual styles that have no direct equivalent in the destination. Decide how to represent their purpose using the supported options. A short emphasis or a clear list may communicate the same hierarchy without attempting to reproduce every detail. The goal is a readable description, not an exact replica of the editing application's appearance.
Compare text after the paste
Read the entered description against the accepted reference. Check the opening, paragraph boundaries, list items, punctuation, and ending. A missing final sentence can be easy to overlook when the first paragraphs appear correct. Confirm that no comment, temporary note, or alternative wording was included during the copy operation.
Look for changes that affect meaning as well as appearance. A broken list can make separate features read as one claim, while missing punctuation can change the relationship between phrases. Resolve the issue in the entered copy and preserve the corrected accepted version. Do not assume that a successful paste action proves the content arrived intact.
Inspect source and character count when troubleshooting
KDP's current guidance explains that formatting markup counts toward the description's character limit. Use the field's count and source view where available to understand what has actually been entered. A visually short description may contain more underlying characters than expected, especially after several formatting passes.
When the appearance is wrong, inspect the relevant formatting structure instead of repeatedly adding spaces or blank lines. Work on a preserved copy and simplify the affected section if needed. Avoid making unrelated changes while diagnosing one problem. A controlled correction makes it easier to determine whether the issue came from the transferred content or a later edit in the field.
Review restrictions independently of formatting
Check the current description restrictions even when the text renders correctly. KDP lists several types of content that cannot be included in that field. Successful formatting does not establish that every sentence is permitted or that the description accurately represents the book. Keep the content review tied to the actual entered wording.
For example, material appropriate to a private launch note may not belong in a book description. Do not copy a complete promotional document simply because part of it contains the accepted summary. Identify the text intended for this field and review it on its own. This prevents surrounding planning material from entering the listing through an otherwise careful transfer process.
Keep the final entered version with the release record
Before completing the publication workflow, inspect the description in the available view and compare it once more with the accepted book information. Record the version actually submitted rather than only the source file you intended to use. If the observed public presentation later differs, that record provides a concrete starting point for investigation.
After any correction, check the whole description again, including the parts that were not intentionally changed. Keep wording, formatting, and publication status distinguishable in the record. The final review should establish that the description contains the right text in a supported, readable form. It should not rely on the appearance of the original document as evidence about the destination field.
Frequently asked questions
Clear answers for this publishing decision.
Can I assume word-processor formatting will survive copying into KDP?
No. Review the destination’s supported options and inspect the entered result. Preserve the accepted wording so formatting corrections can be checked against it.
Why can the character count exceed the visible text length?
KDP’s current guidance states that formatting markup counts toward the limit. Inspect the field’s count and source view rather than estimating solely from visible words.
Does correct formatting mean the description is ready?
Also verify the wording, current content restrictions, and consistency with the book. Display quality and content acceptance are separate review questions.
What should the title, subtitle, description, and keywords look like before I upload?
Check the mechanical limits first, then make sure title, subtitle, categories, and description describe the same book for the same reader; a keyword is useful when it matches how that reader searches, not because it is popular.
Draft the listing fields in a book project