Snip Snipping Tool Chrome Extension OCR API Files API Secure Conversion Service
Make Documents Accessible Process Chemical Documents Collaborate on Documents Developer Solutions Train Language Models Support Academic Research Artificial Intelligence Fintech Edtech Pharma & Chemical Universities & Schools
Handwriting Recognition Digital Ink On-prem PDF Cloud Mathpix Markdown All Supported Languages Image Conversion PDF Conversion Markdown Conversion Table OCR Mathpix CLI PDF Search PDF Reader PDF Data Extraction Chrome Extension View Conversion Gallery
Snip APIs SCS
Mobile Desktop Web Chrome Extension
Mathpix Snip Apps Mathpix OCR API Mathpix Markdown Python SDK
Blog
About Careers Contact
Contact Get Started

Rate and page limits

Limits control the number of images and pages processed in a given time period to prevent overuse. It is crucial for maintaining the efficiency and reliability of Mathpix OCR API for all users.
Limits are per API key, not per organization. Each key carries its own rate limit and page limit, and they are shown in the RATE LIMIT and PAGE LIMIT columns of the API Keys tab on console.mathpix.com. If you split traffic across several keys, each one gets its own allowance — and each one can be raised independently.

Defaults

Limit Default Applies to
Rate limit 200 requests / minute Synchronous image requests — v3/text, v3/latex
Page limit 20,000 pages / month v3/pdf and files/v1, which share one allotment
API key limit Set per organization How many keys you can create
Enterprise accounts are provisioned separately and may start from different values; the API Keys tab always shows what your key actually has.
Monthly limits reset at the start of each calendar month.

The rate limit only applies to synchronous requests

A request that asks for a result immediately counts against the per-minute rate limit. A request that does not, is not rate limited per minute at all:
  • Sending async: true, or supplying a callback, on v3/text exempts that request.
  • v3/batch submissions are exempt.
Those requests are queued as background work, so they are governed by your monthly allowances rather than by a per-minute ceiling. If you are hitting the rate limit on a workload that does not need an immediate answer, moving it to async is usually a better answer than asking for a higher limit.

Image volume

There is no monthly image limit by default, so image volume itself is uncapped. One can be set on a key on request — for example as a deliberate cost ceiling — in which case requests beyond it are rejected rather than billed.

Requesting an increase

Limit increases are self-service. Open the Requests tab of your organization on console.mathpix.com and click Make a request. You can raise three things:
  • Rate limit — requests per minute for a chosen key.
  • Page limitv3/pdf pages per month for a chosen key.
  • API key limit — how many keys the organization may create.
Select the API key, enter the new value (it must be higher than the current one), and optionally add a link to your website and a reason — both help us approve faster. The request appears in the Pending requests table with its quota type, old value, new value, and requestor, and we email you when it is applied.
You do not need to open a support ticket for a routine increase. For anything unusual — a contractual commitment, a one-off burst, or a limit we do not expose in the Console — email support@mathpix.com.

Lowering a limit on purpose

A lower rate limit is the only hard cap on throughput: requests above it are rejected rather than processed and billed. If you want that guardrail, email support@mathpix.com — the Requests tab only raises limits.
For a softer guardrail that warns instead of rejecting, configure per-key spike and daily burn-rate alerts on the Usage tab. See Usage alerts.

Watching your usage against them

The Console Usage tab charts requests and estimated cost per key over time, and exports the same numbers to CSV. v3/ocr-usage returns the same data hour by hour for your own dashboards. See Usage and results.