If you use AI anywhere in your publishing workflow, Amazon expects you to say so — but only for a specific kind of use, and only in a specific place. The distinction Amazon draws is narrower than most publishers assume, and getting it wrong in either direction causes problems: under-declaring risks your account, and over-declaring makes you hesitate about workflows that are entirely permitted.
This guide explains what the disclosure actually asks, where the line between AI-generated and AI-assisted sits, and how to answer confidently for the kinds of books most independent publishers produce.
What this guide covers
- What Amazon actually asks when you publish
- AI-generated versus AI-assisted: the distinction that matters
- Worked examples from real publishing workflows
- Images, covers and translations
- What disclosure does not do
- Disclosure does not replace quality standards
- Pre-publishing checklist
- Frequently Asked Questions
What Amazon actually asks when you publish
The disclosure is not a form you fill in separately, and it is not something you write into your book's description. It appears inside the KDP publishing flow itself, as a question about the content you are uploading. You answer it per title, at the point of publishing or updating.
Two things about this surprise people. First, the answer is not displayed on your book's product page — it is information for Amazon, not a public label. Second, answering yes is not a penalty. Amazon asks the question to understand what is being published on the platform, not to reject books that use AI.
Because the wording and placement of this question can change as Amazon revises its process, check the current content guidelines in Amazon's KDP Help before you publish rather than relying on a screenshot from a guide written months ago — including this one.
AI-generated versus AI-assisted: the distinction that matters
Amazon separates these two, and almost every question publishers have comes down to which side of the line their workflow falls on.
AI-generated means the content was created by an AI tool, whether or not you edited it afterwards. The key word is created. If you asked a model to write a chapter and then rewrote half of it, the chapter still began as AI output. Editing does not convert it.
AI-assisted means you created the content, and used AI to refine, improve or check it. You wrote the chapter; a tool suggested a better opening line, tightened your grammar, or proposed alternative titles. The authorship started with you.
The clearest way to test your own workflow is to ask: if the AI tool had not existed, would this text still exist in some form? If yes, and the AI only improved what you had, that is assistance. If no, and the tool produced the material from a prompt, that is generation.
The distinction is about origin, not effort. A heavily edited AI draft is still AI-generated. A lightly polished human draft is still AI-assisted.
Worked examples from real publishing workflows
Abstract definitions are easy to agree with and hard to apply. Here is how the line falls across workflows independent publishers actually use.
A coloring book with AI illustrations
You choose the theme, decide the page count, and use an image model to produce the line art. The illustrations were created by AI, so this is AI-generated content, and you would declare it. Your creative decisions about theme, sequencing and difficulty are real work, but they are not what the question is asking about.
If you are producing this kind of book, the practical concerns beyond disclosure are consistency and print quality — covered in keeping AI coloring books on theme and creating coloring books for KDP.
A puzzle book with generated puzzles
A crossword or word search produced by a puzzle generator is a slightly different case from a novel written by a language model, but the honest answer is the same: the content was produced by software from your parameters rather than constructed by you. Declare it. The same applies to a maze grid or a sudoku layout.
A non-fiction book you wrote and then edited with AI
You wrote the manuscript. You then used a tool to fix grammar, suggest clearer phrasing, and flag repetition. This is AI-assisted. You are not required to declare it.
An outline from AI, prose from you
This one causes the most hesitation. If the AI produced an outline and you wrote every sentence of the book yourself, the text in the book is yours. Most publishers treat this as assistance. If in doubt, declaring costs you nothing — which is the point worth internalising.
A translation produced by AI
A machine translation of your own book is AI-generated content in the target language, even though the original was yours. The words a reader in that market will read were produced by a tool.
Images, covers and translations
The disclosure covers more than the manuscript. Amazon's content categories include text, images and translations, which matters for low-content and illustrated books where the interior is the images.
A cover generated by an image model counts. A cover you designed yourself from stock elements does not. If you use a tool to design your cover on a correctly sized canvas rather than to generate the artwork, that is a design tool, not content generation — you can lay one out with the KDP Cover Generator and calculate the spine yourself with the Spine Width Calculator, and neither produces AI content.
For the exact spine maths and why it changes with page count and paper type, see the KDP spine width formula explained.
What disclosure does not do
Several persistent beliefs about the disclosure are simply wrong, and they cause publishers to make worse decisions than the rules require.
- It does not appear on your product page. Readers browsing Amazon do not see a badge on AI-assisted or AI-generated titles.
- It does not reduce your royalty. Royalty rates are set by list price and delivery, not by how the content was made.
- It does not prevent publishing. Declaring AI-generated content is not a rejection trigger.
- It does not exempt you from every other rule. This is the one that catches people out, and it deserves its own section.
Keeping a record you can answer from
The disclosure is answered per title, and titles get updated. A book you publish this month may be revised next year — a new cover, a corrected interior, an added chapter. When you update it, you may be asked again, and by then you will not remember which parts came from where.
Keep a short note alongside each project recording which tools produced which components. It does not need to be elaborate: a line saying the interior illustrations came from an image model, the blurb was written by hand, and the translation was machine-produced is enough to answer consistently a year later.
This matters more for illustrated and low-content books than for prose, because those are the books most likely to be produced in batches with slightly different workflows. Publishing ten coloring books in a month, three of which used AI artwork and seven of which used purchased line art, is exactly the situation where memory fails and a note does not.
Consistency is the point. An account that answers the same question differently for near-identical books invites questions that a simple record would have prevented.
Who owns AI-generated content
The disclosure question is separate from the rights question, and conflating them causes unnecessary worry. Declaring that content is AI-generated is not a statement that you do not own it, and it does not transfer anything to Amazon.
What you do need to be confident about is that you have the right to publish the material at all. That depends on the terms of the tool you used, not on Amazon's disclosure. Image and text generators differ in what they permit for commercial use, and some free tiers grant narrower rights than paid ones. Read the terms of the specific tool before you build a catalogue on it, rather than after.
This is also why using a tool built for publishing matters more than it might appear. A general-purpose image generator may produce a usable illustration while leaving the commercial position ambiguous; a tool intended for producing books you will sell should be unambiguous about it.
Disclosure does not replace quality standards
Declaring AI content answers one question. It does not tell Amazon your book is formatted correctly, that your images are print-ready, or that your metadata is accurate. Every other requirement applies unchanged.
In practice, books built quickly with AI tend to fail on the same unglamorous things as books built quickly by hand: interiors that ignore bleed and margin rules, low-resolution images that print soft, page counts that do not match the cover spine, and keyword stuffing in the title field. Those are the problems that actually cost publishers time, and they have nothing to do with AI policy. If your book is rejected, the reason is far more likely to be one of those — see common KDP rejection reasons and how to fix them.
Amazon also limits how many new titles an account can upload in a day. That limit exists independently of AI disclosure and applies to everyone. Check the current figure in KDP Help rather than assuming, since it is the kind of operational limit Amazon adjusts.
Pre-publishing checklist
- Identify, honestly, whether each part of your book was created by AI or merely improved by it.
- Remember that images and translations count, not just the manuscript text.
- Answer the disclosure question in the KDP publishing flow for each title.
- If you genuinely cannot decide, declare — there is no penalty for doing so.
- Confirm the current wording of the content guidelines in KDP Help before publishing a batch.
- Check your interior against trim, bleed and margin requirements regardless of how it was produced.
- Confirm your images are high enough resolution for print.
- Make sure your metadata describes the book accurately, without keyword stuffing.
- Keep a private record of which tools produced which parts, so you can answer consistently if a title is updated later.
Frequently Asked Questions
Does Amazon ban AI-generated books?
No. Amazon asks you to declare AI-generated content when you publish. Declaring it is not a rejection trigger. Your book still has to meet every other content and quality guideline, as any book does.
Will readers see that my book used AI?
The disclosure you give at publishing is not shown as a label on your product page. It is information provided to Amazon.
I wrote the book myself and used AI to fix grammar. Do I declare it?
That is AI-assisted rather than AI-generated. Amazon does not require you to declare assistance of that kind. The content originated with you.
What about AI images in a coloring book?
Images created by an AI tool are AI-generated content, and the interior of a coloring book is almost entirely images. Declare it.
Does a heavily edited AI draft still count as AI-generated?
Yes. The distinction is about where the content originated, not how much you changed afterwards. Editing does not convert generated content into assisted content.
Do I need to declare an AI translation of my own book?
Yes. The text a reader in that language will read was produced by an AI tool, even though you wrote the original.
Where can I check the current rules?
Amazon's own content guidelines in KDP Help are the only source worth relying on. Guides like this one explain the concepts; Amazon defines the requirements, and it revises them.
In short
The rule is simpler than the anxiety around it. If a tool created the content, say so. If a tool improved content you created, you do not need to. Declaring costs nothing, so uncertainty should resolve towards declaring.
What actually determines whether your book succeeds is everything the disclosure question does not ask about: whether the interior is formatted to spec, whether the images print cleanly, and whether the metadata helps the right reader find it.
If you are producing illustrated books, the AI Coloring Book Generator builds print-ready interiors at correct trim sizes so the formatting side is handled while you focus on the theme. For keyword and metadata work, the KDP Metadata Optimizer helps you fill the title, description and backend keyword fields without stuffing them.