How Are Credits Spent for Async Jobs?

Wondering how credits are spent when you run a PDF.co job in async mode vs. sync mode? Here’s what you need to know.

Key Differences: Sync vs. Async

Sync Mode:
- Charges credits per page
- Processes everything immediately
- Example:
  → 10-page PDF at 21 credits/page → 210 credits total
Async Mode:
- Charges a flat endpoint cost
- Small extra charge per /job/check call
- Example:
  → 10-page PDF at 21 credits + 4 checks at 2 credits each
  → 21 + (4 × 2) = 29 credits total

Async mode can be much cheaper, especially for multi-page files.

In sync mode, credits = endpoint × number of pages.
In async mode, credits = endpoint + (credits per /job/check × number of checks).

You’re not charged per page in async mode—the endpoint cost is flat.

Use webhooks instead of polling → webhooks notify you when the job finishes, so no need for /job/check calls.
Poll less often → each /job/check call uses credits. Only check every 10–15 seconds for large files.
Use async mode for large files → prevents timeouts and credit overuse.

Mode	10-page PDF Example
Sync	21 credits/page x 10 = 210 credits
Async	21 credits (flat) + (4 checks x 2 credits) = 29 credits