Localizing Your Roblox Experience: Where to Start
Contents
Experience localization in Roblox is a set of settings covered on a dedicated page of the official Creator Hub docs: source language, a list of supported languages, and a clear line between automatic and manual translation of in-experience text.
This article is for people building a game (in Roblox’s own terms, an “experience”) in Roblox Studio — not for a player who just wants to switch the Roblox app’s interface language on their device. Those are two different settings in two different places, and it’s worth not mixing them up.
Where the documentation covers localization
Roblox’s official docs keep a dedicated page for localization — Localization, at create.roblox.com/docs/production/localization. It’s split into several sections:
| Section | What it’s about (by name) |
|---|---|
| User-facing setting | The setting the player themselves sees |
| Localization settings | General localization parameters for the experience |
| Set source language | The source language translations are made from |
| Set supported languages | The list of languages the experience is translated into |
| Automatic translations | Automatic translation of text |
| Manual translations | Manual translation of text |
| Work with translators | Working with human translators |
Right next to it is a companion page — Automatic translation, at create.roblox.com/docs/production/localization/automatic-translations. Both pages live in the same Creator Hub, which Roblox indexes with a machine-readable llms.txt file for tools that read documentation automatically, not just for people.
Source language: where it all starts
The Set source language section of the official docs covers the starting point of localization — the language a creator originally writes their in-experience text in. The exact steps for setting this language in Studio are covered on the official page itself — this article deliberately doesn’t paraphrase them, to avoid getting a detail wrong.
The list of supported languages
A separate section, Set supported languages, covers which languages the experience is actually translated into. This is a list the creator decides on themselves: localization doesn’t switch on for “every language at once” — it requires a deliberate choice of which languages to support. The full list of available languages is documented in its own Supported languages subsection on the automatic translation page — open it directly rather than looking for a number in the article text.
Automatic vs. manual translation — two different paths
The official documentation clearly separates two approaches to translating text inside an experience:
| Approach | Documentation section |
|---|---|
| Automatic | Automatic translations |
| Manual | Manual translations |
The companion Automatic translation page goes deeper into the automatic approach — it has its own sections: How automatic translation works, Enable automatic text capture, Text capture in Studio, Automatic cleanup, Automatic translation quotas, Automatic translation updates, Supported languages. In other words, before you turn on automatic translation, the docs separately explain the mechanics of capturing text in Studio and how outdated or unnecessary translations get removed (Automatic cleanup).
Manual translation is the neighboring Manual translations section on the main Localization page, and Work with translators covers working with people who translate by hand. The documentation treats these as two distinct sections, not one generic “translation” process.
Automatic translation quotas — not here, at the official source
The documentation has a dedicated Automatic translation quotas subsection. This article deliberately doesn’t repeat any numbers about automatic translation limits: they can change, and a repeated number here would eventually be wrong. For exact quotas, open create.roblox.com/docs/production/localization/automatic-translations and check the Automatic translation quotas section directly.
The same goes for Automatic translation updates, about refreshing already-made translations — check the mechanics at the source, not in a summary.
Before you take on localization
If you’re only just getting started with Roblox Studio, learn the basic steps of building a game first — see First Steps in Roblox Studio. Localization is a setting for an experience that already exists, not a first step for a beginner.
What is not officially stated
- The exact automatic translation quota numbers — the official page states them, but this article deliberately doesn’t repeat figures that could go out of date.
- The full list of supported languages — the documentation keeps it in a separate Supported languages subsection rather than in text that could be quoted safely.
- A step-by-step walkthrough of exactly where these settings live in the Studio interface — the sources establish the section structure, not click-by-click instructions.
- The cost or access conditions for automatic translation — none of the given sources mention this.
In short
Roblox describes experience localization in its official docs as a dedicated page covering source language, the list of supported languages, automatic and manual translation, and working with translators. For exact quotas and the language list, go straight to the official page — this article deliberately doesn’t include a single number that isn’t in the source.
Frequently asked questions
What does Roblox's official documentation call experience localization?
A dedicated page in the Creator Hub that covers the source language, the list of supported languages, and two approaches to translating in-experience text — automatic and manual. It lives at create.roblox.com/docs/production/localization and is split into seven sections, from User-facing setting to Work with translators.
How is experience localization different from account language settings?
Experience localization is a creator setting for a specific game built in Roblox Studio, not the app interface language a player switches for themselves. This article is written for creators, not for players looking to change their client's language.
Where is automatic translation documented officially?
On a separate page, Automatic translation, at create.roblox.com/docs/production/localization/automatic-translations. It goes deeper into automatic translation than the main Localization page and has its own sections, including text capture in Studio and quotas.
Where can I find the exact automatic translation quotas?
In the Automatic translation quotas subsection of the official automatic translation page. Specific numbers are deliberately not repeated here, because the official source can change them and this article won't.
Does the documentation cover working with human translators?
Yes. The main Localization page has a dedicated Work with translators section, covering collaboration with human translators separately from automatic translation.