Translate a document and keep its layout
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
A file of the same type with text translated and tables, headings, numbers, tags and images in place, delivered by an async job whose done status means the file is ready, with a readable error for unsupported or oversized input.
Measured, for our own tests: a 20-page DOCX completes within 2 minutes. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: translate this PDF into German
, give me this contract in French, same layout
, translate these subtitles
, translate the slide deck
Does the job, with a limit 12
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Amazon Translate BB Amazon Web Services, Inc. | Batch jobs translate .docx, .pptx, .xlsx, HTML, text and XLIFF 1.2 with a status endpoint, but need S3 buckets and an IAM service role set up first; real-time documents stop at 100,000 bytes. No PDF. source |
| Azure Translator BB Microsoft Corporation | Synchronous single-file translation returns the document directly with no storage account, but batch jobs need Blob storage and SAS or managed identity, and first-hand reports saw Succeeded before blobs existed and storage-role blocks. source |
| Crowdin BB Crowdin OÜ | Documents and subtitles are among the 50 supported formats, translated by upload, pre-translation and an asynchronous build with status polling, so a file takes several calls and a project rather than one job. source |
| DeepL API BB DeepL SE | Upload, status and download handle DOCX, PPTX, XLSX, PDF, HTML, XLIFF, SRT and more, with per-format size limits published and no storage account. Open reports: jobs over about 15,000 characters failing with 'too many errors', and no detected language on document calls. source |
| Google Cloud Translation BB Google LLC | Online document translation returns DOCX, PPTX, XLSX and PDF up to 20 MB (300 native PDF pages) with detectedLanguageCode and no bucket; batch needs Cloud Storage roles. A first-hand report found document translation and glossary would not work together. source |
| Lara Translate API B Translated s.r.l. | Translate Document covers Word, Excel, PowerPoint, OpenDocument, Apple, PDF, HTML, Markdown and more, but limits, job status and error behaviour were not read, and each file bills at least 20,000 characters. source |
| LibreTranslate D LibreTranslate | /translate_file takes a file and returns a translated one synchronously, but the formats, size limits and layout handling are not stated on the operation page, and there is no async job or status. source |
| Lokalise BB Lokalise, Inc. | Document and marketing projects exist, but translation is an automatic_translation task followed by an export, not a single job that returns the same file; document limits were not read. source |
| Phrase B Phrase a.s. | /v1/fileTranslations takes a file, target languages and term bases; the metadata endpoint reports each action until no longer RUNNING and results are fetched once action.status is OK, with no storage account. Formats, size limits and oversize errors were not in the spec. source |
| Smartcat D Smartcat Platform Inc. | Projects take uploaded documents, track translation status and export the result, with Retry-After on 429, but each file needs a project, a workflow and an export call, and supported document formats were not read. source |
| SYSTRAN Translate API E SYSTRAN SAS | /translation/file/translate with async, then status and result by requestId, plus a supportedFormats endpoint, cover document jobs without a storage account, but format and size limits for files and layout handling were not shown on the reference. source |
| TranslatePlus E PetaBytes, Inc. | Subtitles (SRT, VTT) and i18n files are translated, but there is no DOCX, PDF or slide document endpoint. source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Localazy C Localazy s.r.o. | Release notes mention document translation, but no document translation endpoint, format list or job status was found in the API docs read. |
Doesn't do this job 3
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Lingo.dev B Replexica, Inc. | No document translation; the API and CLI handle key-value content and locale files, not DOCX, PDF or slides. source |
| Lingvanex Translation API F Nordicwise Limited | The cloud API spec has text and HTML translation only, with no document upload or job endpoint. source |
| POEditor MCP server E Code Whale Inc. | Handles localisation strings and Figma pages, not DOCX, PDF or slide documents. source |
What stops agents finishing
- document size or character cap with an unhelpful error
- document jobs need a cloud storage account and role set up by a person
- status reports done before the file can be fetched
- glossary not accepted on document calls
Around it
Before: file-storage.get-file, chat.user-uploads-file, document-extraction.ocr. After: file-storage.save-file, email.send-attachment, e-signatures.send-for-signature.
Where this comes from
Weight 19 of 100 in Translation: 12 of 55 accounts (layout broken, numbers dropped, size and character limits, job status, storage set-up)
The same as data: /api/v1/use-cases/translation.translate-document.json, or the MCP tool get_use_case with id translation.translate-document. Other jobs in this category: /api/v1/niches?category=translation.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.