Tinify API credit bundles vs. pay-per-compression: Which pricing model works for you?
The Tinify image compression API has always offered pay-per-compression, where you pay only for what you use. It's flexible and automatic, which works well when usage varies from month to month.
But some teams need to know their costs upfront, before a project starts, not after it ends. That's why API credit bundles are now available alongside pay-per-compression. Both options are built around the same image optimization engine. The difference is how you pay for it.
Already know what you need?
Get a credit bundle and lock in your compression costs before your project starts.
Not sure which option fits your workflow? Read on for a side-by-side breakdown.
Pay-per-compression pricing for Tinify Developer API
With pay-per-compression, billing tracks your usage automatically. Each compression counts as one unit; each conversion counts as two. You pay for what you process, with no upfront commitment.
This pricing model works well for teams that integrate an image optimizer directly into their product or workflow, whether that's a bulk image compressor pipeline or a single-file upload flow. The API supports image compression and format conversion to JXL, AVIF, WebP, JPEG, and PNG, including compress PNG and JPEG to modern formats like WebP and AVIF.
Once set up, compression runs in the background without manual intervention, and usage can scale up or down as needed. For full integration details, refer to the Tinify API documentation.
Pay-per-compression is a good fit for you if:
✓ Automation matters more than upfront cost control
✓ Usage is continuous or difficult to predict in advance
✓ You prefer not to make upfront payments
✓ Convenience and scalability without planning are priorities
The only trade-off is that monthly spend can vary, since costs are tied directly to usage. For some teams, this flexibility is ideal. For others, estimating costs in advance can be harder, especially when image volume varies from month to month.
| Number of Compressions | Price |
|---|---|
| First 500 images per month | Free |
| Next 9,500 compressions | $0.009 per compression |
| Next 10,000 compression per month | $0.002 per compression |
API credit bundles: a prepaid alternative
API credit bundles offer a prepaid alternative to pay-per-compression, starting at just $9 for 1,000 credits. Instead of being billed automatically per image, you purchase a bundle of credits upfront. Each image compression deducts one credit, and each format conversion (for example, converting PNG to WebP or JPEG to AVIF) deducts two credits. When the credits run out, you can simply buy more manually via your account dashboard.
There's no subscription and no automatic renewal. Each purchase generates a single invoice, which keeps accounting simple. Credits never expire, so there's no pressure to use them before a deadline.
API credit bundles are a good fit for you when:
✓ You're working on a specific project with a defined scope
✓ You can estimate your image volume ahead of time
✓ You want a firm ceiling on what you'll spend
✓ Predictable invoicing matters for your team or clients
Two things to factor in: if your credits run out mid-project, processing stops until you top up. And if you overestimate your volume, some credits may go unused. Neither is a major issue, but both are worth accounting for when you decide how many credits to buy.
Ready to get started? Purchase a credit bundle and start compressing.
| Amount of Credits | Price |
|---|---|
| 1.000 Credits | $9 ($0.009 per credit) |
| 2.500 Credits | $22 ($0.0088 per credit - Save 2%) |
| 5.000 Credits | $40 ($0.008 per credit - Save 11%) |
A quick comparison
Both models include 500 free compressions per calendar month. The main difference between the two pricing models is how usage and costs are managed.
| Aspect | Pay-per-compression | API credit bundles |
|---|---|---|
| 500 free compression per month | ✓ | ✓ |
| Billing method | Automatic, usage-based | Prepaid, manual purchase |
| Cost predictability | Varies by month | Known upfront |
| Automation | Fully automated | Requires manual top-ups |
| Payment timing | After usage | Before usage |
| Invoicing | Usage-based billing | Invoice per purchase |
| Typical use case | Ongoing or unpredictable workflows | Fixed-scope projects |
Neither option replaces the other. They exist to support different ways of using the Tinify API. If you're new to Tinify, you can also compress images without losing quality directly on tinypng.com, no API key required.
Switching between pay-per-compression and credit bundles
Your pricing model isn't locked in. You can start with pay-per-compression while building your integration, then switch to credit bundles for a project with a defined scope. Or go the other way if your usage grows beyond what prepaid credits can comfortably cover.
Head to the Tinify image compression API pricing to review current rates and bundle options.
Frequently asked questions
01. What payment methods do you accept?
The Developer API accepts payments through several methods, including credit cards, PayPal, WeChat Pay, Alipay, and iDEAL. Payment method availability may vary by region.
02. Do API credit bundles expire?
No. Prepaid credits stay on your account until you use them, with no expiry date.
03. What happens when my prepaid credits run out?
Image optimization pauses until you purchase an additional bundle or switch to a pay-per-compression plan. You won't be charged anything beyond what you've already paid.
04. What happens to my unused credits?
Free monthly credits (500 per month) reset at the start of each calendar month and don't carry over. Prepaid credits remain on your account until spent.
05. Which pricing option is cheaper?
It depends on your usage volume and how predictable it is. For both models, the cost per compression decreases as volume grows.
For maximum flexibility, you can combine the two models: purchase a credit bundle to cover your predictable baseline and rely on pay-per-compression to handle unexpected spikes or one-off projects. Check the API pricing page for more details.
06. Can I combine the credit bundles with the pay-per-compression?
Yes. Both models can run on the same account. When you have an active credit bundle, compressions draw from your credits first. Your account switches to pay-per-compression once the bundle is fully used up. A common approach is to use a credit bundle for a fixed-scope project and let pay-per-compression handle anything beyond that automatically.
