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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-06-25.
Written by API Evangelist on 2026-06-25 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/sejda-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.