Doc Translator
Document translation that keeps the original layout
About Doc Translator
Doc Translator solves the part of document translation that is actually hard. Translating the words is the easy half; keeping a fifty-page PDF looking like a fifty-page PDF afterwards, with its columns, tables, fonts and page breaks intact, is the half that makes people paste text into a chat window and then spend an hour rebuilding the formatting by hand. This preserves the original layout, fonts and structure and gives you back the same document in another language.
The format coverage is the other reason to use it over a general-purpose model. Over fifty formats across 150+ languages, and the list goes well past office documents: PDF, DOC and DOCX, PPTX, XLS and XLSX, CSV, JSON, XML, YAML, EPUB, subtitle files in SRT and VTT, images in JPG, PNG, WEBP, HEIC and HEIF, plus Markdown and TXT. Structured formats matter more than they look. Translating a JSON or YAML file without breaking its keys, or an SRT without destroying its timecodes, is a specific job that a chat interface does badly and this does directly.
You can try it before creating anything. Upload a file, translate it and download the result with no account, no card and no queue, which is the right way to evaluate a tool whose whole value proposition is whether the output still looks right.
Upload a file, or paste text if it is a short passage rather than a document. The interface splits those two paths so you are not forced through a document flow for a paragraph.
Pick source and target languages, or leave the source on auto-detect. Auto-detect is the sensible default for anything you did not write yourself.
Translate and download. The output keeps the layout of the input, so a translated PDF is still a PDF with its structure intact rather than a wall of text.
Move up a tier if the files are large or the volume is real. The limits that separate the plans are upload size and how many jobs run at once, which are the two things that bite when you are translating a book or a batch rather than a letter.
- •Layout preservation - Columns, tables, fonts and page structure survive the translation, which is the entire reason to use this rather than paste text into a model
- •Over fifty formats - Office files, PDFs, EPUBs, images, subtitles and structured data, not just documents
- •Structured file handling - JSON, XML, YAML, SRT and VTT translated without breaking keys or timecodes
- •150+ languages with auto-detection on the source
- •Free with no signup - Upload, translate and download without an account or a card, so you can judge output quality first
- •Image translation - JPG, PNG, WEBP, HEIC and HEIF, for the case where the document is a photograph of a document
Anyone who has been handed a PDF in a language they do not read and needs it back in one they do, with the tables still readable. That is the core case and the free tier covers it without an account.
Teams localising documentation get the format coverage: Markdown, JSON and YAML in the same tool as the PDFs means the docs and the strings files go through one place.
Subtitlers and video teams get SRT and VTT handled properly, timecodes intact, which is otherwise a fiddly manual job.
Publishers and anyone working with EPUB are unusually well served, since ebook formats are commonly missing from translation tools.
Worth knowing before you pay: the headline prices are annual billing at a 50% discount, so the monthly figure is higher if you pay monthly. Check which you are being quoted. The plans differ on upload size and concurrent jobs rather than on translation quality, so pick the tier by the size of your files rather than by expecting better output.
Pricing
$9.90 - $39.90/mo
- Basic$9.90/mo
- Pro$19.90/mo
- Higher tier$39.90/mo
From the vendor pricing page, 2026-10-12
