Batch translation without the spreadsheet

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.

1. I.

   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.

2. II.

   Pick the targets

   One language pair, or a matrix — English to German, French, Spanish, Italian, Dutch, Polish, all at once. Standard, Pro, or Publish-Ready mode applies to the whole batch.

3. III.

   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.

4. IV.

   QA the whole batch in one pass

   Smart Proofread runs across the batch and surfaces issues by file. Resolve, regenerate, ship.

When batch changes the math

Questions, answered without the fluff

• How are words billed across a batch?+
  Words are billed at words × target languages × mode multiplier. Standard is 1× source words per language; Pro is 3×; Publish-Ready is 5×. The estimate is shown before you run.
• Can I stop mid-batch?+
  Yes — pause the queue at any point. Completed files stay completed. Resume when you’re ready.
• What happens if one file fails?+
  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.
• Is there a file count limit?+
  No hard limit. Free plan covers small batches; paid plans cover real production workloads. Top-up packs handle anything outside your monthly allowance.
• How many files can I batch at once?+
  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.
• What happens if I add a file mid-batch?+
  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.
• Can I batch translate across multiple language pairs at once?+
  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.
• How does pricing work for a large batch?+
  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.
• Can my team monitor batch progress from a dashboard?+
  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,…