§ Compare
Everyone bills a different unit. That is the problem.
A credit means something different on every endpoint, and then it multiplies by pages, by megabytes, by compute-seconds, or by files you happen to be storing. Here is what each of the four actually charges for.
| Service | One unit of billing is | What makes the bill go up |
|---|---|---|
| ohmywrap | One API call. | Nothing. Same price at every file size, page count, and step count. |
| PDF.co | A processing credit. | The endpoint, the page count, and the options you turn on. |
| iLoveAPI | A credit. | Whether the job is counted per file, per page, or per task. |
| Api2Pdf | A megabyte, plus a compute-second. | File size, and how long the servers took. |
| Cloudflare Images | An image stored. | How many images you are still keeping this month. |
Published rates as of September 2026. Check each vendor’s own pricing page before quoting them.
Every one of these is a decent product. None of them can tell you what your next call costs.
On raw price, a tenth of a cent puts us at or below most of the field, and the gap widens with the size of the job. A competitor’s cheapest single-credit operation may beat us on a one-page file. On a 50-page document, or any pipeline, we come out ahead.
§ One at a time
ohmywrap vs PDF.co
Watermark a 300-page policy document.
Read the comparisonohmywrap vs iLoveAPI
Merge 20 invoices, each 4 pages.
Read the comparisonohmywrap vs Api2Pdf
Compress a 90 MB scanned bundle.
Read the comparisonohmywrap vs Cloudflare Images
Resize one upload, then never look at it again.
Read the comparisonYour first call takes one line of curl.
No plan to choose. No credits to model. No storage to configure.
10,000 calls for $10. No subscription, no expiry.