Review & deliver
Export back to where you started
DOCX for clients. Markdown for engineers. Notion for content workflows. Google Docs for collaboration. Whatever format the source came in, the export comes back as the same — formatting intact, ready to ship.
Free to begin · No card required
Featured on
Translation that doesn’t round-trip your format costs you the time you saved on translating. The translator who has to rebuild headings and tables after exporting from ChatGPT loses an hour per document. The marketing team that gets back plain text instead of HTML loses the campaign. Transept treats the export as a first-class part of the workflow — DOCX in, DOCX out with formatting intact; Markdown in, Markdown out with structure preserved; Notion in, Notion out as a new page in your workspace. The file you ship is the file you started with, in another language.
How do you round-trip the format it came in?
Translation that doesn’t round-trip your format costs you the time you saved on translating. Transept exports respect the structure that came in — headings, lists, bold, links, tables, callouts.
Pick the format
DOCX for clients and editors. Markdown for engineering teams. Notion for content workflows. Google Docs for live collaboration. Plain text and HTML available too.
Formatting preserved
Headings stay headings. Lists stay lists. Bold and italic stay where they were. Tables stay tables. Callouts and code blocks survive.
Side-by-side export
Optional bilingual export with source and target as parallel columns — useful for client review, translator handoff, or QA archives.
Send it where it lives
Direct push to Notion or Google Drive if the source came from there. Or download and share manually.
Where does the export matter most?
Client deliverables
A DOCX with track changes-style export, ready to send to the client in the exact format they expect.
Engineering content
Markdown out for the docs site, or HTML for the help center, with the structure that came in.
Content sync
Notion-in, Notion-out — the localized page lands in your workspace next to the original.
8 hours → 50 minutes
One 40,000-word document, translated by several agents at once, used to take eight hours. We got the agents to sync their memory mid-run, so a term settled in chapter 2 still holds in chapter 40. It now finishes in fifty minutes.
How the syncing works— Don’t take our word for it —
The editor, in miniature
A working slice of the real thing — Literess, glossary, styleguide, workflows, and the translation memory are all live. Click around.
Here to help you translate
A key turned in the lock and the door swung open.
У замку повернувся ключ, і двері розчахнулися.
The knock came just before midnight.
Стукіт пролунав перед самою північчю.
FAQ
- For DOCX, Notion, and Markdown: yes. For PDF: we export to a clean Markdown or DOCX that you can re-PDF in your own tool — original PDFs aren’t a great format to write back to.
- Yes — bilingual export option lays source and target out as parallel columns. Useful for human-review handoffs.
- No hard limit. A 500-page book exports in a couple of minutes.
- Yes — selection export from the editor sidebar. Useful when you’re delivering work in stages.
- DOCX, Markdown, Notion (as a new page), Google Docs (via the Drive integration), HTML, and plain text. PDF export goes via DOCX or Markdown — re-PDF in your design tool to keep typesetting control.
- Yes — bilingual export lays source and target as parallel columns or interleaved blocks. Used most often for client review files, sworn translation handoffs, and QA archives.
- Yes. Tables stay tables (with translated cell content); footnotes stay footnotes (numbered consistently); headings keep their hierarchy.
- Yes — selection export from the editor sidebar lets you export a range of blocks instead of the whole document. Useful when you’re delivering in stages.
- Image references are preserved with their original positioning. Image alt text gets translated. The image files themselves aren’t translated — for image content with localized text inside, replace them in your design tool.
Keep reading around this capability
- FeatureDocument 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…
- Use caseTranslate the next client document→Per-client glossaries that travel across projects. Per-client styleguides that hold tone. Sentence-level review for the lines that matter.…
- Use caseLocalize the help center without breaking product terms→Help articles need a clear support voice, exact product UI strings, and zero drift across a hundred pages. Build a product glossary once,…