Sejda · Rate Limits

Sejda Rate Limits

The Sejda HTML to PDF API does not meter or cap the total number of PDFs generated. Instead it limits the maximum number of requests per hour and the number of concurrent (in-flight) requests, both of which scale with the subscription tier. Exceeding either limit returns HTTP 429. A self-hosted deployment removes the requests-per-hour restriction. Request payloads are capped at 50MB (HTTP 413 when exceeded). Sejda's free web/desktop apps apply separate page, hourly, and per-tool limits unrelated to the API.

Sejda Rate Limits is the machine-readable rate-limit profile for Sejda on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, concurrency, and bytes.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and payloadTooLarge.

Tagged areas include PDF, HTML to PDF, Rate Limiting, Quotas, and Throttling.

3 Limits Throttle: 429
PDFHTML to PDFRate LimitingQuotasThrottling

Limits

Requests Per Hour account
requests
tier-based (200 / 300 / 600 / 1,200+ per hour)
Maximum requests per hour; scales by API subscription tier. Self-hosted has no per-hour limit.
Concurrent Requests account
concurrency
tier-based (3 / 4 / 5 / 6-48 concurrent)
Maximum simultaneous in-flight requests; scales by API subscription tier.
Payload Size request
bytes
50MB
Generated PDFs / request payloads must be under 50MB; HTTP 413 otherwise.

Policies

Tiered Limits
Requests-per-hour and concurrency raise as accounts move up API subscription tiers or self-host.
No Document Metering
Sejda does not count or cap the number of PDFs generated; only request rate and concurrency are limited.
Backoff Strategy
On HTTP 429, clients should back off and retry; requests are not auto-upgraded.

Sources