One upload, many files and languages: how Business batch projects work

Enterprise translation requests rarely arrive as one file in one language. A product launch might mean twelve help articles and four target locales. A compliance packet might be six PDFs that all need French and German.

LSP and enterprise language teams on BabelBee's Business plan can run multi-file batch upload and multi-target languages in a single project — submit once, track everything in one production workbench, and export per file or per language when you are ready.

What changed for teams

Before, each upload was effectively one source file → one target language. That is still the right default for solo users and small plans. Business teams needed a different shape:

Capability	What it means
Multi-file batch	Select up to 20 files in one upload (DOCX, PDF, XLSX, etc.)
Multi-target languages	Add several target languages before you submit
One project, many jobs	Each target language becomes its own translation job inside the project
Per-job workbench	Switch between languages without losing context
Per-document export	Download each source file's translation in the original format
Re-translate one language	Re-run AI on a single target without touching the others

Word counts and billing roll up at the project level, but progress is tracked per job so a slow French review does not block Spanish export.

A typical workflow

1. Prepare files — same source language, any mix of supported formats (contracts + spreadsheets + slides are fine).
2. Upload on Business — drag in multiple files; the upload page totals words across the batch.
3. Choose target languages — e.g. es, fr, de in addition to your primary target.
4. Set tier and preferences — style, glossary, and TM apply to the whole project.
5. Submit — extraction runs for every document; segmentation review shows combined stats.
6. Process — translation jobs run in parallel (one per target language).
7. Review in the workbench — use the job switcher to move between languages; each job has its own QA flags and human-review queue.
8. Export — pick the document and language you need; format-restore export works per file.

Why this is a project, not a folder of separate uploads

Treating batch work as one project matters for teams:

• Shared context — one terminology list, one style instruction, one TM attachment for the whole engagement.
• Single invoice line — Business billing sees the batch as one commitment instead of twenty stray projects.
• Coordinated review — project owners see all languages; reviewers can be assigned per job (see our job reviewer guide).
• Audit trail — one project code, one history — easier to answer "what happened to the March launch pack?"

Multi-file tips

Keep source language consistent. Batch upload assumes one source locale across the selection. Mixed-language folders should be split into separate projects.

Watch total word count. The upload page aggregates words for quota preview. Large batches can consume a significant share of monthly Business quota — plan accordingly or contact us for volume arrangements.

Use segmentation review once. After extract, scan for short fragments across the combined preview. Awkward splits in one file do not block processing for the rest.

Name files clearly. Per-document export uses original filenames. policy_v3.docx beats final_FINAL2.docx when six reviewers download deliverables the same afternoon.

Multi-language tips

Primary vs extra targets. You pick one primary target language plus optional additional targets. Each becomes a job with its own segments, scores, and export files.

Re-translate sparingly. If you change glossary or style after the first run, you can re-translate one language instead of restarting the entire project. Other completed jobs stay untouched.

Human review is per job. On Team Verified projects, flagged segments are resolved inside each language job. French approval does not auto-approve Japanese.

Who this is for

Business plan subscribers get batch upload and multi-target languages by default (up to 20 files per batch). Smaller plans remain single-file, single-target for simplicity.

Good fits:

• Localization managers running content drops (help center, release notes, policy updates)
• Legal or compliance teams translating document sets into multiple jurisdictions
• Agencies packaging client batches where one PM owns the whole engagement

Frequently asked questions

Is there a file limit?

Yes — 20 files per batch on Business, aligned with the server-side cap. Very large individual files still respect your plan's per-file upload size limit.

Can I add files after submit?

Not to the same batch today. Upload a follow-on project or contact sales@babelbee.ai for high-volume pipeline discussions.

Do all formats mix in one batch?

Any supported format can appear in the same project as long as extraction supports it. Remember that scanned PDFs may run OCR and take longer than native DOCX.

How does pricing work?

Business uses word-based monthly quota. Multi-file and multi-language projects count total source words × target languages according to your tier rules. Platform quota accounting is separate from any TM-match or repetition analysis needed for client quotes and translator payments.

---

On Business and ready to run a real batch? Start a free workspace · Compare plans