When this tool is useful
Maintaining ordinary document-level attachments stored in a conventional EmbeddedFiles name tree under explicit file-count and byte budgets.
How local processing works
The browser walks only the Catalog Names/EmbeddedFiles name tree, checks names and stored or declared sizes, rewrites that tree for supported operations, and reopens the result. Page FileAttachment annotations and catalog or page AF relationships are reported but not modified.
How to use it
- Prepare a safe working copy: Keep every source unchanged and review the supported input, controls, and limits before processing. Maintaining ordinary document-level attachments stored in a conventional EmbeddedFiles name tree under explicit file-count and byte budgets.
- Process locally: Run the documented operation in this browser and stop if an unsupported structure is reported. The browser walks only the Catalog Names/EmbeddedFiles name tree, checks names and stored or declared sizes, rewrites that tree for supported operations, and reopens the result. Page FileAttachment annotations and catalog or page AF relationships are reported but not modified.
- Download and verify: Use the destination viewer to list and open every expected attachment, compare names and sizes, and separately inspect FileAttachment annotations and AF relationships that were intentionally preserved.
Important limitations
This is not a universal attachment or portfolio editor. Unsupported, malformed, cyclic, oversized, associated-file, page-annotation, signed, or proprietary structures are rejected or preserved, and attachment contents are not scanned for malware.
Verify the downloaded result
Use the destination viewer to list and open every expected attachment, compare names and sizes, and separately inspect FileAttachment annotations and AF relationships that were intentionally preserved.
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?
Maintaining ordinary document-level attachments stored in a conventional EmbeddedFiles name tree under explicit file-count and byte budgets.
What does the browser actually do?
The browser walks only the Catalog Names/EmbeddedFiles name tree, checks names and stored or declared sizes, rewrites that tree for supported operations, and reopens the result. Page FileAttachment annotations and catalog or page AF relationships are reported but not modified.
Which limits must I understand?
This is not a universal attachment or portfolio editor. Unsupported, malformed, cyclic, oversized, associated-file, page-annotation, signed, or proprietary structures are rejected or preserved, and attachment contents are not scanned for malware.
How should I verify the result?
Use the destination viewer to list and open every expected attachment, compare names and sizes, and separately inspect FileAttachment annotations and AF relationships that were intentionally preserved.