Content Localization and Automatic Translations for Your Community

nat
Thu, 10 Jul 2025 02:56:57 +0000
Announcements

Content localization and automatic translations are now ready, bringing multilingual support to your communities. This feature is enabled here on Meta.

Our experiments here have drummed up quite a lot of buzz as we’ve been tinkering away, and we are very pleased to say that the anticipation is finally over and you can now have these great new features live on your sites too.

With these powerful new additions, you can now translate and serve your site’s content in multiple languages for a seamless multilingual experience. From topic titles to post content, and even categories and their descriptions, your community can now be fully translated into a variety of languages of your choosing.

For details on the feature and how to set it up, please visit the documentation topic: Content Localization - Manual and Automatic with Discourse AI

Hosted by us? This feature is available on all of our hosted plans

FAQ

Which LLM is meta (this forum) using?
We’ve been iterating and have settled with Gemini Flash 2.5 for now; we were just using 2.0 a few weeks ago. Language support and costs will keep evolving and we expect to be updating as-and-when we find better ones. This metric by OpenRouter is useful to determine what is typically used out there - LLM Rankings | OpenRouter.

But … how much does this all cost?
There are many variables to how much translating your community might cost: chosen model, post sizes, number of topics, number of categories. We recommend setting a daily acceptable quota and then vary it as you go. Discourse AI - AI usage and Configuring LLM Usage Quotas in Discourse AI are great topics on monitoring usage.

As a very rough gauge, translating 🇨🇳 Discourse supports Chinese usernames | Discourse 支持中文用户名 to 2 languages (English and Japanese) with the default persona uses 7800 tokens. If using Gemini 2.5 Flash Lite, it costs $0.001030

Upcoming Features and Improvements

Serving localized content to SEO

We want to help public communities get more organic traffic. If your site defines a set of locales that you support, every topic will also indicate links to its translated version for Search Engines like Google to index.

Done

Locale selectors that make sense to you

Currently sitewide, we have “日本語” for Japanese in the dropdown selector. We should use “Japanese” instead when viewing it in English.

Done

Localizing tags

As-is, tags are not as robust as categories and have some quirks. Tags will fundamentally need some changes prior to adding localization features. [1]

Done

Re-translate edited posts

Currently a translated post is not re-translated when the original is edited. We’re considering some good default thresholds, or exposing certain controls that allow privileged users to trigger automatic translation on the edited post.

Done

Community Translation Progress Dashboard

As a community owner, it is not easy to see how much of your forum has been localized.

Our intent is to show a dashboard that indicates translation progress per language you’ve set up.

Done

Oneboxes and links

They currently do not show up correctly on localized topics. This will be fixed.

Done

Have a question or suggestion?

If you’ve found an area which hasn’t been localized when it should, or would like to suggest improvements, we are happy to listen and will take your suggestions internally for further discussion.

Please add them to this topic and we will fork them out into new topics if it deserves its own space.

1. A quick comparison of a category Bug - Discourse Meta to a tag Topics tagged email gives us some hints that tags are not identified by their IDs but the names instead. ↩︎

30 сообщений - 9 участников