Document AI use against the material retained in the accepted manuscript and artwork. KDP requires disclosure of AI-generated text, images, and translations, including generated content edited afterward; it does not require disclosure of AI-assisted work on content you created. Keep version-linked origin and review notes so you can distinguish those cases when preparing a new publication or an update.
Start with the practical question, not the tool
If you are preparing your first paperback, the important question is not whether AI can speed up self-publishing. It is whether you can clearly explain what AI touched, what you created yourself, and what you are submitting to KDP. That record matters before you upload the manuscript, and it matters even more later if you revise the interior, replace the cover, change metadata, or publish another format.
Do not wait until the KDP setup screen asks about AI content. By then, you may not remember whether an image was generated, only edited, licensed from a stock library, or created by a designer using an AI workflow.
KDP’s AI content guidance distinguishes between AI-generated content and AI-assisted content. In plain terms, AI-generated material is content created by an AI tool, even if you later edited it. AI-assisted work is content you created, with AI used to brainstorm, check, refine, or improve it. Always confirm the current wording in KDP’s help pages and publishing interface, because the exact disclosure process can change.
Create a simple AI-use log before you build the paperback files
Your AI-use log does not need to be complicated. A spreadsheet, document, or project notebook is enough. The point is to preserve decision history while the project is still fresh. For each major asset, record the date, tool used, purpose, output type, and whether you consider the result AI-generated or AI-assisted under KDP’s current definitions.
For a paperback, track at least these asset groups: manuscript text, chapter titles, illustrations, charts, tables, cover image, cover typography, back-cover copy, author bio, book description, keywords, and category research notes. If the book includes translated material, record whether AI created the translation, assisted a human translator, or was used only for review. Translation is specifically important because it can affect both content disclosure and reader expectations.
Add a version label to every file you may upload or reuse. For example: Interior_v03_AIproofed, Cover_v02_AIbackground, Description_v01_AIassisted. The label does not need to appear publicly. It is for you, so you can connect the uploaded paperback file to the notes explaining how it was made.
Do not rely on memory or chat history alone. Tools may delete conversations, change export formats, or become unavailable. Keep local copies of final prompts only when they are useful to understand the output, but do not treat prompts as a substitute for your own review. The stronger record is your decision note: what you accepted, what you rejected, and what you changed.
Separate AI-generated material from AI-assisted work
The most useful compliance distinction is this: did AI create publishable material, or did it only help you work on material you created? If an AI tool produced paragraphs, poems, recipes, lesson content, character descriptions, illustrations, icons, diagrams, or a translated passage that you include in the book, record that as AI-generated unless KDP’s current guidance says otherwise. Editing the output afterward does not necessarily make it non-AI-generated.
When you create the content yourself and use AI to edit, refine, check errors, or otherwise improve it, KDP treats that as AI-assisted. Brainstorming ideas with AI followed by writing the actual text yourself is also assistance. Keep a concise record of the process, especially when the same project also contains separately generated material that must be identified.
A command named rewrite does not determine the classification by itself. Record whether the tool improved content you created or supplied new content retained in the book. Do not invent a percentage-of-edits threshold, and do not assume that substantial human editing changes generated material into assistance. When the process is unclear, reconstruct the origin before completing the publishing record.
The safest habit is to mark each asset by outcome, not by intention. “Used AI for cover” is too vague. “AI-generated fantasy landscape used as full front-cover background, manually adjusted color and typography in design software” is useful. “AI suggested five subtitle options; author wrote final subtitle independently” is also useful.
Document the manuscript decisions that can affect later editions
A first paperback often becomes the source for later Kindle, hardcover, large-print, audiobook, workbook, or translated editions. Decisions you make now can follow the project for years. Keep a manuscript change log that identifies which chapters contain AI-generated text, which chapters were only proofread with AI, and which parts were written without AI tools. If the book has exercises, quizzes, citations, recipes, technical instructions, or health-related content, add extra human review notes.
AI can produce confident errors, inconsistent facts, invented references, or wording that sounds polished but is unsuitable for your audience. Your documentation should therefore include a review step, not only a generation step. Note who checked factual claims, calculations, quotations, citations, permissions, and safety-sensitive instructions. If you are the only reviewer, say so and describe what you checked.
For nonfiction, keep source notes separate from AI notes. AI output is not a source unless you are discussing AI output itself. If the book depends on factual information, record the actual sources you consulted and verify quotations, dates, names, legal references, and technical procedures outside the AI tool. KDP holds publishers responsible for the content they upload, including content made with AI.
For fiction, children’s books, poetry, journals, and activity books, documentation still matters. Track whether AI generated story text, puzzles, coloring pages, illustrations, or prompts. For low-text interiors, do not assume there is nothing to disclose or review. Images, repeated pages, and activity layouts can raise quality and rights issues just as text can.
Track cover art, image rights, and paperback production details
Paperback cover files create special recordkeeping problems because one finished PDF may contain many separate elements: front image, background texture, spine text, back-cover copy, barcode area, author photo, publisher logo, and decorative icons. Record each element’s origin. Was it AI-generated, licensed stock, your own photograph, public domain material, designer-created work, or a combination?
If AI generated any visible cover image or interior illustration, keep a note describing the generated element and how it is used. Also keep any license terms or tool terms that applied when you created the asset. Do not assume every AI tool gives you the same commercial-use rights. If you hired a designer, ask for a written breakdown of AI-generated elements, stock assets, fonts, and licenses before you upload the cover.
Paperback production choices also affect later files. Trim size, bleed, paper type, page count, and spine width determine the cover template and final PDF dimensions. If you revise the interior and the page count changes, the cover may need to be rebuilt. Your AI documentation should stay linked to the new cover version, especially if an AI-generated background or illustration is reused.
Keep final flattened files and editable source files. The uploaded PDF shows what KDP receives, but the editable file explains how it was assembled. If you later need to replace a questionable image, correct a rights problem, or change the AI disclosure status during an update, editable files can save time and prevent accidental reuse.
Record metadata help without letting AI write misleading metadata
Metadata is not just marketing copy. On KDP it includes title, subtitle, contributors, series information, edition details, description, keywords, categories, age and grade ranges when applicable, and other setup fields. KDP’s metadata rules generally require that this information be accurate, not misleading, and not stuffed with irrelevant search terms. Confirm the current metadata rules in KDP before publishing.
AI tools can help you draft a book description, compare subtitle options, or organize keyword ideas, but you are responsible for the final entries. Document whether AI generated the description or only helped revise your own draft. If you use AI to produce keyword suggestions, keep the raw list separate from the final KDP keywords you choose. Do not include claims such as “bestselling,” “official,” “free,” or competitor names unless they are accurate and allowed under current KDP rules.
For a first paperback, pay close attention to title and subtitle. These should match the book cover and interior title page. If AI suggests a subtitle that promises outcomes the book does not deliver, reject it. If you later publish a Kindle edition, mismatched title information can create avoidable corrections across formats.
Categories and keywords can change after publication, but changes are not a substitute for truthful metadata at launch. Keep notes on why you chose them. If AI suggested categories that do not fit the book’s actual content, do not use them. Reader expectations and KDP compliance both depend on accurate placement.
Use the KDP setup screen as a final check, not your only record
Use the current KDP content guidance when answering the AI questions during publication or republication. Generated text, images, and translations require disclosure; assisted work does not. Your log should identify what is actually present in the accepted files, rather than treating discarded experiments or every tool session as included content.
For example, an accepted generated illustration remains generated after color correction or added typography. A chapter you wrote and used AI to proofread belongs to the assisted case. Inspect the final files and their origin notes together so the answer reflects the submitted book, including any changes since the previous edition or update.
Also review KDP’s content quality and paperback file requirements before approving proof copies. AI documentation does not replace basic publishing checks. Look for duplicated pages, unreadable text, incorrect margins, missing bleed, low-resolution images, placeholder text, wrong author name, and cover-spine errors. Order or review a proof when appropriate before making the paperback available.
Finally, update the log whenever you change the book. A corrected typo does not usually require a major note. Replacing a cover, adding AI-generated illustrations, rewriting chapters with an AI tool, or changing the description does. Treat your AI record as part of the book’s production file, alongside ISBN information, cover templates, manuscript versions, and rights documentation.
Frequently asked questions
Clear answers for this publishing decision.
Do I need to mention AI use in the book’s copyright page?
KDP’s AI disclosure is handled through KDP’s publishing process, not necessarily through a copyright-page statement. Some authors choose to add a transparent production note, but it should be accurate and not overstate ownership, permissions, or quality review. If you add one, keep it consistent with your KDP answers and your actual workflow.
What if I used AI months ago and do not remember exactly what it produced?
Reconstruct the record as honestly as you can before upload. Review drafts, file dates, exported images, chat logs, design layers, and notes. If you cannot determine whether a piece of included material was AI-generated, consider replacing it with material you can document or consult KDP’s current guidance before publishing.
Should I save every prompt I used?
No. Saving every prompt can become unmanageable and may not prove what is in the final book. Save the prompts or exports that explain included AI-generated assets, then pair them with a clear note about what entered the manuscript, cover, or metadata and what you changed.
Can I use AI to create KDP keywords and categories?
You can use AI as a brainstorming aid, but you must choose final metadata that accurately describes the book and follows KDP rules. Keep a note showing which suggestions you accepted and why. Do not use irrelevant keywords, misleading category choices, or claims the book cannot support.
Does AI-assisted proofreading need the same documentation as AI-generated chapters?
It usually does not need the same level of detail, but it should still be noted. A simple entry such as “AI-assisted proofreading for spelling and consistency; no AI-generated passages accepted” can be enough for your own production record, subject to KDP’s current definitions and disclosure requirements.
What must I check, disclose, and verify myself when AI helped produce the book?
Review facts, rights, and source material yourself, record which parts were AI-assisted or AI-generated so you can answer Amazon’s disclosure question accurately, and treat every automated check as a starting point rather than a verdict.
See what the compliance checks cover