By allentatakai
Prepare the input
Run the command against the exact source deck. Keep the JSON with the assembly job if it helps detect template changes between runs.
These examples use local sample filenames. Substitute your own paths and check jetformat ppt inspect --help against the installed version before running the task. Put paths containing spaces inside quotes.
Run the command
jetformat ppt inspect board-deck.pptx --jsonStructural inspection reports slide, text-box, table, image, and chart counts. Use it to plan an edit before selecting slide numbers.
Review before the next step
Use the inventory to plan edits, then inspect the output again. Structural counts cannot establish whether the final deck tells the intended story or renders correctly.
Record the current slide count and check it again after rearranging or removing slides.
Keep the workflow repeatable
This is a free utility or read operation. It does not need a paid conversion to inspect the result.
Run jetformat ppt inspect --help to compare options with your installed version.
See the ppt 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 ppt inspect options and examples for the command reference. Browse related ppt commands when the next step requires a different operation.