When this tool is useful
Matching a PDF viewer's navigation labels to covers, front matter, chapters, appendices, or printed numbering while leaving visible page artwork unchanged.
How local processing works
The browser validates ordered one-based physical-page rule starts, style, prefix, and positive start values, removes the prior PageLabels entry, writes a bounded number tree, and saves a structurally rewritten PDF.
How to use it
- Prepare and preserve the source: Keep the unchanged source, review the intended destination, and begin with conservative limits. Matching a PDF viewer's navigation labels to covers, front matter, chapters, appendices, or printed numbering while leaving visible page artwork unchanged.
- Run the bounded local operation: Process only in this browser and stop on unsupported, malformed, or ambiguous input. The browser validates ordered one-based physical-page rule starts, style, prefix, and positive start values, removes the prior PageLabels entry, writes a bounded number tree, and saves a structurally rewritten PDF.
- Inspect the result: Reopen the result in the intended PDF viewer, inspect labels at every rule boundary and final page, confirm bookmarks and forms still behave, and never replace a signed original.
Important limitations
Page labels affect viewer navigation only; they do not add visible page numbers. Rewriting can invalidate digital signatures and may not preserve every advanced PDF feature or malformed custom number tree.
Verify the downloaded result
Reopen the result in the intended PDF viewer, inspect labels at every rule boundary and final page, confirm bookmarks and forms still behave, and never replace a signed original.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
When is this tool useful?
Matching a PDF viewer's navigation labels to covers, front matter, chapters, appendices, or printed numbering while leaving visible page artwork unchanged.
What does the local operation do?
The browser validates ordered one-based physical-page rule starts, style, prefix, and positive start values, removes the prior PageLabels entry, writes a bounded number tree, and saves a structurally rewritten PDF.
Which limitations matter?
Page labels affect viewer navigation only; they do not add visible page numbers. Rewriting can invalidate digital signatures and may not preserve every advanced PDF feature or malformed custom number tree.
How should I verify the result?
Reopen the result in the intended PDF viewer, inspect labels at every rule boundary and final page, confirm bookmarks and forms still behave, and never replace a signed original.