Loading BoundHive

Record AI Use for Cover and Interior Artwork

Record how each cover and interior asset was created, which tool or person produced it, what later edits were made, and what rights or permissions support its use. Review current KDP disclosure guidance separately. Different assets in the same book may have different creation histories, so one vague AI-used note is insufficient.

Create an asset-level origin record

Give every selected image a stable identifier and record its creator or generation source. Include the creation date, relevant brief, and the original output or source file. If the image came from a designer, obtain a clear description of the supplied asset and agreed usage rights.

Keep origin distinct from appearance. A hand-edited image can still have an AI-generated origin, while a human-created illustration may have used AI only in an assistance role. The record should describe the actual workflow rather than infer it from how polished or realistic the final image looks.

Describe later edits accurately

Record meaningful edits such as repainting, compositing, cropping, adding typography, or replacing specific elements. Keep the original and selected final version linked. This helps you understand what changed without losing the origin of the underlying material.

Current KDP guidance distinguishes generated content from assisted content and treats substantial later editing as insufficient to erase a generated origin. Verify the current definitions before submission. Do not convert a detailed edit history into an unsupported conclusion that an image must now count as entirely human-created.

A symbolic browser workflow illustrating how to describe later edits accurately.
Describe later edits accurately

Review rights as a separate question

A disclosure decision does not by itself establish that you have permission to use an asset. Review applicable tool terms, supplied licenses, agreements, and any other relevant rights concerns. Keep those records attached to the specific image or source package.

Do not assume a generated image is free of recognizable protected elements simply because it was produced from a prompt. Inspect the output and resolve concerns before using it. When a rights question is consequential or unclear, obtain appropriate qualified advice rather than treating a workflow checklist as a legal determination.

Prepare the publication decision from the records

Review the cover and interior inventories together before answering publication questions. Make sure the final files contain the assets described in your records. A replaced illustration may have a different origin from the version originally approved.

Answer based on the actual content being submitted, not the general intention you had when starting the project.

  • Record origin for each selected asset.
  • Preserve original and edited versions.
  • Keep rights review distinct from disclosure.
  • Verify current KDP definitions and questions.
  • Reconcile the inventory with the final export.
A symbolic browser checklist illustrating how to prepare the publication decision from the records.
Prepare the publication decision from the records

Maintain the history through revisions

When you replace an image, add a new record rather than overwriting the previous asset's history. Link the new version to the release that uses it. This makes later updates and disclosure reviews easier to perform accurately.

Keep the records proportionate but complete enough to explain the decision. You do not need a narrative of every mouse movement. You do need a reliable connection between the final artwork, its creation process, relevant usage information, and the publication choices made for that edition.

Continue with this topic

Frequently asked questions

Clear answers for this publishing decision.

Does heavy editing erase an AI-generated origin?

Under the current KDP distinction, substantial edits do not by themselves change generated content into assisted content. Recheck the official guidance before submission.

Should cover and interior images share one record?

Maintain asset-level records. Their origins, edits, permissions, and final versions can differ even within the same book.

Does disclosure prove I have usage rights?

No. Disclosure and rights are separate questions. Review the applicable permissions and any concerns associated with the specific asset.

Cover and spine

How wide does the full-wrap cover need to be, and how thick is the spine?

The cover width is back cover plus spine plus front cover plus bleed on both sides; the spine width is the final even page count multiplied by the paper-specific factor Amazon publishes, so the cover cannot be sized before the interior page count is final.

Prepare the cover in a book project

Get all of our updates directly to your inbox.
Sign up for our newsletter.

We could not save your subscription.