Check the actual paperback upload PDF for locking or encryption before submission. KDP lists locked or encrypted files among common failure points. If a restriction is present, return to the authorized source and prepare a suitable publication export, then verify the new file's content and layout as well as its settings.
Inspect the file intended for upload
A production folder may contain a review copy, an archival copy, and the publication candidate. Identify the exact PDF that will be submitted before checking its properties. A correct source document or an unrestricted earlier export does not establish the settings of the current file.
Open the document properties or an appropriate inspection tool and review the reported security settings. Record the result with the file version. Do not conclude that the file has no restrictions merely because it opens normally in the application you use every day.
Distinguish viewing from unrestricted processing
A document can be readable while carrying restrictions that affect other operations. A saved password or an already open session can also obscure what another process will encounter. Evaluate the actual file properties instead of using successful viewing as the sole acceptance test.
KDP's paperback submission guidance identifies locked or encrypted files as a common point of failure. Keep that requirement separate from the editorial question of whether the book looks correct. Both need attention, and a successful visual review does not answer the file-restriction question.
Return to the authorized production source
If the upload candidate has unsuitable restrictions, locate the editable source and the export settings used to create it. Prepare a publication copy through the authorized workflow. Preserve any protected review copy separately when it still serves a legitimate purpose in the project.
Do not treat an unfamiliar password or a third party's restricted document as something to bypass casually. Resolve access with the responsible owner or obtain an appropriate source file. The objective is a valid export of the author's publication material, with its source and permissions understood by the production team.
Keep the correction limited but verify its effects
Change the relevant export settings without introducing unrelated layout edits. Then compare the new PDF with the approved version: page count, page dimensions, fonts, illustrations, and representative difficult pages. A different export route can alter more than the property you intended to fix.
Inspect text and artwork that previously required special handling. If transparency, font embedding, or image placement changes, resolve those issues before accepting the replacement. Removing one submission problem does not justify carrying new production defects into the upload package.
Reconcile the handoff after replacing the file
Update the release inventory so it identifies the corrected PDF unambiguously. Mark the restricted candidate as superseded for publication use and retain its history where useful. Similar filenames should not leave the next person guessing which version passed the final checks.
Notify the responsible project reviewer through the normal handoff record and identify which checks were repeated. An earlier approval may cover the manuscript's wording, while layout approval may need to attach to the new export. Keep those scopes clear instead of treating every previous check as either universally valid or entirely worthless.
Confirm the actual submission candidate
Before upload, reopen the exact file named in the handoff and confirm its reported properties. Check that the path has not reverted to a protected review copy. Preserve the verified candidate so any later replacement can be recognized as a new file requiring its own assessment.
Use the rest of the current KDP submission guidance for the remaining technical review and inspect the publication preview appropriately. A PDF without locking or encryption has cleared one file-preparation concern; it has not proved complete compliance, accurate content, or a successful final layout. The record should state the specific check performed and the file it covers.
Frequently asked questions
Clear answers for this publishing decision.
Is a PDF safe to submit if it opens without asking for a password?
That observation alone is insufficient. Inspect its reported security properties and identify the exact file intended for submission rather than relying only on normal viewing behavior.
Should I overwrite the protected review copy?
Keep copies distinct when they serve different purposes. Prepare and identify an appropriate publication export, then ensure the release handoff points to that verified file.
Do I need to recheck layout after changing export settings?
Yes. Compare the resulting file with the approved version because a different export route or setting can affect page geometry, fonts, or images as well as the restriction you intended to change.
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