How to PDF API Rate Limits

Rate limits protect the SublimePDF API from abuse and ensure fair resource allocation across all users. Understanding your plan's rate limits, monitoring your usage, and implementing proper throttling prevents disruptions in your PDF generation workflow. This guide explains rate limit tiers, response headers, and strategies for staying within limits.

Follow the step-by-step instructions below, then use the free tool directly — no registration or download required.

Open Tool →

How to PDF API Rate Limits — Step by Step

1

Check your plan's rate limits

View your current rate limits in the SublimePDF dashboard under Settings → Usage. Free plans allow 10 requests/minute, Pro plans 100 requests/minute, and Enterprise plans have custom limits. Batch endpoints have separate, lower limits.

2

Read rate limit response headers

Every API response includes three headers: X-RateLimit-Limit (your max requests per window), X-RateLimit-Remaining (requests left in the current window), and X-RateLimit-Reset (Unix timestamp when the window resets). Monitor these proactively.

3

Implement client-side throttling

Use a rate limiter in your application code (e.g., p-limit or bottleneck in Node.js, ratelimit in Python) to cap outgoing requests below your API limit. This prevents bursts that trigger 429 errors.

4

Handle 429 responses correctly

When you receive a 429 Too Many Requests response, read the Retry-After header value (in seconds). Queue the failed request and retry after that duration. Do not hammer the API with immediate retries.

5

Use batch endpoints for bulk operations

Instead of sending 100 individual render requests, use POST /api/v1/render/batch with an array of up to 50 data objects. Batch requests count as a single API call against your rate limit and process more efficiently.

Pro Tips

  • 💡 Track the X-RateLimit-Remaining header in your application and proactively slow down requests when it drops below 20% of your limit — this prevents hitting the wall.
  • 💡 If you need to generate a large number of PDFs (1000+), use batch endpoints combined with async mode and webhook callbacks instead of synchronous individual requests.
  • 💡 Rate limits reset on a rolling window, not a fixed clock — so a burst at 11:59 PM doesn't get a free reset at midnight.
  • 💡 Contact sales for Enterprise plans if your application consistently needs more than 100 requests/minute — custom rate limits are available with dedicated infrastructure.

Privacy & Security

All processing happens directly in your browser. Your files are never uploaded to any server — they remain on your device throughout the entire process. SublimePDF uses WebAssembly technology for fast, secure, client-side processing.

Works Everywhere

This tool works on any modern browser — Chrome, Firefox, Safari, or Edge — on desktop, tablet, or mobile. No software to install. PDF is an open ISO standard supported by all major platforms.

How to PDF API Rate Limits — FAQ

Do all endpoints share the same rate limit?
Generation endpoints (html-to-pdf, render, url-to-pdf) share a combined rate limit. Management endpoints (templates, webhooks, account) have a separate, higher limit of 300 requests/minute. Batch endpoints count as one request each.
What happens if I exceed the rate limit?
The API returns a 429 Too Many Requests response with a Retry-After header. No PDF is generated for that request. Your existing in-flight requests continue processing normally.
Are rate limits per API key or per account?
Rate limits are per account, shared across all API keys. If you have three keys each making 40 requests/minute on a 100/minute plan, they collectively consume 120 and will start receiving 429 errors.
Can I see my historical rate limit usage?
Yes. The dashboard's Usage page shows request volume over time with a graph indicating when you approached or hit rate limits. Use this data to plan your batch processing schedules around low-traffic periods.

Ready to get started?

Use SublimePDF's free tools right now.

Open Tool