Resolve Conflicting Advice About KDP File Preparation

When two file-preparation instructions conflict, first check whether they refer to the same format, component, and settings. Read the applicable current KDP guidance directly, record its scope and verification date, and compare your actual export with that requirement. If the conflict remains unresolved, seek clarification using a concrete file example instead of combining incompatible instructions.

Write the disagreement as two specific statements

Conflicting advice is difficult to resolve when it is summarized as “the designer says one thing and the software says another.” Write down the two instructions precisely. Identify the action each would require, such as changing a manuscript file type, altering an export setting, or modifying a cover dimension. Preserve the source context so a recommendation does not accidentally become a universal requirement.

Separate the claim from the proposed solution. A tool might report that it cannot inspect an element and recommend a different export. That does not necessarily mean KDP forbids the existing element. Likewise, an older tutorial may describe a workflow that worked for its author without establishing the current submission rule. A clear statement of the disagreement makes these differences visible before anyone edits the book.

Match the format and file component

Determine whether each instruction concerns an ebook, paperback, or hardcover. Then identify whether it applies to the interior, cover, or the editable source used to produce them. KDP’s formatting resources distinguish these publication formats, and the paperback submission guidance contains separate manuscript and cover instructions. Advice for one part should not be transferred automatically to another.

Bleed provides a useful example. The paperback submission guidance reviewed on September 21, 2026 specifies a PDF manuscript for interiors containing elements that extend to the page edge, while listing additional accepted manuscript file types for a no-bleed interior. Two instructions about file types can therefore appear contradictory while describing different configurations. Confirm the current guidance and your actual layout before deciding which statement applies.

Distinguish requirements from workflow preferences

A designer may prefer a particular export method because it produces predictable files in their application. A checker may apply a conservative threshold to catch potential readability problems. Those preferences can be useful without being direct platform requirements. Ask the source to identify which kind of instruction is being given and what risk it addresses. Keep the requirement and the recommended workflow separately labeled.

For a platform requirement, open the official page rather than relying on a copied excerpt. Read the surrounding section and note the date you checked it. For a software-specific workflow, consult the documentation for the actual application and version used. Do not resolve the disagreement by averaging two settings or selecting whichever instruction is easier. The resulting file needs to satisfy the applicable requirement, and its production method needs to preserve the intended content.

Inspect a representative export before changing everything

If the uncertainty concerns how an export behaves, make a small representative file containing the affected feature. Preserve the source and settings used to create it. Inspect the result with the relevant file and visual checks. This can reveal whether a proposed fix changes the output as intended or merely changes a label in the export dialog.

For example, an instruction to flatten an element may alter its appearance or interaction with neighboring objects. Review the resulting page and compare it with the intended design. A successful local check is useful evidence about that file, but it is not a guarantee of platform acceptance. Keep the scope of the conclusion narrow and carry out the applicable publication preview and review steps when preparing the final submission.

Record the decision so the conflict does not return

Save the applicable guidance, configuration, chosen workflow, and checked export together. Explain why the other instruction did not apply or why it was replaced. A note such as “earlier advice concerned the cover, while this decision concerns the interior” prevents a future collaborator from reopening the question without context. Include the settings that would require the decision to be reviewed again.

If both instructions still appear applicable, keep the issue open. Prepare a concise question with the format, affected component, exact observations, and relevant source links. Avoid sending private manuscript material that is unnecessary to explain the issue. Once clarified, update the production checklist and review the final export. The durable outcome is a traceable decision for this book, not an unsupported rule applied to every future edition.