Summer 2026 product update: smoother review and more reliable delivery

Since late June, we have focused on the parts of real production that teams encounter every day: efficient review, reliable Word export, predictable batch handling, and support for larger projects.

This post is a plain-language summary of the most useful updates shipped between late June and mid-August 2026.

1. Reviewing and editing are much easier

The workbench is now more comfortable for day-to-day editing:

• You can use Find / Replace directly in the toolbar
• Job reviewers can also use it on the language they were invited to review
• You can double-click a translation cell to edit it faster
• Common actions are laid out more clearly, so PMs and reviewers spend less time hunting for buttons

In practice, this means less copy-pasting to spreadsheets and fewer small review tasks escaping the platform.

2. Repeated text stays more consistent

Many projects repeat the same sentence again and again: headings, labels, warnings, contract phrases, and UI strings.

Now, when you save or approve a segment, BabelBee can carry that translation forward to later matching segments. The setting is on by default.

This helps teams:

• keep repeated wording consistent
• reduce the number of manual fixes
• focus review time on the places that are actually different

If a later segment has already been edited by hand or locked, BabelBee leaves it alone.

3. Style instructions can be saved and reused

Teams often translate series of similar files for the same client. Before, PMs had to rewrite or paste the same style notes again and again.

Now workspaces can save style instructions once and reuse them on future uploads. That makes it easier to keep tone, wording, and client preferences steady across a whole series of files.

4. Word exports are more reliable

This was one of the most important areas of work.

We improved how BabelBee handles DOCX files so exports are less likely to come back with broken structure or awkward formatting. The updates cover common trouble spots such as:

• text boxes
• nested tables
• multi-line table cells
• footnote markers and special formatting
• font mapping for the target language
• spacing issues that can appear after translation

The short version: if you translate Word files often, exports should feel much more dependable than they did earlier in the summer.

If your team works with CAT-generated bilingual Word files, XLIFF 1.2 is still the safer interchange path.

5. Batch projects are steadier

We also improved multi-file projects so they behave more like one coordinated job and less like a bundle of separate uploads.

Key improvements:

• zip uploads work again for Business batch jobs
• segment mix-ups between files were fixed
• bilingual export now covers all files in the batch
• review status is handled more safely before export

This matters most for teams running one project across many files and languages, where small inconsistencies can waste a lot of PM time.

6. Larger jobs are easier to finish

Some teams were hitting export limits on large projects. We raised the export ceiling from a few thousand segments to 50,000 segments.

We also improved the project list for larger workspaces by adding pagination and full-workspace search. That makes it easier to open old jobs and find what you need without loading everything at once.

7. Language options are clearer

We expanded the available language list and cleaned up some locale handling so teams can choose target languages more accurately.

One example: Filipino and Tagalog are now listed separately instead of being treated like the same option.

Why these updates matter

None of these changes are flashy on their own. But together they reduce the small points of friction that slow down real production:

• less repetitive editing
• fewer formatting surprises
• smoother batch handling
• better support for large projects

That is the kind of improvement teams feel week after week.

Suggested things to try

1. Open a finished job and test Find / Replace in the workbench.
2. Turn on Sync repetitions and check how repeated text updates.
3. Re-export a Word file that previously had layout issues.
4. Run a multi-file batch and confirm every file appears in bilingual export.

Start a free workspace · Compare plans · Learn about XLIFF