Before processing, write down the intended page groups and compare them with the preview count. After downloading, confirm whether the result is one PDF or a ZIP, count the contained files and compare each page total with the plan. For a range, inspect both endpoints and one middle page. For chunks, inspect the boundary between consecutive parts. For one-page files, verify the first, last and a sampled middle output. Exact bytes are useful identity evidence for this run, not a quality score or fidelity guarantee.
A split result is a new document
PDFSplit copies selected visible pages into newly serialized PDF files; it does not cut bytes out of the original container. Document-level metadata, outlines, page labels, embedded files, portfolios, scripts, open actions, optional layers, tagged structure, PDF/A or PDF/X claims, usage rights, encryption, incremental history and digital signatures may not carry across. Forms, links and annotations can depend on shared resources. Keep the source and never describe an output as signed, certified, archival, compliant or evidentiary merely because the pages look correct.
Inspect every downloaded output
Open the exact downloaded PDF files in the reader used by their destination. Compare the first and last page of every requested range, total page counts, visible order, rotation and crop boxes. Test hyperlinks, annotations, form controls, fonts, reading order and accessibility where they matter. A successful local operation proves only that the current browser produced files with the reported page counts and byte sizes. It cannot prove semantic completeness, destination acceptance, identity, signature validity, legal filing, regulatory compliance or archival quality.