Davix H2I applies usage limits to define how much work a request or plan can perform across the public API. These limits help keep processing stable and give developers clear operational boundaries when building against the platform.
Requests sent to Davix H2I are processed by the platform layer behind the product, including the H2I engine (PixLab) for rendering workflows. Usage limits affect request size, uploaded files, HTML rendering, PDF page operations, monthly quota, and request runtime behavior across the public API.
What this page covers #
This page is the canonical reference for customer-facing non-rate limits on:
POST /v1/h2iPOST /v1/imagePOST /v1/pdfPOST /v1/tools
It covers:
- monthly usage quota
- per-file upload size
- total upload size per request
- maximum files per request
- image dimension limits
- H2I HTML and render limits
- PDF page caps for supported actions
- request timeout allowances
For request-frequency limits, use Rate Limits.
Usage limits by plan #
| Limit | Free | Pro | Business |
|---|---|---|---|
| Monthly usage quota | 150 | 1000 | 5000 |
| Max files per request | 1 | 3 | 5 |
| Max total upload per request | 5 MB | 15 MB | 30 MB |
| Max upload size per file | 5 MB | 15 MB | 30 MB |
| Request timeout | 20 seconds | 45 seconds | 60 seconds |
| Max image dimension | 2000 px | 4000 px | 6000 px |
| H2I max HTML size | 20,000 chars | 50,000 chars | 100,000 chars |
| H2I max render width | 2000 px | 4000 px | 6000 px |
| H2I max render height | 2000 px | 4000 px | 6000 px |
| H2I max render pixel area | 4,000,000 | 16,000,000 | 36,000,000 |
PDF max pages: to-images | 5 | 20 | 50 |
PDF max pages: extract-images | 5 | 20 | 50 |
PDF max pages: split | 5 | 20 | 50 |
| Image max files per request | 1 | 3 | 5 |
| PDF max files per request | 1 | 3 | 5 |
| Tools max files per request | 1 | 3 | 5 |
| Image max total upload | 5 MB | 15 MB | 30 MB |
| PDF max total upload | 5 MB | 15 MB | 30 MB |
| Tools max total upload | 5 MB | 15 MB | 30 MB |
| Image max dimension | 2000 px | 4000 px | 6000 px |
| Tools max dimension | 2000 px | 4000 px | 6000 px |
Monthly usage quota #
Customer API keys can have a monthly usage quota associated with their plan. This quota applies across the external API. When the quota has been exhausted, the API returns:
monthly_quota_exceeded- HTTP
429
The monthly quotas are:
- Free: 150
- Pro: 1000
- Business: 5000
Use this limit to plan how many total operations a customer key can perform during the billing period.
File upload limits #
Upload-based endpoints enforce limits on:
- individual file size
- total upload size per request
- number of files per request
These limits apply to:
/v1/image/v1/pdf/v1/tools
Relevant errors are:
file_too_large(413)total_upload_exceeded(413)too_many_files(413)
Upload limits by plan #
| Limit | Free | Pro | Business |
|---|---|---|---|
| Max upload size per file | 5 MB | 15 MB | 30 MB |
| Max total upload per request | 5 MB | 15 MB | 30 MB |
| Max files per request | 1 | 3 | 5 |
H2I HTML and render limits #
The /v1/h2i endpoint enforces H2I-specific limits for HTML rendering requests.
Relevant error codes are:
html_too_large(413)render_size_exceeded(400)
H2I limits by plan #
| Limit | Free | Pro | Business |
|---|---|---|---|
| Max HTML size | 20,000 chars | 50,000 chars | 100,000 chars |
| Max render width | 2000 px | 4000 px | 6000 px |
| Max render height | 2000 px | 4000 px | 6000 px |
| Max render pixel area | 4,000,000 | 16,000,000 | 36,000,000 |
If the HTML payload exceeds the allowed size, the API returns html_too_large.
If the requested render size exceeds the allowed limit, the API returns render_size_exceeded.
Image dimension limits #
Uploaded images are subject to dimension limits on:
/v1/image/v1/tools
When an uploaded image exceeds the allowed dimension limit, the API returns:
dimension_exceeded- HTTP
400
Dimension limits by plan #
| Endpoint group | Free | Pro | Business |
|---|---|---|---|
| Image uploads | 2000 px | 4000 px | 6000 px |
| Tools uploads | 2000 px | 4000 px | 6000 px |
PDF page and action limits #
The /v1/pdf endpoint applies page caps for selected actions.
The supported page-capped actions are:
to-imagesextract-imagessplit
When a page-capped action exceeds its limit, the API returns:
pdf_page_limit_exceeded- HTTP
413
PDF page caps by plan #
| Action | Free | Pro | Business |
|---|---|---|---|
to-images | 5 pages | 20 pages | 50 pages |
extract-images | 5 pages | 20 pages | 50 pages |
split | 5 pages | 20 pages | 50 pages |
Request timeout limits #
Each external /v1/* request is subject to timeout handling. When a request exceeds the allowed processing time, the API returns:
timeout- HTTP
503
Timeout allowances by plan #
| Plan | Timeout |
|---|---|
| Free | 20 seconds |
| Pro | 45 seconds |
| Business | 60 seconds |
Temporary capacity limits #
Davix H2I also protects the platform with temporary processing-capacity controls. When the service cannot acquire processing capacity for a request, the API returns:
server_busy- HTTP
503
This is a temporary service-capacity condition rather than a plan allowance or validation limit. Client applications should treat it as a transient failure and reduce burst pressure or retry cautiously.
Usage limits are different from rate limits #
Usage limits and rate limits are separate:
- Usage limits cover quota, upload size, file count, dimensions, H2I rendering limits, PDF page caps, and timeout allowances
- Rate limits control how quickly requests can be accepted
For request-frequency controls, use Rate Limits.
How to use this page #
Use this page as the canonical reference for customer-facing non-rate limits. Other documentation pages should link here instead of repeating quota, file-size, render, page, or timeout values.
