By Jetformat
A credit estimate is a count of the successful operations a document workflow will perform. Jetformat uses page-based units for PDF conversion and rendering, and command-based units for Office edits. An estimate should identify those units separately before adding them.
Worked examples, not measured benchmarks
The table below uses the current billing rules. These are arithmetic examples with stated page counts, not performance measurements or promises about the size of your files. The conversion result determines actual PDF page counts.
| Example workload | Calculation | Credits |
|---|---|---|
| Convert a 12-page DOCX | 12 output pages × 1 | 12 |
| Render 3 preview pages | 3 rendered pages × 1 | 3 |
| Fill one Word template | 1 Office write command × 1 | 1 |
| Convert that filled 12-page document | 12 output pages × 1 | 12 |
| Read PDF info for any of these outputs | Free read | 0 |
Add the operations in the workflow
Filling one template, converting a resulting 12-page document, and rendering three preview pages totals 1 + 12 + 3 = 16 credits. Text extraction and PDF inspection add zero. Rendering every page instead would make the same example 1 + 12 + 12 = 25 credits.
An XLSX worksheet count is not a PDF page count. A wide or long sheet can produce several pages. Inspect representative output before estimating a large batch, and leave room for variation in pagination.
Separate usage units from cash pricing
Credits describe operations. Subscription allowances and purchased packs determine how you obtain them; this table does not calculate a universal cash price per job. Check pricing for the current plans and packs.
Use PDF info to measure output pages and selected-page rendering to choose a review scope. Failed jobs are not charged under the documented billing rules.
Build an estimate step by step
- List each operation that will create a document or preview, including intermediate writes.
- Mark each operation as output pages, input pages, rendered pages, or Office write commands using the pricing table.
- Convert a representative document and inspect its actual PDF page count.
- Choose how many preview pages the review requires.
- Add the units, then compare the result with the account’s available credits before starting the batch.
Do not count a whole workflow as one operation just because a shell script launches it. Filling a template and converting the filled document are two writes with different billing units.
Batch example with explicit assumptions
Suppose a batch contains 10 documents, each producing 12 PDF pages, and each document receives 3 page previews. The conversion portion is 120 pages, or 120 credits. The preview portion is 30 pages, or 30 credits. Together that is 150 credits before any Office edits. If each document also requires one template-fill command, add 10 credits for 160 credits total.
Those page counts are assumptions for the example. A longer customer name, wider table, changed font, or additional section can change actual pagination. For variable templates, test more than one representative input rather than multiplying the smallest result by the whole batch.
Keep estimates separate from observed usage
Record estimated counts and final counts as separate values. When a document has more pages than expected, inspect its layout before treating the higher usage as a billing problem. Conversely, a surprisingly short PDF may be missing content and needs review even though it used fewer credits.
Free inspection can be repeated without adding conversion credits. A successful rerun of a paid write is another operation, so include deliberate regeneration and extra previews in planning. An unsuccessful job is not billed, but the later successful retry still has its normal unit count.
Choose a review scope deliberately
Use all-page review when every page matters. Selected-page rendering is appropriate for a stated sampling plan, but it cannot certify the appearance of pages that were never viewed. Keep the estimate honest by labeling the number of pages reviewed instead of calling a sampled workflow “fully verified.”
The preview sampling examples show this tradeoff; the billing guide explains the units used here. No speed, accuracy, or financial savings benchmark is implied by these calculations.