A contract has twelve pages. The first two pages contain the terms and conditions that were negotiated over several weeks. Pages three and four contain the pricing schedule that was reviewed by both legal teams. Page five is the signature page where both parties will place their signatures. After signing, one party wants to ensure that the signed pages, specifically the signature page and the terms pages that were incorporated by reference, cannot be edited, while the remaining pages of the contract, such as appendices and supporting schedules, remain editable for future amendments.
Standard PDF security applies to the entire document. When you password-protect a PDF or apply editing restrictions, those restrictions apply to every page. There is no built-in PDF feature that locks individual pages while leaving others editable. Achieving page-level protection requires a workaround that combines PDF page extraction, signing, and merging to create a document where some pages are signed and locked and others are editable. The workaround is technically sound when done correctly, but it requires an understanding of how digital signatures interact with page-level content.
How PDF Digital Signatures Create Page-Level Protection
A digital signature in a PDF does more than identify the signer. It creates a cryptographic hash of the exact byte content of the document at the moment of signing. If any byte in the signed portion of the PDF changes after the signature is applied, the signature verification fails. This means that a digital signature inherently locks the content it covers against any modification, not because the PDF software enforces an editing lock, but because any edit would break the signature's cryptographic validity.
This property can be used to achieve page-level protection. Sign the pages you want to protect, and the signature's integrity check serves as a tamper-evident seal on those pages. If someone edits the signed pages, the signature breaks and every subsequent viewer sees a warning that the document has been modified since signing. The unsigned pages remain editable because changes to those pages do not affect the byte content of the signed pages, provided the pages are organized in a way that isolates the signed content from the unsigned content. The Protect PDF capability of a digital signature is a cryptographic property, not a permission setting, and it is more reliable than password-based editing restrictions because it cannot be bypassed by a non-compliant PDF reader.
Method 1: Split, Sign, and Merge for Page-Level Locking
The most straightforward approach to locking only specific pages is to split the PDF into two separate files, one containing the pages to be signed and locked, and one containing the pages to remain editable. Sign the first file with a digital signature and apply any additional security settings, such as an owner password that restricts editing. Merge the signed file and the unsigned file back into a single PDF, with the signed pages appearing first and the unsigned pages appearing second.
After merging, the signed pages retain their digital signature because the signature's cryptographic hash covers the exact byte range of the signed pages at the time they were signed. The unsigned pages, which were appended after the merge, are outside the signed byte range and can be edited without affecting the signature. A recipient who opens the merged PDF in a signature-aware PDF reader sees a valid signature on the signed portion and a clear visual boundary between the signed section and the editable section.
The technical requirement for this method is that the merge operation must append the unsigned pages after the signed pages without modifying the signed pages' byte content. Most PDF merge tools achieve this correctly because they concatenate pages at the object level rather than re-encoding existing pages. To verify that the merge was performed correctly, open the merged PDF in a signature validation tool and confirm that the signature on the signed pages still shows as valid after the merge. A broken signature after merge indicates that the merge tool modified the signed pages' byte content, and a different merge tool or merge method should be used. WukongPDF's Sign PDF and merge tools use append-only concatenation that preserves existing signature byte integrity, which makes this split-sign-merge workflow reliable.
Method 2: Using PDF Portfolio or Collection Instead of a Single File
An alternative that avoids the complexity of split-sign-merge is to not produce a single merged PDF at all. Instead, package the signed pages and the editable pages as separate PDFs within a PDF Portfolio, a feature that Adobe introduced in PDF 1.7 and that is supported by most modern PDF readers. A PDF Portfolio is a container file that holds multiple independent PDFs, each with its own security settings, signatures, and editability.
Create the Portfolio by opening Adobe Acrobat and selecting File, Create, PDF Portfolio. Add the signed PDF containing the locked pages and the editable PDF containing the unsealed pages. The Portfolio presents the documents as a navigable collection with a unified interface, but each document retains its independent security settings. The signed document inside the Portfolio keeps its valid signature regardless of how many times the editable document is modified and re-added. The main limitation of the Portfolio approach is that it does not produce a single, sequentially paginated document. Each component PDF has its own page numbering starting from 1. For contracts where the pages should be numbered consecutively, such as page 5 of 12, the Portfolio approach may not meet the formatting requirement. For document sets where each component is a logically separate unit, the Portfolio provides clearer separation and stronger security isolation than the merged approach.
Method 3: Applying Incremental Save and Append-Only Signatures
The most technically nuanced method uses PDF's incremental save mechanism to create a document where a signature covers an initial set of pages and subsequent pages are appended through incremental saves without invalidating the original signature.
A PDF file is structured as a sequence of objects followed by a cross-reference table and a trailer. When an application performs an incremental save, it appends new or modified objects to the end of the file, adds an updated cross-reference section, and writes a new trailer, without modifying the original objects. A digital signature applied through an incremental save covers the byte range up to the signature object itself, and subsequent incremental saves that append new content after the signature do not modify that covered byte range.
To use this method, create the initial PDF containing only the pages to be signed. Apply a digital signature using a signing tool that supports incremental saving. The signature covers the entire file up to the signature object. Then, open the signed PDF and append the additional pages, the ones that should remain editable, through an incremental save operation. The appended pages are outside the signature's byte range and can be modified without breaking the signature. This method is the most seamless for the recipient, who sees a single continuously numbered PDF with a valid signature on the first section and editable pages in the second section. The method requires a PDF editor that explicitly supports incremental save mode. Adobe Acrobat saves incrementally by default when modifying a signed PDF unless you use Save As, which performs a full save and invalidates the signature. Always use Save, not Save As, when appending content after a signature (Adobe, "Digital Signatures in Acrobat: Incremental Save Behavior", 2025).
Communicating the Page-Level Protection Structure to All Parties
A PDF where some pages are signed and locked and others are editable is unusual, and recipients need clear communication about which pages are protected and what they may and may not edit. Without this explanation, a recipient may attempt to edit a signed page, see the signature break, and assume the entire document has been compromised. Or they may assume the document was sent in error because they cannot edit a page that looks identical in formatting to the adjacent editable pages.
Include a cover page or a header note on the first page that explicitly states the protection structure. For example: Pages 1 through 5 of this document are digitally signed and page-locked as of the execution date. Any modification to pages 1 through 5 will invalidate the digital signature. Pages 6 through 12, consisting of Appendix A, Schedule 1, and the exhibits, remain editable for future amendments and updates. This language sets clear expectations and documents the intended protection scope.
Also communicate the page-level lock structure in the email or cover letter that accompanies the signed PDF. The combination of in-document explanation and out-of-document communication ensures that all recipients, including those who may not read the cover page, understand which pages are authoritative and which are administrative. The communication step transforms a technical workaround into a transparent documented process that holds up under contractual scrutiny. Insufficient communication in this step has caused contract disputes where one party assumed a page was editable because it was part of the same PDF file, and the other party assumed it was locked because it was covered by the signature scope. The ambiguity is resolved entirely by clear, written communication that accompanies the document.