What Amazon KDP’s AI Disclosure Rule Actually Requires
Yes. Amazon KDP requires authors and publishers to disclose AI-generated material when uploading a book to Amazon, particularly in e-book formats. The requirement applies to content created by generative AI systems, including substantial text, illustrations, cover elements, translations, and certain excerpts. Merely using spelling correction, grammar checking, brainstorming, or other conventional editing tools does not normally count as AI-generated content. Using an AI system does not automatically disqualify a title, but presenting AI-generated work without making the required declaration may delay publication, trigger a metadata request, or lead to removal.
Also worth reading: Who Owns AI-Generated Writing, and What Publishing Rights Should Authors Secure in 2026? · How Should Authors A/B Test AI-Generated Book Covers Without Fooling Themselves? · What is the definitive C2PA provenance audit checklist for AI-generated content in 2026?
The policy has evolved since Amazon introduced its first formal disclosure requirement in September 2023. Later updates broadened how publishers report AI use and distinguished between AI-generated and AI-assisted production. Because policies and interfaces can change, authors should use the current KDP Content Guidelines and title setup screens rather than relying on an old blog post or a publisher’s memory. As of 30 September 2026, the safe operational position is straightforward: disclose AI-generated content through the applicable KDP form, describe its extent accurately, and check again before every new upload or major edition revision.
Amazon’s rule concerns a declaration, not a promise that a book is entirely human-written in every minor respect. It also does not say that a disclosed AI-generated book will receive less reach or be rejected. The actual risk is inaccurate representation. An author should not answer “no” merely because AI output was lightly edited, because disclosure can be evaluated according to the generative origin of the material rather than the amount of human cleanup performed afterward.
How “AI-Generated” Differs from “AI-Assisted”
AI-generated content is material substantially produced through a generative model. Examples can include passages drafted by a text model, illustrations generated by an image model, and translations produced by a machine-translation system. The fact that a human selected a prompt, accepted the output, or changed a few sentences does not necessarily turn AI-generated material into human-written content. Authors therefore need to examine where the words or images came from, not simply how polished the final file looks.
AI-assisted content is generally work in which AI was used as a tool while a human retained responsibility for drafting, revising, or curating the material. Common examples include generating alternative headlines, suggesting an outline, checking punctuation, or proposing revisions that the author then writes and approves independently. KDP’s treatment of assisted work may depend on the role of the AI and the exact point in the production process. Authors should not use a narrow personal definition that conflicts with Amazon’s wording.
The distinction matters because “I used AI somewhere” is not a useful disclosure answer. A book can involve human-created chapters, AI-generated illustrations, an AI-assisted outline, and a human-reviewed translation. The correct response may need to cover only the generated illustration, or it may require a general declaration depending on the title and the current KDP workflow. Authors should keep a record of the tools, dates, and material involved, especially if several people contributed to the book.
| Feature | AI-generated material | AI-assisted material |
|---|---|---|
| Typical example | Model-written prose, generated cover art, AI translation | Brainstorming, outline suggestions, grammar assistance, alternative titles |
| Human role | Chooses, edits, or combines generated output | Drafts and controls the material, using AI for support |
| KDP treatment | Declare through the applicable content or metadata workflow | Rules can differ by use; verify whether declaration or details are requested |
| Main concern | Misleading readers about authorship and creation | Misclassifying assistance, especially if it substantially created text |
A Practical Disclosure Process for KDP Authors
Begin by inventorying every stage of production. Note where the manuscript came from, which image tool created any illustrations, whether translation software was used, and whether metadata such as a blurb, subtitle, or author biography was generated. For collaborative books, ask each contributor to describe their AI use in writing. A simple production log with six columns—section, tool, date, output type, human edits, and disclosure decision—can prevent a last-minute contradiction.
Next, open the official KDP title setup workflow rather than assuming the answer will appear in a fixed field. Complete all prompts concerning AI-generated or AI-assisted content and make the declaration before submitting the files. If KDP requests details, identify the content accurately and proportionately. Do not paste a vague disclaimer into the book description when the proper answer belongs in the disclosure workflow, and do not remove a required statement without checking the current policy.
After publication, retain screenshots of the completed disclosure, the submitted manuscript, and any related correspondence. If Amazon contacts the publisher about the title, respond promptly and provide the production record. KDP accounts can include authors, publishers, administrators, and rights holders, so the account owner should also ensure that coauthors and editors know what was declared. Updating only one person’s local records creates avoidable confusion.
The process usually adds no separate KDP fee and can take less than 10 minutes if the production history is well documented. More time may be needed when a publisher inherited an old title, translated it from an AI source, or cannot locate original files. In that situation, conservative disclosure is generally safer than guessing, although authors should still describe the known facts rather than make unsupported claims.
What Triggers Disclosure—and What Usually Does Not?
The clearest triggers are outputs created by a generative system and then incorporated into the book. A chapter drafted by a language model, cover art made by an image generator, or an entire translation supplied by machine translation can all require action. Repeated use becomes harder to characterize as occasional assistance if it supplies passages, scenes, character descriptions, or other expressive material. Authors should evaluate the total use rather than counting the number of prompts.
Conventional tools are less likely to require disclosure when they do not generate expressive content. Examples include a dictionary lookup, spellchecker, basic formatting tool, manually operated scan editor, and perhaps a grammar service that only flags errors. Even with these tools, authors should follow the current Amazon language. A service that rewrites entire sentences may be more than a grammar checker, while a tool that only identifies an incorrectly placed comma generally presents a different case.
Research can also create uncertainty. KDP, Kindle Unlimited, and Amazon Ads each have separate rules, and one platform’s answer does not necessarily settle another. A bibliographic record may identify the underlying source and display the disclosure required for a particular edition. If AI helped locate facts but the author independently verified and wrote the final prose, that is different from accepting generated sentences as the text. Authors should not insert unsupported factual claims merely because a model supplied them.
The practical threshold is not a published number of AI-generated words or images. Amazon’s policy is based on the nature of the content and the required declaration, not a universal allowance such as “under 10% is exempt.” Even one substantial generated passage deserves scrutiny. Conversely, a book mentioning AI in its subject matter is not automatically AI-generated; using AI to study a topic does not mean the finished work came from the model.
Disclosure, Metadata, and Reader Notices Are Different Things
A KDP disclosure is a platform declaration made during publishing. It is not automatically a label readers will see on every Amazon product page, and the presence of a disclosure does not need to dominate the cover or title. Authors should therefore avoid assuming that completing the KDP form satisfies every possible notice obligation. The edition’s metadata, copyright page, publisher website, contract, and retailer requirements should be reviewed separately.
Authors whose books are distributed through other channels should check each retailer’s policy. IngramSpark, Apple Books, Barnes & Noble, libraries, academic distributors, audiobook sellers, and subscription services may use different definitions and forms. A single statement such as “AI was used in the creation of this book” may be broad enough to cover the actual production, while a more specific description—such as identifying generated cover art but a human-written manuscript—may be more accurate. The wording should be honest without becoming technically confusing to ordinary readers.
Professional publishers face added questions about editorial standards, contributor contracts, and marketing claims. An author should not describe a work as “100% human-created” unless that statement is defensible. Likewise, a publisher should not remove an existing disclosure simply because a new edition was lightly revised. The relevant question is whether the new edition still includes material covered by the prior disclosure. Keeping the original and revised files can demonstrate what changed.
A useful publication record contains at least the date, edition identifier, model or tool category, material affected, human review performed, declaration made, and location of supporting files. Reviewing that record before release reduces disputes with Amazon and gives authors evidence if a question arises later. It also makes correction of a mistaken disclosure faster.
Common Mistakes That Can Delay or Complicate a Release
One common error is treating light editing as a complete reset. Replacing a model-written passage with a few corrections does not necessarily make the passage human-written. Another is assuming that disclosed content will prevent publication or automatically reduce royalties. Those are separate policy questions. A disclosure may be neutral in sales, but concealing generated material can create enforcement and account problems that cost far more than a few sales.
Authors also make errors in the opposite direction. They may declare whole-book AI use when AI only suggested titles, or they may attach a public disclaimer while failing to complete KDP’s internal declaration. Overbroad statements are not a substitute for answering the platform’s questions accurately. If the policy has changed, an old disclaimer is not proof that the current workflow was completed as required.
Translated books deserve special attention. A human may have edited an AI translation without independently reconstructing every sentence, and a publisher may inherit rights from an overseas author who used a different workflow. Keep the source file, translation service, editor’s notes, and final revision history. When facts cannot be reconstructed, pause the submission or seek Amazon guidance instead of inventing a provenance claim.
Finally, do not treat disclosure as a substitute for copyright and quality control. A model may reproduce recognizable source material, invent quotations, or create misleading claims. Check permissions for source and reference material, verify every factual assertion, and ensure that images do not imitate a living artist’s identifiable style in a way that conflicts with law or retailer rules. Disclosure addresses how content was produced; it does not legalize copied work or guarantee accuracy.
When Authors Should Act, Recheck, or Seek Help
Authors should act before uploading a new title, changing a subtitle or cover, issuing a new edition, or materially rewriting a manuscript. They should also recheck their records if a copyright year changes, a publisher takes over the title, or a book moves between formats. A correction that affects fewer than a handful of words may seem minor, but the question is whether any AI-generated material remains in the new edition.
The strongest case for direct contact with KDP support is a genuinely ambiguous workflow. Examples include an inherited title with no production history, a hybrid book created by several contractors, or a translation whose provenance is disputed. Save screenshots and describe the facts plainly; support cannot make a factual declaration on the author’s behalf. If the question concerns tax, royalty ownership, or an unpublished title, the publisher should open the relevant support case rather than publishing first and asking later.
Authors should not delay an entire project merely because they used AI brainstorming or ordinary proofreading. Instead, they should document the limited use and determine whether the current policy requires a declaration. This prevents both over-compliance and concealment. The cost of KDP disclosure itself is normally $0 because it is part of the standard publishing workflow, while professional AI-policy review or consulting is a separate service whose price varies by scope.
As of 30 September 2026, the defensible standard is to re-read Amazon’s current official guidance on the day of publication. The 2023 introduction date is useful history, but it is not a substitute for the live rule. Keep a dated policy note in the title archive. That small habit gives the author evidence of reasonable diligence and makes future edition changes easier to handle.
Does the Disclosure Affect Sales, Royalties, or Account Status?
A disclosure does not by itself establish that a book is low quality, unacceptable, or permanently hidden from Amazon search. KDP can distribute disclosed AI-generated titles, and a disclosure statement is not a royalty penalty. The market effect is harder to predict: readers may react positively to transparency, reject generic fiction, distrust a book in a genre where voice matters, or ignore the notice entirely. A specific number of lost sales cannot be assigned from Amazon’s policy alone.
The more direct financial risks are publication delay, requested edits, removal of an inaccurate title page or metadata declaration, and disruption to an established series. Authors should budget for ordinary KDP production costs rather than a mandatory AI surcharge. International 100% royalty eligibility for e-books has its own pricing and distribution conditions, including the traditional list-price bands, but AI disclosure is not an extra royalty charge. A title priced at $2.99 or $9.99 should be evaluated under the applicable distribution and territory rules, not because of its disclosure status.
If an author wants help, AI publishing consultants may review workflow records, compare retailer requirements, draft an accurate provenance statement, or establish a quality-control process. Pricing is not standardized: some lightweight audits are fixed-fee projects, while broader ghostwriting, editing, cover, or metadata services are quoted by scope. Ask for a written scope, deliverables, revision limits, and a statement identifying what the consultant does not control, such as Amazon’s final review decision. The service should improve documentation and compliance, not sell concealment or guarantee rankings.