Translate
Batch translation without the spreadsheet
A 30-file launch kit into 12 languages used to mean a spreadsheet, a project manager, and a week. With batch translation, it’s a queue you set up once and a delivery you ship the same day — same glossary, same styleguide, same QA across every file.
Free to begin · No card required
Featured on
Translating one document is a tactical decision. Translating fifty is a project — and projects are where AI translation tools usually fall apart. The glossary that worked on file one drifts by file thirty. The styleguide gets renegotiated between batches. Half the files come back without the formatting you started with. Batch translation in Transept treats the whole bundle as one job with shared context: one glossary across every file, one styleguide across every file, one queue you can monitor, one QA pass at the end. The 50-file deliverable that used to take a week now takes a quiet morning.
How does a batch run — a queue, not a project plan?
Drop the files in, pick the targets, hit run. Batch translation runs each file with shared resources — your project glossary, your styleguide, your model preference — so the output reads like one translator did all of it.
Upload the bundle
Drop in DOCX, PDF, Markdown, or HTML files. Or import a Notion or Google Drive folder. Or paste a URL list for HTML pages.
Pick the targets
One language pair, or a matrix — English to German, French, Spanish, Italian, Dutch, Polish, all at once. Fast, Standard, or Pro mode applies to the whole batch.
Shared context across every file
The glossary and styleguide you’ve set apply to every file in the batch. Character names, product terms, and brand voice stay consistent across files that would otherwise drift.
QA the whole batch in one pass
Smart Proofread runs across the batch and surfaces issues by file. Resolve, regenerate, ship.
When does batch change the math?
Product launches
Landing page + announcement email + FAQ + release notes + press kit, into ten languages, one queue.
Knowledge-base localization
A hundred help articles into a new market without onboarding a translation vendor or building a spreadsheet.
Quarterly content sync
Newsletter back-issues, blog archive, gated reports — kept in sync across markets on a monthly cadence.
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
- Batch translation means translating many files in a single run instead of one document at a time. You upload the whole bundle, pick one or more target languages, and every file is translated together with the same glossary, style guide, and QA pass — so a fifty-file deliverable ships as one queue rather than fifty separate jobs.
- Yes — translating a whole batch at once is exactly what this is for. Upload multiple files (DOCX, PDF, Markdown, or HTML), or import a Notion or Google Drive folder, choose your target languages, and batch-translate every file in one run with shared context across the set.
- Words are billed at words × target languages × mode multiplier. Fast and Standard are 1× source words per language; Pro is 3×. The estimate is shown before you run.
- Yes — pause the queue at any point. Completed files stay completed. Resume when you’re ready.
- The rest of the batch keeps going. Failed files surface in the dashboard with the error reason; rerun just that file when the issue is fixed.
- No hard limit. Free plan covers small batches; paid plans cover real production workloads. Top-up packs handle anything outside your monthly allowance.
- No hard cap. Practical limits are word budget and queue throughput. Most teams batch 20–100 files per run; a few customers run thousand-file batches monthly.
- New files queue up behind the running batch and use the same shared glossary and styleguide. The dashboard shows pending vs running vs completed so you can keep adding without losing visibility.
- Yes — pick all your target languages upfront and the batch runs the full matrix (files × languages) in parallel. Smart Proofread also runs per-language at the end.
- Words = source words × number of target languages × mode multiplier. The pre-run estimate shows the word cost before you commit. Top-up packs let you handle bursts that exceed your monthly plan without changing tier.
- Yes — the batch view shows files by status (queued, translating, proofreading, ready), per-language progress bars, and an estimated time-to-completion. Notifications fire when the batch finishes.
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…
- FeatureA glossary the AI actually follows→Character names, product terms, branded phrases, client-specific vocabulary. Build a glossary once — manually, by upload, or seeded from a…
- Use caseLocalize the launch kit, all of it→Email, landing page, FAQ, release notes, social posts — the assets that make a launch. Run them through Transept as one bundle with a…
- 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,…