Before reusing an asset, identify its origin, the permission or license record associated with it, and the use planned for the new edition. Compare that record with the actual asset and publication context. If coverage is unclear, resolve the question with the relevant rights holder or qualified advice before treating the asset as ready for publication.
Identify the exact asset and its history
An image in an old project folder may have passed through several contributors, exports, and revisions. Begin by identifying the exact file you intend to reuse and the source from which it came. Record the original creator or provider where known, the acquisition date, and any changes made since acquisition. Keep the original and revised versions distinguishable.
Do not infer permission from a descriptive filename, a watermark-free appearance, or the fact that the asset was used before. Those observations can help locate history, but they do not explain the terms of the new use. If the working file contains several components, identify them separately where needed. A composite illustration may include material with different origins and different supporting records.
Locate the document that supports the intended use
Look for the actual permission communication, agreement, or license terms associated with acquisition. An invoice may help establish a transaction, but inspect what it says rather than assuming it defines every allowed use. Preserve the relevant version of the record and any reference linking it to the asset. A current provider page may differ from the terms under which an older file was obtained.
Read the record for the concrete use you are planning. Relevant questions may include the edition, formats, modifications, distribution, and any attribution conditions described in the document. This article does not determine how a particular agreement applies. Its workflow is to expose the facts and uncertainties so the author can obtain clarification rather than make an unsupported assumption about coverage.
Compare the proposed use with the recorded scope
Describe where the asset will appear and what will change. Reusing an illustration inside a revised manuscript is a different production description from placing it on a cover or using it in promotional artwork. Record those uses separately. If you plan to crop, recolor, combine, or add text to the asset, include those details when checking the record or requesting clarification.
For example, an author might have a documented permission for a photograph in a specific print edition and now want to include it in another format. The important step is to check what the record actually covers, not to assume that the same book title settles the question. Keep the proposed use and the relevant wording together so a rights holder or adviser can understand the issue without reconstructing the project.
Keep uncertain assets out of the final selection
Mark the asset as unresolved when its origin or permitted use cannot be established from the available record. Identify the missing information and who can provide it. A clear status prevents a designer from assuming that a polished file has already passed every review. Consider a replacement with a documented basis for use if clarification is unavailable within the production schedule.
KDP’s content guidance places responsibility for applicable rights compliance on the publisher. A local file check or an AI tool’s assurance cannot establish permission for an asset. Keep the review separate from technical readiness: an image can have suitable dimensions and still lack an adequate record for the intended use. Conversely, a documented asset may still need formatting and editorial checks before publication.
Connect the final file with the reviewed record
Once the issue is resolved, record the selected file, the intended use, the supporting document, and any conditions that need to be reflected in the book. Check the final manuscript or cover for the required attribution or other agreed treatment. Do not let a later asset substitution inherit the previous file’s reviewed status merely because the filenames are similar.
Keep the supporting record with the project’s publication documentation and revisit it when the use changes. Future editions, additional formats, or new promotional materials may raise questions the earlier review did not address. A useful asset record makes those questions easy to identify. It supports careful publication decisions without claiming that an internal checklist itself grants rights or guarantees compliance.
Frequently asked questions
Clear answers for this publishing decision.
Does previous publication prove I can reuse the asset?
It establishes that the asset appeared before, but it does not by itself explain the basis or scope of permission. Locate the supporting record and compare it with the new intended use. Resolve any uncertainty before relying on the earlier publication as precedent.
What if a collaborator supplied the image?
Ask for its origin and the documentation relevant to the planned use. Keep that information connected to the file. A collaborator’s delivery message may be a useful lead, but inspect what it actually establishes instead of assuming it resolves every rights question.
Should I store the record inside the image file?
Keep an accessible project record that remains connected to the asset even after export or renaming. Embedded metadata may be removed by production tools, so it should not be the only place where essential permission information can be found.
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