2026-07-26 · all guides

The KDP Re-Upload Fix: When Amazon's Backend Is Wrong About Your Book

Two problems, one weird fix

Here are two failures that look unrelated:

• Your ebook won't enroll in KDP Select. The tooltip says “Public Domain works are not allowed to enroll,” and every 70% royalty row errors at publish time — but your Publishing Rights say “I own the copyright,” and they always have.
• Customers receive printed copies with defects — smears, shifted trim, missing pages — while your print previewer shows a flawless book, and KDP support even admits the fault is on their side. Yet bad copies keep shipping.

In both cases, every setting you can see is correct. That's the tell: the broken state isn't in your files or your form fields. It's in the derived artifacts KDP builds from your upload — the content-analysis verdict attached to your manuscript, the print master generated at the facility. When those go wrong, no amount of toggling visible settings helps, because the visible settings were never the problem.

The fix

Re-upload the file. The same file. Unchanged.

Go to the Content step, upload your manuscript (and cover, if it's implicated) again, let processing finish, and then retry whatever was blocked — the Select enrollment, the publish, the next author-copy order. Uploading forces KDP to re-run everything it derives from the file: the content scan, the conversion, the print master. If the derived state was the corrupted piece, the fresh derivation replaces it, and the wall disappears.

This feels too dumb to work, which is why authors spend weeks toggling rights radios, re-saving pricing pages, and arguing with support chat first. But the visible controls only write to the record you can see. The re-upload is the only lever you have that rewrites the records you can't.

When to reach for it

• Select enrollment blocked over rights you never claimed. The “public domain” verdict usually comes from KDP's automated scan concluding your content is publicly available — sometimes because it matched your own already-published edition. The scan's verdict sticks to the upload; a re-upload gets a fresh verdict.
• Print defects from a clean file. Previews render from your PDF; printed copies render from a generated print master. When the two disagree, regenerate the master by re-uploading, then order a single author copy to confirm before telling anyone it's fixed.
• Stale conversion artifacts. Formatting complaints on the ebook that don't reproduce in your EPUB, “Look Inside” showing an older version — same shape, same fix.

When it's *not* the fix

Re-uploading can't fix mismatches that live in your actual files or metadata — cover text that doesn't match the title fields, spine width built for an old page count, an ISBN conflict. Those are real errors on your side, and the re-upload just re-submits them. The distinguishing question: does the failure contradict what your own dashboard and files plainly show? If yes, suspect Amazon's derived state and re-upload. If your files genuinely disagree with each other, fix the files.

Escalating when it doesn't work

If a re-upload plus one retry doesn't clear it, you're likely looking at a flag that requires a human — contact KDP through the specific category (print quality, rights, Select) rather than general chat, name the contradiction precisely (“my rights say X, your system behaves as if Y”), and include dates and order IDs. Precise contradictions get escalated; general complaints get templates.

FAQ