By Jetformat
PDF extraction creates a new PDF containing a selected contiguous range. Splitting creates separate PDF files for individual pages. Rendering creates raster images for viewing. These operations differ in output format, numbering, and the evidence they provide.
Choose from the required deliverable
| Request | Operation | Output |
|---|---|---|
| Send pages 2–5 as one document | pdf extract --pages 2-5 |
One four-page PDF |
| Store every page separately | pdf split |
One PDF per page |
| Inspect pages 1 and 3 visually | pdf render --pages 1,3 |
Page images |
A screenshot is useful for checking layout, but it is usually the wrong deliverable when a recipient expects a searchable multipage PDF. Likewise, splitting a large PDF into hundreds of files is unnecessary when only one chapter is needed.
Page selectors are not interchangeable
pdf extract accepts one contiguous range, including 1-last or all. Rendering supports comma-separated selections such as 1,3-5,last. Do not copy a renderer selector into an extraction command and assume it has the same meaning.
jetformat pdf extract book.pdf --pages 2-5 -o chapter.pdf
jetformat pdf info chapter.pdf
jetformat pdf render chapter.pdf --pages 1 --width 1600 -o chapter-preview
The last command previews the first page of the new chapter. Its page 1 corresponds to page 2 in the source. Keep that change in numbering explicit when documenting review findings.
Check the result at the right level
For extraction, verify page count and the first and last selected pages. For splitting, compare the number of generated files with the source page count. For rendering, open the images and check readability at the intended display size.
Reading the PDF page count is free. PDF writes and rendered pages use credits, so inspect before producing unnecessary outputs. See the focused guides for extracting a range, splitting pages, and rendering previews.
Run a range operation without losing context
- Read the source page count with
pdf infoand confirm the requested range exists. - Choose a new output path and run the selected operation.
- Inspect the generated file count or PDF page count, depending on the output type.
- Open the first and last relevant pages and compare them with the source.
- Record how output page numbers map back to the original document.
If someone requests noncontiguous source pages in one PDF, do not pass a render-style selector to extract. Plan separate supported extractions and a merge, or confirm a different deliverable. Additional writes create additional usage units and should be explicit in the workflow.
Calculate only the operations you need
Suppose a source has 10 pages. Extracting pages 2–5 writes 4 output pages and uses 4 credits. Splitting the entire source writes 10 pages across 10 PDF files and uses 10 credits. Rendering only pages 1 and 3 writes 2 images and uses 2 credits. These are alternative examples; add them only if your workflow actually performs all three.
If you extract the four-page chapter and then preview its first page, the total is 5 credits. Reading either file’s properties is free. See credit estimates when a workflow also includes conversion or Office edits.
Preserve the useful format
Image previews are useful in review tools but should not replace a searchable PDF when the recipient needs to copy text or navigate a multipage document. Likewise, a collection of single-page PDFs can be harder to handle than one chapter file. Ask what the next reader or process must do with the result, then choose the smallest set of operations that produces that artifact.