When a report flags metadata, establish whether it means properties embedded in a document or the book details entered in KDP. These are different objects with different review tasks. Inspect the exact finding, correct the relevant source or export, and preserve the publication identity record rather than deleting useful listing information to clear an unrelated file warning.
Identify what the report inspected
Read the finding in the context of the tool and file it examined. A document inspector may refer to properties carried inside a PDF, while a publishing dashboard may refer to a title, contributor, or description field. The same word does not establish that both reports are discussing the same information.
Record the object, property name, and file or page version involved. If the report is unclear, investigate its documentation or the inspected output before making changes. A broad instruction to remove metadata can cause confusion when the project contains manuscript files, artwork, editorial records, and a worksheet of required public book details.
Keep the publication identity record intact
Maintain the approved title, subtitle, author, series information, and other applicable book details in the project's publication record. These values describe the edition readers are offered. Their review concerns accuracy and consistency with the actual book and cover, rather than whether a separate export retains unnecessary document properties.
For example, a report may flag an internal working title stored in a PDF property while the visible title page and KDP worksheet already use the accepted title. That is a reason to inspect the file property and export process. It is not a reason to erase the correct public title or to assume the whole edition has been renamed.
Review the applicable file requirement separately
KDP's paperback submission guidance lists metadata among material that submitted files should not contain. Treat that as a file-preparation requirement and consult the current guidance for the intended format. Do not reinterpret it as an instruction to omit the book details that the publishing workflow asks the author to provide.
Use a suitable inspection method for the actual export and understand what it reports. Properties, visible text, bookmarks, and comments may be presented in different areas of an application. Record the specific finding rather than declaring that every item displayed by an inspector is interchangeable. The correction should address the identified requirement without damaging unrelated content or obscuring the book's identity.
Correct the export through a reproducible process
Trace the unwanted property to the source document or export settings where practical. A cleanup performed only on one output may be lost when the manuscript is exported again. Preserve the accepted source and document the steps needed to produce the corrected upload candidate so another collaborator can repeat them.
Check the replacement file after the correction. Confirm that the reported property has been handled as intended and inspect representative pages to make sure the process did not alter visible content. If the workflow involves a conversion or optimization step, evaluate its actual output instead of assuming that a setting name proves the result.
Preserve working records outside the upload artifact
Keep the project information needed for future revision in an appropriate working record or archive. Source history, contributor decisions, and production notes can remain useful even when they do not belong inside the submitted file. Separate their storage and purpose so file cleanup does not destroy the only account of how the book was prepared.
Make the upload folder unambiguous. Identify the exact interior and cover candidates, while keeping editable sources and internal records clearly distinguishable. This helps the uploader select the intended artifacts without treating every file in the project as part of the public book. The working archive and the submission package serve related but different needs.
Close both reviews with their own evidence
Record the corrected file, the inspection performed, and the resulting finding. Separately verify that the public book details still match the accepted edition and current metadata guidance. Closing the document-property issue should not silently approve a description, contributor entry, or series relationship that nobody checked.
Repeat the relevant file inspection if another export replaces the accepted candidate. Revisit public details when the manuscript or edition identity changes. Keeping these triggers distinct makes the review easier to maintain: a technical cleanup can remain a technical correction, while a genuine change to the book's promise receives the editorial and production review it needs.
Frequently asked questions
Clear answers for this publishing decision.
Does removing file metadata mean removing the KDP title?
No. First identify which object the finding concerns. Embedded document properties and the public book details are separate, and the applicable requirements should be reviewed for each.
Should I delete my editorial history during file cleanup?
Preserve needed working records in the project archive. Distinguish information required for ongoing production from material that belongs in the submitted artifact.
Can a metadata warning be fixed by changing only the filename?
A filename change does not establish that an embedded property was corrected. Inspect the actual finding and verify the resulting file using an appropriate method.
When should the check run again?
Review a replacement export against the applicable file requirements. Review public book details separately when the edition or reader promise changes.
What should the title, subtitle, description, and keywords look like before I upload?
Check the mechanical limits first, then make sure title, subtitle, categories, and description describe the same book for the same reader; a keyword is useful when it matches how that reader searches, not because it is popular.
Draft the listing fields in a book project