Localizing Animated UI: Text, Length and Direction in Motion
How to localize animations and interactive UI: dynamic text instead of baked-in words, text expansion, fonts and scripts, number formats, and right-to-left motion.
Core Takeaway
To localize animated UI, keep text as live, replaceable text rather than outlines baked into the animation, design containers that grow with longer translations, load fonts that cover every script you support, format numbers and dates with locale-aware APIs, and mirror directional motion for right-to-left languages.
Never bake text into artwork
Text converted to shapes, or rendered into a video, has to be re-animated for every language. Keep labels as text layers your code can set at runtime, and treat them as inputs like any other value.
Plan for text expansion
Translations are often longer than English, especially for short labels. The W3C's internationalisation guidance on text size notes that short strings can expand dramatically in some languages.
- Let containers grow, or define how text truncates
- Test with long pseudo-translations before real ones arrive
- Avoid animations timed to the width of one specific word
- Check line breaks for languages without spaces
Fonts, scripts and numbers
Make sure your fonts cover every script you ship, or fall back gracefully. Some scripts need more line height. Format numbers, currencies and dates with locale-aware tools such as JavaScript's Intl APIs, especially in animated counters, where digits and separators vary by locale.
Direction
Motion that implies direction, such as sliding forward, progress filling or arrows, should mirror in right-to-left languages. Logos, clocks and media playback controls usually do not. See our separate guide on right-to-left animation.
Building this in ExodeUI
ExodeUI, which we make, keeps text as text runs in the open .exode file rather than outlines, so translated strings can be swapped in without redrawing the animation, and AI coding tools can do it through the MCP server. Test long strings in the editor before release.
Key Principles to Remember
- Keep text as live, replaceable layers
- Design for longer translations and test with pseudo-text
- Cover every script with fonts; format numbers per locale
- Mirror directional motion for right-to-left languages
Frequently Asked Questions
Sources
- Text size in translation — W3C Internationalization
- Intl — MDN Web Docs