Jetformat

How many PDF preview pages should a batch render?

Render the pages needed for the review decision. Sampling lowers the number of preview images, but it cannot establish that every unreviewed page is correct.

Published · 4 min read

By Jetformat

State the assumptions first

This example batch contains 100 PDFs with 20 pages each. Conversion has already happened. The calculations below cover only PDF rendering at one credit per rendered page; they are not measured throughput or quality results.

Preview policy Calculation Images Render credits
First page only 100 × 1 100 100
First, middle, last 100 × 3 300 300
Every page 100 × 20 2,000 2,000
First page100 Three pages300 Every page2,000
Calculated image counts under the stated batch assumptions; no speed or quality benchmark is implied.

Choose pages by risk, not only position

A title page may be the least demanding page in a document. Add pages containing dense tables, unusual fonts, charts, or section transitions. A fixed “first, middle, last” policy is a starting example, not a guarantee of coverage.

For a 20-page document, a three-page selection can be rendered with:

jetformat pdf render report.pdf --pages 1,10,last --width 1600 -o preview

Check the page count first. A page selector that fits this example may not fit a shorter document in the same batch.

Expand review when a defect appears

If a sample reveals clipping or font substitution, inspect other pages sharing the affected structure. After a layout fix, rerender changed pages. Review all pages when the cost of an unseen defect requires full visual coverage.

The render guide explains selectors, and PDF inspection supplies the page counts for your own estimate. Use the credit estimate article when the workflow also includes conversion and editing.

Last updated