Localization

Upload localizations of text-based content

Are you a Closed Beta partner? If you are not participating in the Closed Beta release, you can access documentation by using your Epic Games account to sign in to the Knowledge Base.

The Localization page allows you to view and manage your localized content. Localizations are made at the Offer level, and the dashboard displays all offer entities with localized content. You can also view which languages were uploaded and the date when they were updated.

  • Please do not edit or remove the first row (header) of the template sheet, and do not change the template structure, as this will break the import.

  • If your content requires changes in Stage-Review, localized content will also have to be updated.

  • Character limits are applied consistently across all languages. To ensure that all localized content strings can be imported without issue, we recommend keeping English (en) text at no more than 70–80% of the maximum number of field characters.

Upload Localizations

Known Issue: At this time, you will need to remove columns for any languages you have not translated.

  1. Go to Product > Localization > Dev > DOWNLOAD TEMPLATE.

  2. Select entities to localize > DOWNLOAD. The downloaded .CSV file will include all user-facing content strings within the product entities selected. If you have not created any localizations, the downloaded .CSV file will not contain data within the locale columns.

    1. Note: If you have an entity that has fully supported localization, but have other entities that are not, we suggest downloading/uploading those templates separately. For example, if your Product Home is to be fully localized but not Store Configuration, it is better to download those templates separately. Example steps:

    2. Download Product Home Page template and provide localizations for all columns. Upload Product Home Page template.

    3. Download Store Configuration Template and provide the localizations in the columns for the locales you support. Remove the rows that you are not localizing. Upload the template.

  3. Provide translated content within the appropriate locale columns and cells. Editable locale columns include: en,ar,de,es,es_ES,fr,it,ja,ko,pl,pt_BR,ru,th,tr,zh_CN,zh_TW. Remove columns for any languages you have not translated.

  4. Save your template file as .CSV . Note: Saving as a .CSV UTF8 is recommended.

  5. Return to the Localization page for your product > UPLOAD FILE. The max file size is 5MB.

  6. Select the .CSV template file to upload. If the upload was successful, the uploaded file displays with a success message.

    1. The dashboard will display any issues with the files; for example, the translated content may have exceeded the character limit of that field, or cells for required fields may be empty. You can click on each language icon to view issues or download a .JSON file with a compiled list of errors.

  7. Click SAVE. The dashboard displays the uploaded languages for each entity.

Manage Localizations

You can view and edit details about each localized entity.

  1. Go to Product > Localization > Entity name.

  2. On the Manage Localization, you can individually select which language you want to view.

    1. You can remove a language from an entity or add a language, only if it was included with your uploaded .CSV template file.

Preview Localizations

You can display a Page Preview of the localized entity to see how your localized content displays for each language.

  1. Go to Product > Localization > Entity name > select language > TEXT > PREVIEW ON STORE.

  2. Once on preview, you can click on the globe icon to preview other languages.

Publish Localizations

When you are satisfied with the localized content, you can push the localized offers to Stage.

  1. Go to Product > Epic Games Store > Dev > PUSH TO STAGE.

  2. Select Offers with localized content > PUSH TO STAGE.

  3. When the Offers display in Stage, you can SUBMIT FOR REVIEW.

  4. When all entities have been approved, you can PUBLISH to the Live sandbox.