Transept

Translate

Document translation that holds together

DOCX, PDF, Markdown — uploaded, parsed into blocks, translated with the rest of the document for context. Page 1 reads like page 300; the headings stay headings, the lists stay lists, the formatting comes back where it started.

Start translating→

Free to begin · No card required

In context✦

Document translation is the deepest end of AI translation — and the place generic tools break first. A DOCX with tables, footnotes, and a 200-page running header isn’t one sentence repeated; it’s a structured artifact where formatting carries meaning. A PDF research paper has citation markers that need to survive the round trip. A Markdown file from a documentation site has code blocks that should never be translated. Transept treats every document as structured content from the moment it’s uploaded — parsing it into blocks that map back to their original positions on export — so the file that comes out reads like the file that went in, only in another language.

From file to finished translation, one workspace

Drop the file in, pick your language pair, and pick the mode. Everything else — context, glossary, styleguide, review — happens inside the editor instead of across five tabs and a chat thread.

  1. Upload or paste

    DOCX, PDF, Markdown, TXT. Or paste raw text. Or import directly from Notion or Google Drive. The file becomes blocks that map back to their original positions on export.

  2. Translate with document context

    Each block is translated with awareness of the surrounding document — the chapter, the heading hierarchy, the recurring terms. Long-document drift, the thing DeepL and ChatGPT lose at page 50, doesn’t happen here.

  3. Edit at the sentence

    Click any sentence to see alternatives, regenerate with a direction, or rewrite by hand. Your edits feed back into the styleguide so the rest of the document picks up the change.

  4. Export back to where you started

    DOCX out for clients, Markdown for engineers, Notion or Google Docs for content workflows. The export keeps the formatting that came in.

Transept editor showing a translated DOCX side-by-side with the original

Built for the long ones

Client deliverables

Freelance translators and agencies handing in DOCX files. Glossary per client, styleguide per project, QA before the email goes out.

Knowledge bases

Help centers, product docs, and policy documents where terminology consistency across the whole library is the entire point.

Long-form content

Books, reports, white papers, research — the work where the voice has to survive the trip into another language.

Footnotes✦

Questions, answered without the fluff

  • Upload DOCX, PDF, Markdown, or TXT. Or import from Notion or Google Drive. Or paste raw text. Export back to DOCX, Markdown, Notion, or Google Docs.
  • Yes — headings stay headings, lists stay lists, bold and italic stay where they were. We parse the file into structured blocks rather than treating it as a wall of text, so the export comes back with the same shape.
  • There is no hard limit. The Free plan covers 1,500 words per month — enough for a short article. Starter at $19/month covers 100,000 words, which is roughly a 330-page book.
  • Yes — and batch translation handles the matrix of files × languages in one queue. Glossary and styleguide apply across all targets so the terminology stays put.
  • A chat window will translate text from a DOCX, but you lose the formatting on the way out and have to rebuild headings, lists, tables, and bold/italic by hand. Transept preserves the structure end to end — the DOCX you export has the same headings, the same tables, the same formatting, in the new language.
  • Transept handles searchable PDFs natively. For scanned PDFs (image-only), run them through OCR first — we recommend Adobe Acrobat or a free option like OCRmyPDF — then upload the resulting PDF. We’re building native OCR into the pipeline; for now the extra step is required.
  • Yes — batch translation handles the matrix of one document × many target languages in one queue. Glossary and styleguide apply across all targets so the terminology stays consistent.
  • Track changes are accepted before translation; the resulting clean text is what gets translated. Comments in the source are not carried into the translated export by default — they live in the original. If you need them as part of the translated artifact, ask in support and we can wire it.
  • A 480-page reference manual, translated EN→DE with a 60-term glossary, in Premium mode. Total run time: about 35 minutes. The translator who delivered it said the glossary enforcement caught three terms his old workflow missed on a previous edition.
Related✦

Keep reading around this capability

❧

Drop a 50-page document in and have it back, ready to deliver, before lunch

Start translating→

Free to begin · No card required