Batch or Real-Time Translation: Choosing

Quick answer — Use real-time translation where content is user-generated or changes constantly, and batch where content is reviewed before publishing. Most organisations need both, decided per content type rather than as a single policy.

Vitra.ai Universe creates, translates, adapts and publishes from one place.

Two different questions

Real-time means translated on request, at the moment somebody needs it. Batch means translated ahead of time and stored. The choice is usually framed as speed versus cost. It is really about whether the content can be reviewed before it is seen.

What suits each

The bottom row is the hybrid most sites end up with: translate the high-traffic articles properly and serve a real-time translation for the long tail, marked as machine translated.

Why batch wins for anything indexable

A real-time translation is generated per request and generally not indexed, so the page does not exist for search in that language.

If discovery matters — and for marketing and product content it is usually the whole point — the translated version needs to be a real page with its own URL, which means batch. That is the argument set out in multilingual sitemaps.

Real-time also cannot be reviewed before it is seen, which rules it out for anything with legal consequence.

Why real-time wins for content you did not write

User-generated content arrives continuously, in unpredictable languages, in volumes nobody can pre-translate. A review with four upvotes does not justify a batch job, but a reader still wants it.

The same applies to a catalogue with a long tail — pre-translating a million listings to serve a hundred is waste.

The practical arrangement

Batch what you publish, real-time what your users produce, and cache the real-time results so a second request is free. Route each mode through the same quality control so the standard does not depend on which path served the text.

Memory underneath both means the terminology matches whichever path served the text, so a product name is the same in your description and in a translated customer review — which is the part that gives away a bolted-on real-time layer.

FAQ

When should translation be real-time rather than batch? For content you did not write and cannot pre-translate: user reviews, comments, support chat and long-tail catalogue items. Volume and unpredictability make batching them wasteful.

Why is batch translation better for marketing pages? Because real-time output is generated per request and generally not indexed, so the page does not exist for search in that language. It also cannot be reviewed before a customer sees it.

Can both modes be used together? Yes, and most sites end up doing so. Translate high-traffic content in batch and serve real-time translation for the long tail, labelled as machine translated, with results cached.

What keeps terminology consistent across both modes? A shared memory underneath. Without it a product name reads one way in your own description and another in a translated customer review, which is what exposes a bolted-on real-time layer.