Subtitles in games serve both localization and accessibility functions — enabling players who speak different languages and players with hearing differences to access the game’s spoken content. Game subtitle localization is distinct from text translation: subtitles must be timed to match spoken audio, formatted to remain readable on screen, truncated appropriately when translations run longer than the original, and implemented with accessibility features like text size scaling. This guide covers the requirements, workflow, and technical implementation of subtitle localization for games.

Subtitles vs. Captions vs. Intertitles

Games use several types of on-screen text that are often called ‘subtitles’: (1) Subtitles — translations of dialogue spoken in one language for players who speak a different language. Subtitles appear and disappear timed to the spoken dialogue. (2) Closed captions (CC) — transcriptions of all audio including dialogue, sound descriptions (‘[explosion]’, ‘[footsteps]’), and music cues for players who are deaf or hard of hearing. Captions are an accessibility feature distinct from localization subtitles. (3) Intertitles / text overlays — in-engine text that appears on screen to deliver narrative information without voicing. These are translated as standard game text strings. A complete subtitle localization strategy covers all three types, especially for games targeting markets with accessibility requirements (CVAA compliance in the US, European Accessibility Act compliance in the EU).

Subtitle Timing and Text Fitting

The core technical challenge in subtitle localization is fitting translated text within time constraints set by the original audio. The original subtitle timing is set to the source language audio — a German sentence spoken in 3 seconds is replaced by a French sentence that must also display for approximately 3 seconds, even if the French translation is longer. Solutions for text fitting: (1) Translation adjustment — subtitle translations should be slightly condensed compared to full text translation; the adaptor removes redundant words that would cause overflow while preserving meaning. (2) Reading speed limits — subtitles should not exceed 17–20 characters per second (the standard readable pace for adults); translations that are inherently longer than this at original timing must be condensed. (3) Split subtitles — very long translations can split across two subtitle display segments if the original timing allows. (4) Subtitle regions — multi-line subtitle display (typically 2 lines) gives translators more space; standard game subtitle display is 1–2 lines. Text fitting is why subtitle localization requires more time and skill than pure translation — it’s an adaptation exercise within rigid time constraints.

Subtitle File Formats for Games

Subtitle files for games differ from video subtitle files: (1) SRT (SubRip) — the most common plain-text subtitle format, widely used in games with external subtitle file support. SRT files contain sequential subtitle blocks with timing and text. (2) VTT (WebVTT) — web standard subtitle format, increasingly used in web-based games and engines with WebGL/HTML5 rendering. Supports additional styling information. (3) Engine-native formats — Unity, Unreal, and custom engines often use proprietary subtitle systems: Unity commonly uses timed AudioClip-synchronized dialogue scripts; Unreal uses Dialogue Wave assets with subtitle fields. (4) SSA/ASS — advanced subtitle format with styling support, used in some games particularly for anime-styled Japanese games. (5) XML/JSON dialogue files — many games implement custom subtitle systems using the game’s dialogue data format (timed entries in the same format as other game strings). The subtitle format is defined by the game engine; the localization team adapts translations to the required format after translation.

Subtitle Accessibility Requirements

Accessible subtitles are increasingly required by law in some markets and expected as standard practice. Key accessibility considerations: (1) Text size — subtitles must be readable at typical playing distances. Minimum recommended font size is 36pt for TV/console games; accessibility options for increased font size should be included. (2) Background contrast — white text on transparent background is often unreadable against bright game scenes; a dark semi-transparent background box or text shadow is required for accessibility. (3) Font choice — readable sans-serif fonts are standard for subtitles; decorative or script fonts are not appropriate for subtitle display. (4) Speaker identification — in dialogue-heavy games, speaker labels or name tags help players track who is speaking. Color-coding speakers is a common approach. (5) Caption descriptions — for CC compliance, non-dialogue audio cues (‘[music: tense]’, ‘[sound: door opening]’) should be included for deaf/hard-of-hearing players. (6) Subtitle persistence — subtitles should remain on screen long enough to be read comfortably; auto-advancing subtitles that disappear too quickly fail accessibility standards.

Frequently Asked Questions