Amazon KDP's AI rules,
translated for novelists.
What you must disclose, what you don't, and how to know which side of the line your manuscript is on.
Since 2023, Kindle Direct Publishing has required authors to declare AI-generated content at publishing time. The policy is short. The confusion it produces is not — because the line Amazon draws is not the line most writers expect.
The two categories that decide everything
KDP sorts AI involvement into exactly two buckets, and the entire disclosure question turns on which one your book falls into:
- AI-generated — the tool produced the words (or images, or translation). Amazon is explicit that this stays AI-generated even if you substantially edited the output afterward. Generated-then-revised is still generated.
- AI-assisted — you produced the text yourself and used AI to edit, refine, error-check, brainstorm, or outline. This does not require disclosure.
Notice what the distinction ignores: quality, percentage, and effort. A chapter the model drafted and you spent ten hours rewriting is disclosable. A chapter you wrote at 2 a.m. and ran through an AI line-edit is not. The question is never how much work did I do — it's who put the first version of these sentences on the page.
The gray zone every hybrid writer lives in
Real drafting is messier than two buckets. You wrote the scene, but the model suggested three sentences of description you kept. You dictated the plot beats and the tool expanded them. You translated your own paragraph through an AI and back. Modern manuscripts are often mosaics — mostly human, with machine-made tiles scattered through.
For mosaic manuscripts the practical questions become: which passages actually read as machine-generated, and how much of the book do they cover? That's an auditing problem, and it's the reason we built a detector specifically for fiction — one that names the pattern and quotes the passage for every flag, instead of handing you an unexplainable percentage. Knowing where the AI-flavored prose sits lets you make the disclosure call deliberately — or rewrite those passages until the question disappears.
What Amazon does with the disclosure
As of this writing, the declaration is between you and Amazon: it does not appear on your product page, and Amazon hasn't announced ranking penalties tied to it. Two cautions belong next to that sentence. First, platform policies change without much notice — check the current KDP content guidelines before you publish. Second, Amazon reserves the right to remove content that creates a poor customer experience, and AI-heavy prose increasingly generates exactly the reviews that trigger that scrutiny.
The risk nobody discloses: readers
The disclosure checkbox is the smaller half of the problem. The larger half is that romance and fantasy readers — the most voracious buyers on the platform — have become alarmingly good at spotting machine prose, and they put their findings in one-star reviews. An AI slop accusation in your review section does more commercial damage than any disclosure ever will, and it lands on fully human books too when the prose happens to lean on the constructions AI made infamous.
That's the case for auditing before publishing regardless of how you drafted: find the passages that read machine-made — whatever their true origin — and fix them while they're still yours to fix. The patterns are knowable; we've catalogued the seven most common tells in AI fiction, and our audits are calibrated so human styles don't get punished: all four of our public-domain calibration novels score 0 out of 100.
A sane pre-publish checklist
- Classify honestly. Did a tool write any of the prose? If yes, you're disclosing — editing it afterward doesn't change the category.
- Audit the manuscript. Run it through a fiction-calibrated detector and read every flagged passage. You're looking for both genuine AI leftovers and human passages that could be mistaken for them.
- Rewrite what reads wrong. Not with a so-called humanizer tool — those don't move structural audits — but by hand, where your voice is strongest.
- Keep your drafts. Version history is the provenance trail that settles accusations quickly.
Frequently asked questions
Do I have to tell Amazon my novel used AI?
If portions of the actual text were generated by an AI tool — even portions you then edited substantially — KDP requires you to disclose it as AI-generated during publishing. If you wrote the text yourself and used AI only to edit, proofread, brainstorm, or check errors, Amazon classifies that as AI-assisted, and disclosure is not required.
What's the difference between AI-generated and AI-assisted on KDP?
AI-generated means the tool produced the words, images, or translation, regardless of how much you revised afterward. AI-assisted means you produced the content yourself and used AI to refine it. The line Amazon draws is who created the underlying content — not how polished the final draft is.
Do readers see the AI disclosure on my book's page?
As of this writing, no — the disclosure goes to Amazon, not onto your public listing. But policies evolve, and review-driven accusations are public regardless of what Amazon displays, which is why many authors audit their prose before publishing.
Can Amazon actually detect AI-generated fiction?
Amazon hasn't published a detection methodology, and no detector — Amazon's, Slopsleuth, or anyone's — can prove authorship. What detection tools measure is statistical pattern density. That's exactly why honest disclosure plus a pre-publish audit is the lowest-risk path: you know what your text looks like before anyone else weighs in.
Will disclosing AI use hurt my book?
Disclosure itself doesn't currently change how your book is displayed or ranked. The bigger commercial risk is undisclosed AI-heavy prose that readers notice — 'AI slop' accusations in reviews damage a title far more than a checkbox Amazon doesn't publish.
Audit your manuscript before Amazon — or your readers — do.
Five fiction-calibrated audits. Every flagged passage quoted. Free sample audit, no signup.
Try Slopsleuth free →