Subtitles are easiest to read when their contrast, position and timing work with the footage rather than fight it. Start with a plain, consistent treatment, then preview the exported video on the screens and platform your viewers will use.
There is no font, colour, size or placement that works for every video. The right choice depends on the image behind the text, the information viewers need to see, and whether the text is burned into the picture or displayed by a player.
Subtitles and captions do different jobs
In everyday use, “subtitles” often means text for spoken dialogue, particularly a translation into another language. Captions are intended to convey speech and relevant non-speech audio, such as a bell, a door closing or music that signals a change in mood. The terms vary by country and platform, so say what your file is meant to provide rather than relying only on its label.
This distinction matters when you prepare a devotional stream, a local news loop or a recorded lesson. A translation of a speaker’s words may help viewers follow the language; captions that also identify a meaningful sound can help viewers understand what is happening when they cannot hear the audio. For speech, consider identifying a speaker when it is not clear from the picture who is talking. Do not rely on colour alone to tell viewers who is speaking or what a sound means.
Captions can be open or closed. Open captions are part of the video image: every viewer sees them, and viewers cannot switch them off. Closed captions are delivered separately for a player to display, which can leave viewers in control of whether they appear and, in some players, how they look. The W3C WAI guide to captions and subtitles explains these distinctions and cautions that player support for styling is inconsistent.
Choose the form that fits the viewing situation. Burned-in dialogue translation may be useful when a short clip must look the same wherever it is shared. For a long programme, closed captions can give viewers more control, provided the destination player supports the file and the features you need. Neither choice is automatically better: consider viewer control, content obstruction, the information conveyed and portability together.
Begin with readability
Treat decoration as secondary. A decorative typeface may suit a title card but slow down reading when it appears over moving footage. A legible sans-serif face is a sensible starting point, not a universal rule; inspect the actual letters, punctuation and language you use. Some characters that look distinct in one script or font may become harder to separate at a small on-screen size.
Size must be judged in context. A preview that looks clear in an editing window can become cramped on a phone, where a viewer watches a small version of the frame. Section508.gov gives 18-point white text on a translucent black background as an example default. Treat that as a starting example, not a fixed pixel size or minimum for every player. The intended delivery size, video resolution and player scaling all affect what viewers see.
Keep each cue digestible. Section508.gov recommends no more than two lines and no more than 45 characters per line, with fewer characters ideal. This is practical guidance rather than a rule for every language: line length, word breaks and reading speed can differ. If a sentence feels crowded, split it at a natural phrase rather than shrinking the type until it is difficult to read.
Timing is part of readability. A cue should appear in step with the speech and remain long enough to read, without distracting scrolling or flashing. Check a complete sentence against the audio; word-perfect transcription is not useful if the text arrives late or disappears before a viewer can finish it. For a playlist that will repeat, watch the transition and first caption of the next segment as well as a typical middle section. The YouTube live playlist setup guide covers the wider task of preparing a playlist; caption timing still needs its own review.
WCAG 2.2 specifies contrast ratios of 4.5:1 for normal text and 3:1 for large text in its applicable text-contrast criterion, subject to the criterion’s exceptions. These are standards for applicable contrast contexts, not proof that a particular subtitle recipe conforms in every scene or implementation. Use contrast figures as a useful check, then inspect real footage and the finished player presentation. A colour sample against a flat test screen cannot reveal what happens when bright detail passes behind a cue.
Choose contrast and a background treatment
A subtitle must remain distinguishable from the image beneath it. White text can be clear over dark water and disappear against a pale sky; dark text can reverse that problem. Instead of trying to pick a colour that wins on every frame, choose a stable treatment that keeps the characters separate from changing footage.
A translucent or opaque backing behind text can provide that separation without requiring the entire picture to change. A subtle outline or shadow may help in some scenes, but it is not a substitute for checking contrast across the complete frame. If the background changes from a dark temple interior to bright outdoor footage, pause on both scenes and decide whether the same treatment remains legible.
The common white-on-dark-box appearance is familiar, but it is not a universal design prescription. A box may cover more of a narrow phone image; an outline may look uneven at small sizes; a translucent fill may allow detail to distract through the letters. Compare these options using the video itself, including its brightest, darkest and busiest moments. Make a choice that remains readable without drawing more attention than the content.
For open captions, style and placement are baked into the export, so a change means editing and exporting the video again. For closed captions, the player may render the text in its own default style or offer viewer settings. In either case, keep foreground and background distinct enough to read, and do not use a colour change as the sole signal for a new speaker, sound or category. Add a name or concise sound label when the information matters.
Place text without hiding the picture
Lower-centre placement is a useful first preview, not a rule. It often leaves the main action visible, but many videos put essential information there: a speaker’s name, a news ticker, a product label, a sign or subtitles already embedded in a source clip. Move a cue when it covers something the viewer needs to understand.
Review the frame for faces, gestures and text as well as the central subject. For a news loop, captions over a lower-third name banner can obscure both the words and the identity they explain. For a bhajan video, a lyric cue might cover a singer’s hands or an instrument that helps viewers follow the performance. WCAG 2.2 says captions should not obscure or obstruct relevant video information; the important question is what is relevant in the scene you are showing.
If the video changes composition, a single fixed position may not be suitable. Try moving the text to an open part of the frame, but avoid shifting it erratically from cue to cue. A steady, purposeful adjustment is easier to follow than text that jumps around whenever an object enters the picture. Where a speaker label is needed, include it in the caption text or a consistent layout rather than relying on position or colour alone.
Think about the whole frame and the likely crop. An open-captions export may be viewed in a vertical feed, cropped on a mobile screen or surrounded by player controls. A cue placed comfortably above the bottom edge in the editor might be clipped or compete with the playback interface. Check the actual destination view, not only a full-size preview. The guide to vertical YouTube video streams is relevant when your source or viewing layout is vertical, but the safe placement still depends on your own composition and player.
Keep the visual language consistent
Consistency reduces the work of learning each cue. Keep typeface, weight, backing, alignment and speaker-label conventions stable through a programme unless a clear content reason calls for a change. If a speaker is named on first appearance, for example, use a predictable way of showing names later. A viewer should not have to work out whether a colour or a sudden change of style signals a new speaker or simply a new scene.
Consistency does not mean refusing to adapt. If a pale background makes the usual treatment hard to read, use a considered adjustment that preserves the same overall visual language. You might maintain the same text face and size while making the backing more opaque. The aim is continuity in the reading experience, not identical pixels over every kind of footage.
Captions need to carry the sounds that matter, not decorate every moment with arbitrary labels. Include a meaningful bell, alarm or off-screen voice when it helps explain the video; skip sounds that add nothing to understanding. Identify speakers when the image does not make the speaker apparent. Keep labels concise and make sure the punctuation and casing are consistent enough to scan.
For repeated programmes, create a short style note before preparing a batch of files. Record the chosen type treatment, line breaks, speaker-label pattern, placement approach and how you handle sound cues. This is especially useful when a playlist combines material edited at different times. The note is a reference for your own decisions, not a guarantee that another platform will reproduce them.
Preview on changing scenes and real devices
Do not approve subtitles from a still frame alone. Find representative footage: a bright exterior, a dark shot, a detailed or moving background, and a scene where text, faces or hands carry information. Watch the captions in motion and at normal playback speed. A treatment that appears crisp while paused can blur or become distracting when the picture moves.
Then inspect the exported file on a small screen and on the destination platform. Check that line breaks remain sensible, text is not clipped, timing is intact and controls do not cover the cues. If your audience commonly watches on a phone, a desktop edit preview is not enough. Consider the actual crop and player chrome, especially for vertical video or a stream with on-screen labels.
Include scene transitions and loop points in the test. A cue can linger into a shot where its placement blocks a sign; a repeated file can restart with an awkward gap or a caption already in progress. For a continuous YouTube channel, inspect the file as it will be used in the broadcast, not only in an editing timeline. If the playback method or player changes, review the result again.
Keep a short review checklist: Can you read every cue without concentrating unusually hard? Does the background treatment hold up across the selected scenes? Is any relevant image obscured? Are sounds and speakers identified when needed? Does the export still look and behave as intended on the platform? These questions expose practical problems without pretending one design test answers every accessibility question.
Check platform and file-format support
Subtitle files do not all carry the same styling or positioning information, and a player may ignore styling that your editor displays. YouTube Help says some subtitle and closed-caption formats contain positioning and style data. Its supported subtitle and closed-caption file formats documentation describes format-specific support; its WebVTT documentation, for example, includes positioning support but lists only bold, italic and underline for styling. Check the current help page for the format you plan to upload.
The W3C also warns that support for author-positioned and styled captions varies among browsers and media players. Some players use their own default presentation, while others let viewers adjust options such as size, colour and position. This means a setting that works in one editor or playback window may not survive an upload or another device unchanged. Preview the uploaded result where possible, and do not describe a closed-caption file as though it were a burned-in image.
A practical export workflow is to keep the text and video versions clearly labelled, upload or attach the intended caption file, then test the platform’s actual playback. If you burn captions into the video, inspect the encoded frame and likely crops. If you rely on a separate file, test that it loads and that the player gives viewers a readable result. The guide to scheduling a YouTube live playlist with prerecorded video addresses playlist scheduling; whichever workflow you use, verify captions independently rather than assuming the schedule preserves them.
For a 24/7 recorded channel, caption styling is only one part of preparing the source file. If the recurring nuisance is leaving a computer running just to keep a prepared video on air, StreamNeo removes that particular need: you upload the video, provide your YouTube stream key, and the broadcast continues with your computer switched off. It does not choose, proofread or guarantee the appearance of your captions, so review the finished video and platform output before using it.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Should subtitles be white with a black background?
That is a familiar starting point, and Section508.gov gives white text on a translucent black background as an example. It is not right for every image, screen or player, so check whether the backing and text remain legible over your own footage and do not obscure relevant detail.
Where should captions go on screen?
Try the lower centre first, then move text if it covers a face, sign, label, news banner or other information viewers need. Check the whole frame and likely mobile crop; the useful position depends on the composition and the player.
Are subtitles and captions the same thing?
Usage varies, but subtitles often present dialogue, sometimes translated, while captions also include relevant non-speech audio and may identify speakers. Be explicit about the purpose of your text, especially when accessibility for Deaf and hard-of-hearing viewers is important.
Will my styling look the same after uploading a subtitle file?
Not necessarily. Styling and positioning support vary by file format, platform and player; closed captions may also be rendered using player defaults or viewer settings. Check the destination platform’s current documentation and preview the uploaded result.