AI Document Translator

Translate documents into dozens of languages while keeping the original page layout, images, headings, and tables intact. Major Asian and right-to-left scripts included.

Pro AI tools send document content to xAI.

AI Translate is a Pro feature — included in PDFwarp Pro at $9 USD/month along with every other tool and unlimited conversions.

PDFs are translated in place: text is grouped into blocks, sent to xAI in batches of 60 segments, then drawn back onto the original page with Noto fonts for CJK/Arabic/Hebrew. Word files are translated paragraph-by-paragraph inside the .docx. If the overlay fails, you get a translated Word file instead of a broken PDF. 29 target languages. Pro only.

Why use PDFwarp for AI Translate?

How to use AI Translate — step by step

  1. Upload your document.
  2. Select the target language (and optional PDF font/size/align).
  3. Download the translated PDF or Word file.

Tips & best practices

It rewrites, not substitutes

Unlike word-for-word tools, the AI rewrites sentences idiomatically. Output reads like it was written in the target language — not like something that went through a translator.

Right-to-left and CJK use Noto on the overlay

The server picks Noto Arabic, Hebrew, CJK, Devanagari, or Thai from the sample text. If those fonts are missing in a broken deploy, glyphs can fail — that is a server font issue, not your file.

CJK and RTL often change fit

Chinese, Japanese, and Korean pack more meaning into fewer characters; Arabic and Hebrew change direction. The overlay shrinks-to-fit inside the original box. Expect different visual density, not a new page count, on the PDF path.

Under the hood

PDF path: batch translate, then paint

Words are grouped into blocks, translated in chunks of 60 via xAI, and drawn back with Pillow. Font size, family, and alignment come from the form when you leave Auto. A failed overlay falls back to extract-and-docx rather than returning an empty PDF.

Word path: in-place runs

DOCX paragraphs are translated in place so styles and most structure remain. If that path throws, the same extract-and-rebuild fallback runs. Plain text always becomes a .docx of the translation.

Why scans fail here

Overlay needs selectable text. A photographed page has none, so the route tells you to run AI Scan to Text — which is a different model (vision) and a different output (new text document).

Frequently asked questions

What languages are supported?

The 29 languages in the Target Language dropdown. That list is what the route accepts — it is not an open-ended 'any language' box.

Is the formatting preserved?

On PDF, yes for the page furniture (images, lines) — only the text blocks are replaced. On Word, paragraph and run structure stay; a failed overlay falls back to a new .docx of the translated text.

What if the PDF is a scan?

There is no text to overlay. Use AI Scan to Text first, or expect an error asking you to do that.

What plans support AI Translate?

AI Translate requires a Pro account. Upgrade at pdfwarp.com/pricing.

Related guides

Related tools