# Game UI String Translation and Length Limits | Vitra.ai > Game UI is the least forgiving text in software: fixed art, no reflow, and languages that run a third longer. What to send translators and what to design for. **Canonical URL**: https://www.vitra.ai/gaming/game-ui-string-translation **Source**: This is the Markdown rendering of https://www.vitra.ai/gaming/game-ui-string-translation, generated at build time from that page. --- 4 min read # Game UI String Translation and Length Limits Game UI is the least forgiving text in software: fixed art, no reflow, and languages that run a third longer. What to send translators and what to design for. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Senior Product Manager , Vitra.ai Updated Aug 17, 2026 ![Game UI String Translation and Length Limits](https://www.vitra.ai/static/images/blog/game-ui-string-translation.jpg) Table of contents [The panel does not stretch](#the-panel-does-not-stretch) [Send the limit with the string](#send-the-limit-with-the-string) [Design for the longest language](#design-for-the-longest-language) [Reused strings are a false economy](#reused-strings-are-a-false-economy) [Check it on screen](#check-it-on-screen) [FAQ](#faq) Contributors [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Senior Product Manager Subscribe to our newsletter Subscribe > **Quick answer —** Game UI strings are constrained by art that does not reflow, so length limits have to travel with every string. German and Russian run longer than English, and a menu built to fit English breaks in both.[Vitra.ai Universe](https://www.vitra.ai/platform) keeps character voice and terminology intact across every language. ## The panel does not stretch Application UI reflows. Game UI is usually art — a carved menu plate, a HUD element, a button baked into a texture — with a text field of fixed size sitting on it. So a translation that runs long has three outcomes, and all of them are bad: truncation, a font scaled down until it is unreadable, or text spilling past the frame. ## Send the limit with the string Send Why Character or pixel limit The field will not grow Screenshot or screen name Verb versus noun, and register Whether the string repeats Consistency across screens Speaker or source HUD, menu, tutorial, system message Variables and what they hold See [protected terms](https://www.vitra.ai/general/do-not-translate-lists) A limit is a design constraint, so the translator writes to it rather than translating to it. A shorter word that fits beats an accurate one that truncates, and only the translator can make that trade if they know the budget. ## Design for the longest language The usual guidance is to leave thirty percent headroom for German, which is roughly right and not sufficient on its own — Russian runs long too, and compound-heavy languages produce single words that cannot be broken. Better where the art allows: text fields that can grow downward, two-line tolerance on buttons, and no critical label baked into a texture. Anything with words inside the artwork needs [image translation](https://www.vitra.ai/features/image-translation) rather than a string pass, and it is the most commonly missed part of a localized build. ## Reused strings are a false economy One `Confirm` shared across twelve screens looks efficient and guarantees at least one context where it is grammatically wrong. Separate keys per context cost nothing at build time and remove a whole class of LQA finding. The saving from reuse is a handful of translated words; the cost is a tester filing a bug, a translator explaining that the word is correct in eleven of twelve places, and somebody deciding which context loses. That trade is never worth taking. ## Check it on screen String length problems are invisible in a spreadsheet and obvious in the build. Run [pseudo-localization](https://www.vitra.ai/general/localized-website-testing) before translation — every string padded and accented — and the fixed-width fields surface while the fix is still a UI change rather than a re-translation. Then [quality control](https://www.vitra.ai/features/quality-control) on the extracted text, and a human on the running game. ## FAQ **Why is game UI harder than application UI?** Because it usually does not reflow. Menus, HUD elements and buttons are art with fixed text fields, so a long translation truncates, shrinks below legibility, or spills past the frame. **What should be sent with each UI string?** The character or pixel limit, a screenshot or screen name, whether the string is reused, its source, and what any variables hold. A limit lets the translator write to it rather than overflow. **How much headroom should game UI leave?** Around thirty percent for German is the usual starting point, but it is not enough alone. Russian also runs long and compound languages produce unbreakable single words. **Should the same UI string be reused across screens?** No. One shared label across many contexts guarantees at least one is grammatically wrong, and separate keys per context cost nothing while removing a common class of LQA finding. Our blog ## Lastest blog posts Tool and strategies modern teams need to help their companies grow. Automotive [Automotive Brochure Localization by Market](https://www.vitra.ai/automotive/automotive-brochure-localization) A car brochure is a spec grid, a legal footer and a photo library, all market-specific. What actually has to change, and why the layout decides the schedule. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 Automotive [Automotive Campaign Localization Across Markets](https://www.vitra.ai/automotive/automotive-campaign-localization) Campaigns run through national companies and dealer networks, so one master becomes hundreds of files. Where the offer text and the disclaimers actually break. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 Automotive [Car Service Manual Translation for Technicians](https://www.vitra.ai/automotive/automotive-service-manual-translation) A workshop manual is read mid-repair by someone with the car on a lift. What that demands of procedures, torque figures and fault codes, in every language. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 [View all posts](https://www.vitra.ai/blog/page/1) --- ## Structured data ```json { "@context": "https://schema.org", "@type": "Article", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://www.vitra.ai/gaming/game-ui-string-translation" }, "headline": "Game UI String Translation and Length Limits", "image": [ { "@type": "ImageObject", "url": "https://www.vitra.ai/static/images/blog/game-ui-string-translation.jpg" } ], "datePublished": "2026-08-17T00:00:00.000Z", "dateModified": "2026-08-17T00:00:00.000Z", "author": [ { "@type": "Person", "name": "Samhitha J Bhatt" } ], "publisher": { "@type": "Organization", "name": "Vitra.ai", "logo": { "@type": "ImageObject", "url": "https://www.vitra.ai/static/images/vitra-v-logo.png" } }, "description": "Game UI is the least forgiving text in software: fixed art, no reflow, and languages that run a third longer. What to send translators and what to design for." } ``` ```json { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.vitra.ai" }, { "@type": "ListItem", "position": 2, "name": "Gaming", "item": "https://www.vitra.ai/gaming" }, { "@type": "ListItem", "position": 3, "name": "Game UI String Translation and Length Limits", "item": "https://www.vitra.ai/gaming/game-ui-string-translation" } ] } ``` ```json { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Why is game UI harder than application UI?", "acceptedAnswer": { "@type": "Answer", "text": "Because it usually does not reflow. Menus, HUD elements and buttons are art with fixed text fields, so a long translation truncates, shrinks below legibility, or spills past the frame." } }, { "@type": "Question", "name": "What should be sent with each UI string?", "acceptedAnswer": { "@type": "Answer", "text": "The character or pixel limit, a screenshot or screen name, whether the string is reused, its source, and what any variables hold. A limit lets the translator write to it rather than overflow." } }, { "@type": "Question", "name": "How much headroom should game UI leave?", "acceptedAnswer": { "@type": "Answer", "text": "Around thirty percent for German is the usual starting point, but it is not enough alone. Russian also runs long and compound languages produce unbreakable single words." } }, { "@type": "Question", "name": "Should the same UI string be reused across screens?", "acceptedAnswer": { "@type": "Answer", "text": "No. One shared label across many contexts guarantees at least one is grammatically wrong, and separate keys per context cost nothing while removing a common class of LQA finding." } } ] } ```