# XLOC > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-11-08. - **Brand record:** https://optimly.ai/brand/xloc - **Dataset:** https://optimly.ai/brand/xloc.json - **Markdown:** https://optimly.ai/brand/xloc/llms.txt - **Official website:** https://xloc.com - **Slug:** xloc - **Categories:** saas-cloud-software ## Overview - **Tagline:** Web-based localization management solutions for the international video games industry. Source: Brand's website (https://xloc.com) · 2026-11-08 - **Description:** XLOC provides a web-based Content Management System and localization management tools that manage text, audio and art assets throughout the multilingual game development process. Source: Brand's website (https://xloc.com) · 2026-11-08 ## Identity - **Mission:** Make video game localization easier, more controlled and more profitable by streamlining localization processes and integrating them into the development cycle. Source: Brand's website (https://xloc.com) · 2026-11-08 - **Website:** https://xloc.com Source: Brand's website (https://xloc.com) · 2026-11-08 - **Voice & tone:** Professional, practical, technology-focused and collaborative. Source: Brand's website (https://xloc.com) · 2026-11-08 - **Founded:** 2004 Source: Brand's website (https://xloc.com) · 2026-11-08 - **Headquarters:** Raleigh, North Carolina, United States Source: Brand's website (https://xloc.com) · 2026-11-08 - **Parent ownership:** Part of Keywords Studios; Keywords Studios acquired XLOC in 2017. Source: Brand's website (https://xloc.com) · 2026-11-08 ## Offerings - **Problem solved:** XLOC helps video game developers and publishers manage complex multilingual localization workflows, coordinate teams, control asset changes, integrate localization with development processes, and deliver titles across multiple languages and platforms. Source: Brand's website (https://xloc.com) · 2026-11-08 - **Core capabilities:** - Web-based localization management - Centralized management of text, audio and art assets - Multilingual asset tracking and status visibility - Localization workflow and production pipeline management - Translation management, history and fuzzy matching - Immediate testing and prototype builds - Build checks and linguistic quality assurance support - Game engine, development tool and API integrations Source: Brand's website (https://xloc.com) · 2026-11-08 - **Products / SKUs:** - XLOC Content Management System (CMS) - XLOC 7.25 - XLOC proprietary web-based localization applications and tools - XLOC consulting and support services Source: Brand's website (https://xloc.com) · 2026-11-08 - **Pricing:** Pricing is based on the number of strings and games. XLOC creates a one-year license that includes an AWS server and complimentary support hours; clients may also use their own server. Source: Brand's website (https://xloc.com) · 2026-11-08 ## Audience - **Target industry:** Video games and interactive entertainment. Source: Brand's website (https://xloc.com) · 2026-11-08 - **Customer base:** Video game developers, publishers, producers, localization managers, developers, QA and LQA teams, translators, and translation managers. The site names clients including Activision, Bandai Namco, Capcom, EA, Riot Games, Glu, Phoenix Labs, Milestone and others. Source: Brand's website (https://xloc.com) · 2026-11-08 - **Ideal customer profile:** Game development and publishing organizations, from major gaming companies to smaller start-ups, that need to manage multilingual localization for games across platforms, engines, formats or development environments. Source: Brand's website (https://xloc.com) · 2026-11-08 - **Use cases:** - Managing localization for mobile, AAA console and MMO PC games - Coordinating multilingual text, audio and art production - Tracking localization progress across languages and roles - Managing translation projects and translation history - Testing localized assets and generating prototype builds - Performing build checks and linguistic QA - Integrating localization with game engines and internal tools - Managing simultaneous releases across multiple platforms and languages Source: Brand's website (https://xloc.com) · 2026-11-08 - **Customer outcomes:** - Reduced localization production time and costs - Faster QA and localization testing - Improved coordination and visibility across teams - Fewer process breaks, mistakes and human errors - Faster time to market for globally released titles - Support for broader market reach and increased revenue potential - More standardized development and localization processes - Improved control of localization assets and changes Source: Brand's website (https://xloc.com) · 2026-11-08 Page last updated 2026-11-08. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.