Techniques··4 min read

Preparing Multilingual Documents for AI Translation

Get better AI translations by cleaning source text, preserving structure, and handling token costs for non-English languages.

Structure carries over

Convert source documents with PDF to Markdown so headings and lists survive translation. For many files, use the Batch Document Extractor.

Watch the token count

Paste a sample into the Token Counter. Languages like Japanese or Hindi can use noticeably more tokens than English for the same content, affecting cost and chunk size.

Use a glossary

Give the model a short glossary of product names and terms that must stay consistent, and translate section by section.

Try it free in your browser

  • PDF to Markdown — Headings, lists, and structure preserved. Perfect for Obsidian, GitHub, RAG, and LLM context.
  • Token Counter — Live token, character, and context-window meter for any prompt. Uses official tiktoken encoders.
  • Batch Document Extractor — Drop PDFs, images, Word docs, and text files together. Get clean text out — combined or zipped one-per-file. Browser-side OCR included.

Tools mentioned

Frequently asked

Why do other languages cost more tokens?

Tokenizers are trained mostly on English, so other scripts and languages often split into more tokens per word.

Should I translate in chunks?

Yes, by section. It keeps terminology consistent when you provide a glossary.

Keep reading