Skip to main content
Every PDF.co API endpoint consumes credits when you call it. This page lists the credit cost of each endpoint so you can estimate how many credits a workflow will use before you run it. Endpoints are charged in one of two ways, per processed page or per API call, and the tables below are grouped accordingly.
For a quick estimate, use the interactive Credit Calculator on the Subscriptions page. It lets you pick an endpoint and page count and shows the credit cost instantly.

How to estimate credits

For example, converting 5,000 one-page PDFs to JPG with /v1/pdf/convert/to/jpg uses 5,000 × 12 = 60,000 credits. If each document has multiple pages, multiply by the total number of pages. For example, 5,000 documents with 3 pages each is 15,000 pages, so PDF to JPG would use 15,000 × 12 = 180,000 credits.

Endpoints charged per page

Endpoints charged per API call

Notes

  • Estimated credits are calculated for sync mode and could differ in async mode.
  • Some workflows make more than one API call. For example, uploading a file separately before processing it consumes upload endpoint credits in addition to the processing endpoint credits.
  • Async jobs may require status checks with /v1/job/check, which is listed separately in the per API call table.
  • To check the remaining credits in an account, use /v1/account/credit/balance.
  • You can also estimate costs with the Credit Calculator on the Subscriptions page.