Keep an illustration’s original creation record linked to every accepted derivative used in the book. Record meaningful edits and added elements without replacing the earlier history. Cropping, retouching, or extensive manual editing does not by itself erase an AI-generated origin under KDP’s content guidance, so review the final asset using its actual creation process.
Start with the source asset and its creation record
Identify the image from which the production version was made. Record whether it was generated, created by a person, or assembled through a mixed process, using information from the actual creator. Include a stable asset identifier and the location of relevant source files. A generic folder label such as original artwork can become misleading when several creation methods are represented inside it.
Keep the record focused on what the publisher needs to understand the accepted asset. You do not need to expose unrelated private account information or preserve every abandoned experiment in the release package. You do need enough information to distinguish the asset’s origin from later editing work and to resolve questions when a contributor delivers a replacement with a different history.
Track meaningful derivatives without losing the parent
When you create a crop, retouched version, or layout adaptation, connect it to the source identifier. Record the purpose of the change and the accepted output. A crop made for a cover can differ substantially from an interior illustration even though both derive from the same image. Their shared origin should remain traceable while their placement and review status remain distinct.
Use clear version relationships instead of relying on filenames alone. A sequence of files called final, final-new, and final-approved does not explain which source produced them or why one replaced another. A short note linking the accepted derivative to its parent and describing the change is often enough to prevent that confusion during a later handoff.
Record added elements as part of the process
Retouching can range from adjusting contrast to adding new visual content. Describe additions that affect the final image’s creation history, including generated replacements or elements supplied by another contributor. If a composite includes several sources, identify those components at a useful level. Do not assume that the origin of the largest visible component fully describes the resulting asset.
Keep source and permission information for included material alongside the creation record where relevant. Knowing that an element came from a particular tool or contributor does not resolve every publication responsibility. The workflow should make the evidence available for review, while avoiding unsupported conclusions about ownership or permission based only on the image’s appearance or the amount of editing performed.
Apply current disclosure guidance to the history
KDP’s content guidance distinguishes generated content from work created by a person with AI assistance. It also states that substantial edits to generated content do not remove its generated classification. Use the documented process when reviewing the book’s disclosure requirements. Do not substitute a team-made rule based on how many hours a human spent retouching the result.
When the process is unclear, ask a specific question tied to the asset. Was the depicted content created by an AI tool, or was an existing human-created image refined with assistance? Which accepted elements came from which process? Preserve uncertainty until the responsible person can resolve it. An attractive final image does not provide enough evidence to reconstruct those answers reliably.
Reconcile the placed image with the record
Before finalizing the book, compare the image actually placed in the cover or interior with the accepted asset inventory. Check for late substitutions and layout exports that point to an earlier version. A correct origin record for one image does not automatically cover a visually similar replacement. Update the inventory when the selected asset changes, and retain the superseded relationship as history.
Save the reviewed creation record with the accepted derivative and the relevant release files. If the illustration is reused in another format, carry the origin link forward and record the new adaptation. This gives future editors a reliable starting point for their own checks. The aim is continuity: each published asset should connect to an understandable creation history despite the ordinary crops, edits, and exports that occur during production.
Frequently asked questions
Clear answers for this publishing decision.
Does manual retouching make a generated image human-created for KDP disclosure?
KDP guidance states that generated content remains within its generated-content treatment even after substantial editing. Preserve the original process and check the current instructions when preparing the disclosure.
Do I need a separate origin record for every crop?
You can link derivatives to one source record while identifying each accepted crop and its use. Keep the relationship clear enough that a later reviewer can trace the placed asset without guessing.
What if a designer replaces one part of the image?
Record the replacement element and how it was created, then review the resulting composite and its relevant source information. Do not assume that the earlier record fully describes newly added content.
What must I check, disclose, and verify myself when AI helped produce the book?
Review facts, rights, and source material yourself, record which parts were AI-assisted or AI-generated so you can answer Amazon’s disclosure question accurately, and treat every automated check as a starting point rather than a verdict.
See what the compliance checks cover