Contact Get Started
Snip Snipping Tool Chrome Extension Convert 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 Convert API Files API SCS
Mobile Desktop Web Chrome Extension
Mathpix Snip Apps Convert API Mathpix Markdown Python SDK
About Blog Careers Contact
Contact Get Started
← Back to Blog

Introducing eu.api.mathpix.com: EU data residency for the Mathpix API

2026-07-21 · api, updates
Today we are launching eu.api.mathpix.com, a production deployment of the complete Mathpix API hosted entirely in the European Union, for customers whose compliance or contractual requirements demand that document data stays in the EU.

What stays in the EU

When you call eu.api.mathpix.com, everything derived from your documents is processed and stored in EU data centers:
  • Document processing runs on compute in Frankfurt and Falkenstein.
  • Uploaded documents, page images, and conversion outputs (Markdown, DOCX, and more) are stored in EU-resident object storage.
  • OCR results (the full recognition output for every image and PDF page) are stored in an EU-resident results database.
  • Document tracking and job state live on dedicated EU database infrastructure.
  • Cropped images and figures referenced in your results are served from eu-cdn.mathpix.com, an EU-regional endpoint with no global CDN in the path.
  • Operational telemetry from the EU deployment is likewise kept in the EU.
Only account metadata that is not derived from your documents (API key authentication and usage counts for billing) is handled by our existing global account infrastructure.

Same API, one line to change

The EU endpoint serves the full Mathpix API surface: image OCR (/v3/text), PDF processing (/v3/pdf), conversions (/v3/converter), and the Files API (/files/v1/*), including remote sources and customer-bucket destinations via data sources. Your existing API keys work as-is. Simply change the base URL:
curl -X POST https://eu.api.mathpix.com/v3/text \
  -H "app_id: YOUR_APP_ID" \
  -H "app_key: YOUR_APP_KEY" \
  -F "file=@document.jpg" \
  -F 'options_json={"formats": ["text"]}'

Result queries are per-region

Results live in the region that processed them and are queryable from that same endpoint: GET https://eu.api.mathpix.com/v3/ocr-results lists documents processed through the EU endpoint, while the same call on api.mathpix.com lists documents processed through the global endpoint. Result histories are never merged across regions: an EU-processed document is queryable only from eu.api.mathpix.com. This is the residency guarantee doing its job: your EU results have no path through US infrastructure, including at query time.

Console support

The Mathpix Console works with both endpoints:
  • Playground: an endpoint selector lets you send test documents to eu.api.mathpix.com; they are processed and stored in the EU, straight from your browser to Frankfurt.
  • Results: the same region selector switches the results view between endpoints, following the per-region rule above.
  • Usage and billing are shared across endpoints: one account, one plan, one bill. Usage from api.mathpix.com and eu.api.mathpix.com counts against the same quotas and appears together.

What this means for your compliance

GDPR permits processing EU data in the US under standard transfer mechanisms, and the global endpoint remains fully supported on that basis. What eu.api.mathpix.com changes is that no cross-border transfer mechanism (SCCs, adequacy reliance, or transfer impact assessments) is needed for your document data at all. That removes a branch of compliance paperwork for your data-protection team, insulates your document workflows from ongoing EU-US transfer litigation, and supports frameworks that require EU processing outright (health, financial-services, and public-sector rules in several member states). Account metadata (API-key authentication and usage counts for billing) continues to be handled by our global account infrastructure. EU residency commitments can be incorporated into your Data Processing Agreement: contact us to set that up.

A note on api.mathpix.com

The global api.mathpix.com endpoint continues to operate exactly as documented, with data processed and stored in the United States. If your organization has EU data residency requirements, or you simply want in-region latency from Europe, switch to eu.api.mathpix.com.

If you use our EU regional URLs directly, please migrate

If you call our EU regional hostnames directly (https://img-eu-central-1.api.mathpix.com/ or https://eu-central-1.api.mathpix.com/), please migrate to https://eu.api.mathpix.com/.
In one week, these regional hostnames will be re-routed to our US infrastructure as we consolidate EU serving onto the new EU-resident deployment. Nothing will break (your requests will keep working with the same keys and the same behavior), but you will lose in-region latency. Requests to api.mathpix.com from clients near the EU will likewise be served from the United States from that point on.
Moving to eu.api.mathpix.com is a drop-in replacement (same API, same keys) and upgrades you to lower EU latency and EU data residency.

Getting started

The EU endpoint is available now for all API accounts at our standard API rates. See the EU data residency documentation for details. If you have contractual data-residency requirements and want to discuss your setup, or you’d like help migrating existing workloads, reach out to us at support@mathpix.com.