By allentatakai
Decide what success means
Use the information to validate requested page selections. Metadata and page count do not establish that every page is readable or visually correct.
Prepare and run
Run inspection before a write command and keep the input path associated with the result. Avoid inferring page count from a filename or thumbnail.
These examples use local sample filenames. Substitute your own paths and check jetformat pdf info --help against the installed version before running the task. Put paths containing spaces inside quotes.
jetformat pdf info book.pdf --jsonUse pdf info after conversion to learn the actual page count, PDF version, encryption state, and first-page dimensions. It is a free read operation.
Inspect the saved result
Use --json for scripts and compare the page count with the expected output rather than inferring it from the source file size.
Scope and repeatability
This is a free utility or read operation. It does not need a paid conversion to inspect the result.
Run jetformat pdf info --help to compare options with your installed version.
See the pdf command reference for the surrounding workflow.
Keep the input revision with the result so a later reviewer can reproduce the decision. For a write operation, choose a new output path first; use overwrite flags only when replacing a previously reviewed result is intentional.
See the pdf info options and examples for the command reference. Browse related pdf commands when the next step requires a different operation.