Choosing iRacing broadcast overlays for a league
What league viewers need from iRacing overlays, how the main tools differ, and how to test a package before race night.
A league overlay package needs readable timing, driver cards, flags, results and sponsor graphics that work together in OBS. This guide covers what viewers actually need from those graphics and how the main tools differ. We build EDR Broadcast; facts about other products were checked against their official websites on 22 August 2026.
Choose by the graphic you need most
Checked 22 August 2026.
For a new league broadcast, start by testing EDR Broadcast: it brings 45+ coordinated overlays and 15+ themes into one application, Pro adds the Auto-Director, incidents and replay tools, and League adds the WYSIWYG Theme Editor. Compare ATVO when an established NDI workflow is essential, and SDK Gaming when driver HUD and detailed timing are the main job.
A completely custom TV package
EDR Broadcast is the natural first test for a new league package: its WYSIWYG Theme Editor (League plan) builds the custom look inside the same browser-source system that runs timing, cameras, incidents and replays. Its standard output workflow uses individual browser sources, while NDI output is available on request with Enterprise. Choose ATVO when an existing NDI theme workflow is the non-negotiable requirement.
A clean OBS package a small crew can run
EDR Broadcast provides individual browser-source overlays and connects them to camera, incident and replay workflow.
Detailed timing you can style component by component
SDK Gaming should be on the shortlist. Its Live Streamer web overlay exposes detailed layout and styling controls.
Free self-hosted graphics that never leave your PC
Use a local open-source project if your crew is comfortable installing Python, maintaining updates and supporting the stack.
Driving overlays rather than a league broadcast package
RaceLab or JRT may be a better fit. Their centre is driver information, timing and strategy, not complete race-night direction.
The seven overlays that carry a league broadcast
A complete package uses several focused graphics, each shown when it has a job. It does not leave every widget on screen for the entire race.
Leaderboard
Overall and class position, gaps, pit state and a clear focus indicator. It must remain readable when the field has 40 cars.
Focused-driver card
Name, number, team, class and the one or two statistics relevant to the current story. Do not turn it into a database dump.
Battle or relative box
A compact view of the cars around the target. This tells viewers why the camera is staying with P14 instead of the leader.
Flags and race state
Green, caution, restart, white and chequered information should be obvious without covering the action.
Grid and results
Starting order, class separation and final positions give the show a proper beginning and ending.
Track map
Most useful in multiclass racing, pit cycles and long endurance events. Class colour and focused-car emphasis matter.
Sponsor and race-control graphics
Sponsor straps, penalty notices and steward messages need dedicated safe areas rather than being squeezed into the timing tower.
The main overlay software choices
Checked 22 August 2026.
| Tool | Overlay strength | Production route | Best for |
|---|---|---|---|
| EDR Broadcast | 45+ coordinated overlays, 15+ themes and the WYSIWYG Theme Editor (League) | Individual browser sources plus operator control | Leagues and small crews running the full show |
| ATVO | Visual Theme Editor and established custom packages | NDI or window capture | Designer-led custom productions |
| SDK Gaming | Detailed timing and configurable web components | Web overlay in OBS | Timing-heavy streams and connected HUD use |
| iSimBroadcaster | League, championship and season graphics | Local browser sources | Season data and championship storytelling |
| Self-hosted open source | Useful local graphics with code-level control | Local web servers and browser sources | Technical crews prioritising ownership and cost |
| RaceLab and JRT | Driver timing, strategy and HUD information | App, browser or streaming layouts | Drivers, analysts and simpler streams |
Sources: ATVO, SDK Gaming, iSimBroadcaster, RaceLab, JRT.
For full product details and links, see the iRacing broadcast software comparison. If you are moving from a specific tool, read the ATVO alternative guide or the SDK Gaming alternative guide.
Browser source, NDI or window capture?
Checked 22 August 2026.
Browser sources are easy to duplicate, layer and toggle inside OBS. Each graphic can have its own URL, size and visibility. They suit web-based overlays and local app servers.
NDI sends a video or graphics feed across the machine or network. It can preserve alpha and suits multi-PC studios, but it adds an NDI layer to the production. ATVO recommends NDI. EDR Broadcast uses individual browser sources as its standard workflow, while NDI output is available on request with Enterprise.
Window capture is simple when a tool renders its own output window, but the operator must protect the capture from resizing, focus and desktop changes. Test the exact route at your target resolution and frame rate.
What makes an overlay readable
Design for the phone viewer. Many viewers see the stream on a small screen. If a surname, gap or class colour only works on your 32-inch monitor, it does not work.
Use class colour consistently. The same class should use the same colour on the leaderboard, map, driver card and results. Never make viewers relearn the palette.
Limit simultaneous messages. A timing tower, ticker, lower third, battle box and sponsor strap can all be individually good and collectively unreadable.
Respect safe areas. Keep important information away from platform UI, captions, chat crops and the edges used by vertical clips.
Show changes, not everything. Use overlays to explain a pass, penalty, pit cycle or replay. Hide information when it is no longer helping the story.
Label live and replay clearly. A beautiful replay without an obvious label makes viewers misunderstand the current race.
Multiclass overlays need different logic
Overall position is not enough in an endurance broadcast. The tower must make class position obvious, the map needs class colours and the focused-driver card must explain whether the car is racing for an overall or class result.
Pit cycles also distort simple gaps. A useful broadcast separates track position from strategic position and gives commentators enough context to avoid calling a temporary lead as a genuine pass. A track map earns its space when it explains traffic, pit cycles and where the next battle will meet. The multiclass broadcast guide covers this in detail.
A race-night overlay test
- Record a 20-minute practice stream at the exact output resolution your viewers will receive.
- Watch it once on a television and once on a phone without pausing.
- Write down every moment you could not identify the car, class, gap or live versus replay state.
- Remove one persistent graphic and see whether the picture becomes easier to understand.
- Ask somebody unfamiliar with the league to name the leader, current battle and flag state within ten seconds.
- Only after that test, add sponsor or secondary data elements.
Start with the essential scene
Build the essential scene on the Free plan first: leaderboard, lower thirds, ticker, flags, grid intro and podium, with 2 looks on 1 machine. Add Pro only when camera and replay workflow solve a real production problem: it adds the Auto-Director, replay, incident detection, race control and all 15+ public themes, on 2 machines. The Theme Editor for a custom league look comes with League, and Enterprise covers custom themes and overlays. Check current plan details before choosing a workflow.
Frequently asked questions
Checked 22 August 2026.
What is the best free iRacing overlay software?
It depends on your tolerance for setup. EDR Broadcast’s Free plan includes core overlays at no cost: leaderboard, lower thirds, ticker, flags, grid intro and podium. Open-source self-hosted projects can offer more control but require installation and maintenance.
Does ATVO work as an OBS browser source?
ATVO’s official site says browser-source capture is not supported. It recommends NDI or window capture.
Can I use RaceLab for a league broadcast?
You can use racing overlays in a stream, but RaceLab’s product centre is driver-facing information across multiple sims. Compare it with dedicated broadcast software if you need race control, replay and league operations.
How many overlays should stay visible all race?
Usually fewer than you think. A readable leaderboard or ticker may stay persistent, while driver cards, battle boxes, flags and sponsor graphics should appear when they have a job.
Do browser-source overlays hurt performance?
They use resources, especially when several animated pages render at high frame rates. Test the complete scene and disable sources you do not need.
Can EDR Broadcast overlays use my league branding?
Yes. EDR Broadcast includes 15+ ready-made themes (2 looks on Free, all of them on Pro), and the League plan adds the WYSIWYG Theme Editor for building a custom league look across 45+ overlays.