How to Create Broadcast Lower Thirds That Don't Look Amateur
Lower thirds are the most common graphic in broadcast. They're also the most commonly botched. Here are the five mistakes that give it away — and how to fix every one of them.
Look at the bottom of almost any live broadcast and you will find it: a horizontal band of text in the lower portion of the frame, identifying a speaker, a score, a location, a headline. The lower third. It is the workhorse of broadcast graphics — so common it has become nearly invisible. And that invisibility, when it works, is exactly the point.
When it does not work, however, the lower third announces itself immediately. The font is wrong. The contrast fails. The animation overshoots. The hierarchy is muddled. Viewers may not be able to articulate what they are seeing, but they clock it in under a second: this looks cheap.
Broadcast is an unforgiving medium. It does not allow for zoom or pinch. It does not allow for dark mode. It plays at frame rate, at compression, on screens calibrated for television. The lower third that looks fine on your design monitor may look entirely different in playout. This guide covers the five mistakes that appear most consistently in amateur broadcast graphics — and exactly how to correct them.
Wrong Safe Area Placement
Broadcast uses a concept called action safe and title safe zones. These are inset boundaries that define the area of the frame guaranteed to be visible on every display and through every transmission format. Content that bleeds to the very edge of frame risks being cut off — by overscan on older displays, by edge cropping in streaming encoding, or by the aspect ratio handling of certain playout systems.
The title safe boundary is the inner of the two zones. At 1920×1080, the conventional title safe inset is 5% on every side — approximately 96 pixels. Any text or graphic element that matters should sit within this boundary. A lower third that hugs the bottom edge of frame marks itself as amateur the moment it appears on a reference monitor.
The fix is straightforward: enable safe area guides in your graphics editor and treat them as hard boundaries, not suggestions. In CloudMonet, canvas guides can be toggled as overlays during design so the safe zone is always visible while you work.
Fonts That Were Not Designed for Motion
Thin serif fonts look elegant in print. On screen, at broadcast frame rates and after compression, thin strokes flicker. This phenomenon — called strobing or temporal aliasing — is a known problem in broadcast and there is a reason that news channels, sports networks, and live event producers overwhelmingly use clean, medium-weight sans-serifs for their on-screen text.
The mechanism is simple: thin horizontal strokes, particularly those thinner than one pixel at display resolution, beat against the scan frequency of the display. The result is a vibrating, illegible mess that draws the eye for entirely the wrong reasons.
Safe typeface choices for broadcast: Montserrat Medium, Inter, Barlow, Noto Sans, or any condensed sans-serif with a minimum weight of 400. Avoid anything below 300 weight, hairline serifs, or decorative scripts. When in doubt, test your chosen font on actual broadcast output — not your design monitor — before committing to it across a production.
Low Contrast Text
Broadcast signals compress colour information. What presents as sufficient contrast on a consumer monitor — which is typically over-saturated and over-brightened relative to broadcast calibration — can become nearly unreadable after encoding. The minimum contrast ratio for broadcast text is 4.5:1 against its background.
The single most reliable fix is a solid or semi-opaque backing plate behind all text. Never rely on the video content beneath the lower third to provide contrast. The video could be anything — a bright sky, a white shirt, an overexposed exterior shot. The lower third must be legible regardless of what is playing behind it.
85–95% opacity on the backing plate is generally the sweet spot: sufficient contrast without the graphic feeling completely opaque and heavy. A fully transparent backing is almost always a mistake. A fully opaque one can feel too solid unless it is part of a deliberate design aesthetic.
Animation That Draws Attention to Itself
The job of a lower third animation is to bring the graphic on and take it off without the viewer consciously noticing the transition. If someone is watching the animation instead of the content, it has failed. This is the paradox of broadcast motion design: the better the animation, the less it is seen.
“The best broadcast animation is the animation nobody remembers watching. It simply arrives, and then it is gone.”
— Broadcast design principleThe amateur tell is almost always one of three things: animation that is too slow (the graphic feels like it is loading rather than appearing), animation that overshoots (elastic bouncing or spring physics that belong in a mobile app, not a broadcast), or animation that is too complex (three-dimensional spins, particle effects, or cascading elements that turn a name super into a spectacle).
Wipe and reveal transitions are the most broadcast-appropriate choices for a standard name super. Fade-in is acceptable. Slide-in from below or left works well when paired with a matching backing plate motion. Anything involving rotation, scale bounce, or blur smear is almost certainly wrong for a production that needs to look professional.
Broken Visual Hierarchy
A name super carries two pieces of information: the name, and the title or role. These need to be visually distinct. When both lines are rendered at the same size, the same weight, and the same colour, the viewer must actively parse the graphic to understand which is which. That parsing takes cognitive effort. In broadcast, you have roughly two seconds of viewer attention before the lower third is taken for granted or ignored.
The hierarchy rule is simple: the primary element — the name — should be 20–30% larger than the secondary element, or meaningfully differentiated in weight, colour, or both. The two lines should read as clearly different in importance at a glance, without needing to be read word for word.
The colour accent bar — a thin horizontal line, typically in a brand or network colour, above or below the text block — is the classic broadcast solution for anchoring the lower third visually and reinforcing the primary line. It draws the eye to the name line first, then lets it fall naturally to the title below.
Building a Lower Third in CloudMonet
With the principles above as a foundation, here is a practical walkthrough for building a broadcast-ready name super in CloudMonet Studio.
Start at 1920×1080. Place a rectangle backing plate at approximately Y 820px from top, inset 96px from each side edge. Apply your brand colour at 88% opacity. Add a thin horizontal accent bar — 3px height, full backing plate width, solid brand colour, no opacity reduction — above the text block.
Add two text layers: name line at 22–26px in a medium-weight sans-serif, white; title line at 13–14px in the same family, 400 weight, uppercase, letter-spaced, in a mid-grey (around #9ca3af works well against dark plates). Group all three elements.
In the CloudMonet timeline, set a Reveal animation on the accent bar at 12 frames ease-in-out. Follow with a Reveal on the name line at 10 frames, offset by 8 frames. Fade the title line in over 10 frames, offset by a further 6 frames. Total build-in: approximately 28 frames, or just under one second at 30fps. Build-out mirrors this in reverse at 20 frames total.
Publish as an HTML5 URL. In OBS, add as a Browser Source at 1920×1080. In vMix, load as a Web Browser input. Test on your actual output signal — not just the preview — before going live.
One Thing Most People Skip
Test on a real display, not your design monitor. Broadcast monitors are calibrated to different standards than consumer displays. What reads as clean and legible on a MacBook can appear blown out, over-compressed, or muddy on a broadcast reference monitor. If you have access to a broadcast display, always do a final check there before going live. If you do not, at minimum test on a second screen with its brightness and saturation reduced to approximate broadcast calibration.
The extra ten minutes before a production is always worth it. The lower third that fails on air is the one nobody thought to test.
A Note on Data-Driven Lower Thirds
Static name supers are straightforward. Where lower thirds become genuinely interesting — and where most tools fall short — is when they need to update in real time. Sports lower thirds that pull live scores. Financial overlays with live data. Guest name supers populated automatically from a rundown sheet.
CloudMonet supports live data binding from Google Sheets and REST APIs, which means your lower third template stays visually consistent while the content updates automatically between takes or between guests. The design work happens once. The data does the rest.