+1 571 357 3985 info@alconost.com

Alconost Inc.
901 N. Pitt Street
Suite 170
Alexandria VA 22314


How to Prepare a Game for Localization? 10 Basic Rules

Shortly after the long-awaited local release is in the bag, most game developers start thinking about how to attract more international gamers. And sooner or later, after taking a crack at promoting their game in more countries, they come up with several ideas for localization.

This is why we have prepared this list of rules for developers to follow from the very beginning of the design process in order to make localization as painless as possible.

1. Pre-select localization languages in advance

So what is the best way to predict promising locales before you start?

  • Analyze the competitors’ localizations. Usually, if a rival game has found fertile ground in a certain market, you also have a great chance for a success story.
  • Evaluate localizations by genre. For example, if you’re an indie developer contemplating the release of a retro-style roguelike, you might have a good idea of your potential locales by looking at a success story in the genre.
  • Study the most wanted languages for game localization.

However, your localization plans notwithstanding, our “Rule #0” is to make English the source language if at all possible. And we recommend developing with two locales in mind from day one.

The two “default” locales should probably be English and your native language (if that isn’t English). This approach has several undeniable benefits: first, you’ll be able to translate your game later on into new languages using English as the source material, which helps ensure consistency. Second, having two languages from day one will automatically guide you through all the pitfalls of preparing for localization. Then you’ll see little difference when you have 20 languages.

2. Adjust the interface for potential languages

When building interface elements, it’s generally a good idea to plan for at least 30% extra space (or even more, if possible) for other languages. This is especially valid for short strings (menu items, UI, etc.).

However, if you’ve taken Rule #1 into account and have a preliminary long list of locales, there’s another helpful option: design your interface for the worst-case language.

For example, the German version is going to be an average of 30% longer than the English one, and the Russian version will be approximately 10% longer. The same is usually true for the Arabic version. On the other hand, traditional Chinese characters generally take up 30% less space than English texts.

When it comes to bytes, one Latin letter equals one byte, but Cyrillic and Arabic characters are twice as big, which also needs to be accounted for when planning data storage.

3. Don’t build text strings into the code

Transforming the text for localization will result in these hard-coded strings being lost. Every localizable string should be editable without touching a line of code. Another important tip is to avoid building pieces of text out of smaller single words.

Actually, all the engineering tasks that need to be performed in order to begin the localization process are attributed to the internationalization process or i18n for short.

4. Time, dates, units of measurement, and numbers also need to be localized

Numerical information also needs to be extractable from the code for localization and therefore must not be hard-coded.

You also need to be ready to redesign your numbers in the interface. For example, a clock ticking down the game’s timeline should probably be localized. The underlying motivation for this is that Western countries are mostly monochronic, which means they’re used to having time represented as a stretching timeline, whereas Asian countries prefer to have time represented as a circle.

Not to mention that the formats for dates and units of measurement differ across almost all languages.

5. Use placeholders and formatters and make them accessible

Using placeholders sometimes seems like a good alternative to just hard-coding text when it comes to localization and text editing. However, it can be a double-edged sword if you don’t provide access to placeholders.

This issue is connected to word and phrase order that might be absolutely different in another language. So our recommendation here is: make your placeholders part of the phrase so they can be inserted in context. Here’s a little example of what’s “good” and what’s “bad”:

No: "Mommy ate " + %num + " apples."
Yes: "Mommy ate %num apples."

A short description of placeholders can also be very helpful. This makes it possible to avoid confusion when a placeholder is considered to be wrongly related or unrelated to the previous piece of text.

6. Avoid text in images

If you use images in your game, be ready to localize them too, especially if they’re enriched with text. This means redesigning the whole image from scratch.

Redesigning images and creative assets is sometimes a good idea so you can meet standards for colors and characters in your target locale. However, it’s a waste of time and effort if you’re just doing it to insert translated text.

7. Try to use the right encoding and fonts

Encoding issues are inevitable if you need certain “spécîål” characters that don’t fit into your string class. If your target language has an encoding mismatch after localization, it could take a great deal of time and effort to remove those awful ��� characters.

The same problem applies to fonts. In particular, certain fancy fonts for games don’t contain glyphs for all languages. As a result, it might be necessary to choose different fonts for different languages. We recommend keeping this in mind when choosing a font; otherwise, you risk ending up with a bunch of boxes (□□□) instead of subtitled text.

Our recommendation is to use Unicode over ASCII whenever possible. UTF-8 is the most common and space-efficient encoding. So make sure your input files are encoded correctly.

8. Play with pseudo-translation if you’re ready for localization

Finally, once you’ve got all the technical aspects outlined above ready, try doing a test run. There are a number of great pseudo-localization tools available across the Web that can imitate your interface as if it were in a foreign language, including adapting text length and checking encoding and hard-coded strings.

These tools basically run a script that mimics the target language and produces a build, which then must be QA tested within the regular process as a non-localized build.

9. Start building your glossary early

A glossary is a collection of in-game terms and concepts that must be preserved consistently throughout the entire game. It mostly contains items, character names, artifacts, and statuses.

Maintaining consistency with the glossary across the entire game is essential. Just imagine if a certain in-game item is translated as “potion” in one place and “elixir” in another — you’ve unintentionally created an extra logic puzzle for your players.

10. Be ready to provide context

No less important than providing a glossary is ensuring that the localization team has all the context they need. In our experience, context can be established by enabling communication between translators, localization project managers, and game developers.

We hope you find this simple list of recommendations helpful for designing your games. We’re wishing you great success stories and captivated players!

Need help with translation or localization?



