Looking for technical support for your game localization project?
Rest easy! We've got you covered!

Professionalism is an extremely important quality in this industry and it's something we at Altagram value highly.

With video games being our specialty, we understand that optimized content management is complex and demands experience. We can work with any text format and from any source, thanks to our highly trained project managers, coordinators, and in-house localization engineers who can adapt to any of your requests.

Upon receiving your files, we integrate them into memoQ and proceed with the localization process. Once they are complete and ready for delivery, we take care to ensure that they are returned to you completed in the format of your choice. If your preferred format isn’t on the following list, please don’t hesitate to contact us. We'll no doubt be able to work out your request regardless of the format.


Excel (.xlsx, .xls)

The most common file format for exchanging localization content. Easy to read and organize, supports most languages, and allows you to give each line that is to be translated an ID for context. Linguists can therefore translate content with maximum creativity and accuracy.

Text-based tables (.tsv, .csv)

Tables that offer the same benefits as an Excel file. Be careful to check the encoding of the text when submitting.

.doc, .pdf, .txt or any other 'plain text' format

Rarely used for in-game text, but common standards for marketing content. Naturally, free equivalents like .odt or .ods files are also accepted.

HTML / PHP Files (.html, .htm, .php)

When translating text, staying aware of the underlying source file structure is very important. This ensures the linguists have all the information needed to produce a contemporary-sounding and catchy localization. Our tools support these formats.

GNU Gettext Files (.po)

Another common format for organizing localization data. It contains a slightly different structure from the classic string file.

.xliff (.mgxlf, ...)

Less common than other formats, but often used in localization-specific tools.

String files (.string, .stringdict, .iua etc.)

More and more games, especially on the mobile market, are organizing their strings in this format. Our tools support them easily and without conversion.


Other formats

.yml, .yaml (YAML), .ini (configuration file), .js (RequireJS/i18n), .json (i18next multilingual), .json (i18next single language), .plist (Apple Property List en XML), .l10n (Java l10n), .lang (Java lang), .properties (Java Properties), .md (markdown), .tmx (Translation Memory eXchange), .qph (Qt Phrase Book), .locale (Play Framework Properties), .indd (InDesign), Mozilla RDF.

Related Case Studies

Explore other solutions

Quality Assurance

Altagram understands the need for quality and we want your game to be a bona fide classic. We have a native, dedicated, and experienced team of in-house testers across more than 25 languages to ensure your game is ready for any market of your choosing.

3500+ audio and voice-over productions.

Give a 360° Experience ->

Audio Production & Voice-Over Recording

Altagram has 3500+ audio and voice-over productions in experience and offers every audio localization service your game might need in over 50 languages.

Explore the Global Soundscape ->