品質を損なわずにナレーション原稿の準備資金を節約するための4つのアドバイスxml動画を見る 詳細
ゲーム「Charm Farm」のローカライズ
  • 開発元/発行元: Nevosoft
  • 言語: PT-BR, NL, FR, DE, JA, PL, ES
  • 分量: 100,000ワード
  • サービス: ローカライズ
動画を見る 詳細
PPC広告を利用したMobiDB Database Designerアプリのプロモーション
  • お客様: Enterra
  • 言語: EN, RU
  • サービス: PPC
動画を見る 詳細
  • お客様: Petcube
  • 言語: KO, FR, HE, RO, Pt, NL
  • サービス: ローカライズ
動画を見る 詳細
Clash of Kingsのゲーム内テキストの校正
  • 開発元/発行元: Elex Tech
  • 言語: 英語
  • 分量: 25,000ワード
  • サービス: 校正、編集
動画を見る 詳細
Punch Clubのローカライズ
  • 開発元/発行元: Tiny Build
  • 言語: ZH-CN, PL
  • 分量: 20,000ワード
  • サービス: ローカライズ
動画を見る 詳細
  • お客様: Jooble
  • 言語: ES, PT, KO, JAその他11言語
  • 分量: 10,000ワード
  • サービス: ローカライズ
動画を見る 詳細
音声と動画のローカライズ、吹き替え、字幕:海外の視聴者にわかりやすい動画を作るにはxml動画を見る 詳細
  • お客様: Xsolla
  • 言語: FR, ES, JA, KOその他14言語
  • サービス: ローカライズ
動画を見る 詳細
  • お客様: Bitrix24
  • 言語: PT-BR, EN, DE, RU, ES, UKR
  • サービス: ナレーション録音、サウンド編集
動画を見る 詳細
  • お客様: Trade Voyage
  • 言語: EN, RU
  • サービス: PPC
動画を見る 詳細
Kaspersky Labの予告動画7本を2カ月で制作できた背景
  • お客様: Kaspersky Lab
  • 言語: EN, RU
  • 分量: 予告動画7本
  • サービス: 原稿作成、アニメーション、サウンドデザイン
動画を見る 詳細
  • お客様: DreamCommerce
  • 言語: NL, TR
  • サービス: ローカライズ
動画を見る 詳細
  • お客様: Bandsintown
  • 言語: FR, DE, IT, JA, PT, PT-BR, ES
  • 分量: 27,000ワード
  • サービス: ローカライズ
動画を見る 詳細
Dr. Bormental診療所のGoogleアナリティクス設定
  • お客様: Doctor Bormental
  • 言語: EN, RU
  • サービス: Webアナリティクス
動画を見る 詳細
KooRaRoo MediaのPPC広告
  • お客様: KooRaRoo Media
  • 言語: EN, RU
  • サービス: PPC
動画を見る 詳細
App Storeにおける予告動画の審査内容xml動画を見る 詳細
Monster Hustleのミニシリーズ動画
  • お客様: True Pilots U.N. Limited
  • 言語: EN, RU
  • 分量: 動画2本
  • サービス: 2Dアニメーション
動画を見る 詳細
Kaspersky Lab向けチュートリアル動画
  • お客様: Kaspersky Lab
  • 言語: EN, RU
  • 分量: 動画62本
  • サービス: 原稿作成、アニメーション、サウンドデザイン
動画を見る 詳細
動画クリップのナレーション原稿を書くための7つのアドバイスxml動画を見る 詳細
  • 開発元/発行元: Viber
  • 言語: RU
  • サービス: 製品ローカライズ、マーケティング翻訳
動画を見る 詳細
Smarty CRMプラットフォームのローカライズ
  • お客様: Clouds Technologies
  • 言語: ES, PT-BR
  • 分量: 9,000ワード
  • サービス: ローカライズ
動画を見る 詳細
Avatarico & Lostroomのクエストのナレーション
  • お客様: Avatarico
  • 言語: EN, ES, CAT, DE
  • 分量: 2,000ワード
  • サービス: ナレーション録音、音声処理
動画を見る 詳細
  • お客様: Clue
  • 言語: AR, FR, DA, DE, ES, HI, IT, JA, KO, PL, PT-BR, RU, TR, ZH-CN, ZH-TW
  • 分量: 70,000ワード
  • サービス: 継続的ローカライズ
動画を見る 詳細
Kerish Doctorソフトウェアのナレーション
  • お客様: Kerish Products
  • 言語: EN, HU, NL, ES, IT, DE, DAその他7言語
  • サービス: ナレーション録音
動画を見る 詳細
Guild of Heroesの広告キャンペーン用動画バナー
  • 開発元/発行元: BIT.GAMES
  • 言語: EN
  • 分量: 動画バナー18点
  • サービス: ゲームプレイ映像集、アニメーション
動画を見る 詳細
Life is Feudal: Your Ownのキャラクター音声
  • 開発元/発行元: BitBox
  • 言語: ES, PT-BR
  • サービス: キャラクター音声
動画を見る 詳細
Klondike: The Lost Expeditionのローカライズ
  • 開発元/発行元: Vizor Interactive
  • 言語: FR, ES, ZH-CN, JAその他7言語
  • サービス: 継続的ローカライズ
動画を見る 詳細
  • お客様: Alvadi
  • 言語: EN, RU
  • サービス: PPC
動画を見る 詳細
  • お客様: Teamlead
  • 言語: EN
  • 分量: 予告動画3本
  • サービス: 原稿作成、アニメーション、サウンドデザイン
動画を見る 詳細
  • お客様: Jetradar
  • 言語: FR, ES, DE
  • 分量: 100,000ワード
  • サービス: ローカライズ、LQA
動画を見る 詳細






読み込み処理中 — GIFアイコンお待ちください…