A scoreboard overlay is a graphic supplied by a scoreboard service; OBS, vMix or another production tool places that graphic over your live video. To add one, create a sport-specific scoreboard, copy its public display URL, add it as a browser source, size it to your production canvas and test that score changes appear before the event.
The scorekeeper can operate the service’s control page from a separate phone, tablet or computer while the production operator manages cameras and scenes. The connection between the control page and the display still needs to be set up and working: a URL by itself does not guarantee that updates will appear.
Choose a scoreboard and production workflow
Start by separating the two jobs. The scoreboard service provides a graphic and a control page for entering the score and other game details. Your production software takes the graphic, composites it into the programme and sends that programme to YouTube. OBS calls the relevant input a Browser source; vMix calls it a Web Browser input.
This URL-based workflow is not tied to one scoreboard provider. Look for a service that supplies a display or overlay URL and instructions for your production software. A hardware switcher may take a different route or require a different link format, so check both the switcher’s documentation and the scoreboard provider’s instructions before settling on this approach.
Choose for the game you actually cover. A simple scorebug may suit a local football match, while another sport may need sets, periods, fouls or a clock. The available fields and layouts vary by service. Check that its sport-specific controls match the way your event is scored rather than assuming a generic score graphic will cover every case.
| Decision | What to check | Why it matters |
|---|---|---|
| Sport and scoring | Teams, score, clock and relevant period, half, quarter or set fields | An unsuitable layout can omit details viewers need or expose fields you will not use. |
| Display style | Compact scorebug or a larger board; placement and team branding | The graphic must fit your camera view without covering play. |
| Control | Whether a second device or another operator can use the control page | This lets the scorekeeper work without changing production scenes. |
| Production fit | Display URL and current instructions for OBS, vMix or your chosen tool | Compatibility claims are provider-specific; confirm them rather than relying on a generic list. |
| Connectivity | What happens if the control device or production computer loses network access | The crew needs to know how to recognise a stale score and recover before going live. |
If one volunteer has to run the camera, switch scenes and keep score, simplify the layout and rehearse the controls. When possible, assign scorekeeping to another person. This division reduces the chance that a score change is missed while the production operator is handling a cut or checking the programme output. For the wider relationship between timing and what viewers see, see why low latency matters for live sports streaming.
Create the scoreboard and copy its overlay URL
Set up the board in the scoreboard service before opening your production scene. Select the sport, enter the team names and choose a layout that will remain readable at the size you plan to use. Configure only fields that matter for the game. A visible clock is useful if someone will keep it accurately; an unused or incorrectly configured clock can confuse viewers.
The service may provide more than one link. Use the public display or overlay URL in the production source, not a private control-panel URL, if the service distinguishes between them. The display link is for showing the graphic; the control link is for changing its data. Treat the control page as an operational tool and do not put its private URL on screen or share it more widely than needed.
Keep the two links labelled somewhere the crew can find them, for example in the event run sheet: “scoreboard display” and “scorekeeper control”. Do not rely on a volunteer remembering which browser tab is which during a match. If access is tied to an account, check who can open the control page and whether the scorekeeper’s device can reach it on the venue network.
Before building out the production scene, open the display URL in a browser and make sure it shows the intended board. This is a quick way to catch a copied control URL, an incomplete setup or the wrong sport layout. Keep the service’s setup page available for its current instructions; options and link behaviour can change, so use the provider’s documentation rather than assuming all scoreboard tools work identically.
Add the URL as a browser source
In OBS, select the scene that will carry the match, then use + in the Sources panel and choose Browser. Give the source a name that makes its purpose clear, such as “Match scoreboard”, and paste in the public display URL. Set the source width and height to match the production’s base canvas resolution; you can refine placement after it loads.
In vMix, use Add Input, choose Web Browser, paste the display URL and add the input. To show it in the programme, activate it with a numbered overlay button, then use the input’s Position settings to move, zoom or crop the board as needed. The names of controls can shift between software versions, so if the interface differs, consult the current OBS Browser Source guide or vMix’s Web Browser input documentation.
Check which link you pasted before troubleshooting anything else. A control page displayed in the production can expose buttons, account details or a blank interface instead of the intended graphic. Conversely, putting the display link on the scorekeeper’s device does not necessarily give them the controls. Keep source and control roles distinct.
A browser source depends on the production computer’s ability to load the web page. If it does not appear, first confirm that the source is enabled, visible in the active scene and above the camera or video source in the layer order. Then check that the URL is correct and that the computer can reach the service. Reloading the page can help after those checks, but it will not fix a wrong link or a blocked connection.
Match the overlay to the production canvas
The canvas is the working frame into which your camera, graphics and other sources are composed. Set the scoreboard source dimensions to the canvas resolution actually configured in OBS or your production tool. A full-HD canvas such as 1920 × 1080 pixels is a common example, not a setting to copy blindly. If your canvas differs, use its dimensions instead.
Matching the source dimensions gives the browser graphic the frame it expects. If those dimensions are wrong, the overlay can be scaled, cropped or look soft after you resize it. In OBS, check the base canvas resolution in the video settings before configuring the Browser source. In vMix, compare the project’s production format with the web input and its Position controls.
Keep a note of the canvas settings in the crew’s run sheet. If someone changes the production format after the overlay is positioned, revisit the source size and placement. A quick review of the dropped-frame checks for YouTube livestreams can also help the crew distinguish a composition problem from a broader stream-performance problem; the scoreboard’s dimensions and dropped frames are separate things to diagnose.
Once the board is on the canvas, inspect it at the same output size viewers will receive, not just in a close-up configuration window. Fine text can look readable on the production display yet become hard to follow in the delivered picture. Choose the simplest layout that shows the score and game details clearly, and avoid shrinking the graphic until its labels become indistinct.
Position the scoreboard over the video
In OBS, sources higher in the Sources stack appear over the sources below them. Move the Browser source above the camera or match-video source, then place it in a corner or along an edge where it will not hide the ball, players, a referee or other important action. Lock the source once it is correctly positioned if an accidental drag during production would be disruptive.
In vMix, activate the browser input as an overlay and adjust its Position settings. Use zoom and crop only to solve a specific fit problem. Cropping can remove labels or clock details, while enlarging a board can obscure more of the picture. After any adjustment, verify the complete graphic in the programme output, not only in the input’s preview.
A clean composition should leave the score easy to find without turning it into the main subject. Check the board against the camera angles you expect to use: a position that avoids the action in a wide shot may cover a player’s face or a sign when the camera cuts closer. Ask another crew member to watch the programme preview and point out collisions before the event.
If the board has a black background or transparency is missing, do not assume every source or switcher handles it the same way. Check the scoreboard provider’s transparency instructions and the production software’s settings. A graphic that looks correct in a standalone browser may not composite as expected in a particular workflow.
Operate the control panel from a separate device
Open the scorekeeper control page on a phone, tablet or second computer and keep it separate from the production view. The scorekeeper can then update the score, clock and available game fields without touching the scene or camera controls. This split is helpful even when both jobs are handled by volunteers who share a small table: one device remains the programme control surface, and another is used for scoring.
Agree who is responsible for each change before the match. For example, the scorekeeper can confirm a score with the referee or event official and then enter it, while the production operator watches the outgoing picture. If one person must do both, decide when they will make updates and avoid changing scenes at the same time unless the workflow has been rehearsed.
The controls are only useful if the service’s control page and the display source are correctly connected. Verify that an edit made on the control device reaches the display URL. If it does not, check that the control page is connected, the production source uses the display URL, and both devices have network access. Some browser sources may reload when hidden; check the service and source behaviour if the score or clock appears to reset after a scene change.
Connectivity deserves a practical check at the venue, not just at home. A phone may be on mobile data while the production computer uses venue Wi-Fi, or a network policy may block a page on one device. Where the production depends on a web overlay, confirm access from the actual devices and connection you will use. Keep the guide to handling upload drops on Indian broadband in mind for the stream’s outgoing connection, while recognising that network access for the overlay is a separate check.
The overlay is not a substitute for a plan to recover the programme if the stream itself stops. If your crew operates a longer-running channel outside match coverage, see how automatic livestream restarting works when FFmpeg stops. That is a different problem from getting score updates into a browser source.
Test score updates before the event
Run a private or unlisted rehearsal before match day. Use the same production computer, network, scene and control device planned for the event. Enter a test score and, if relevant, change the clock or period. Confirm that the production preview shows each update, that the graphic remains legible and that the scorekeeper can operate the controls without altering the programme scene.
Use a short checklist rather than relying on a quick glance:
- Is the display URL loaded, and is the source visible above the match video?
- Does the board fit the actual production canvas without unwanted crop or blur?
- Do score, clock and sport-specific fields change on the display when edited from the control device?
- Does the graphic stay in place when you switch between the scenes planned for coverage?
- Can both devices reach the relevant pages on the venue connection?
- Does the output preview remain clear at the intended viewing size?
Test a correction as well as an increase in score. Volunteers may need to fix an entry, and it is better to know how to do so before viewers are watching. If a clock is included, agree who starts, pauses or resets it and rehearse those actions. The available controls vary by provider and sport; do not assume that a feature described for one scoreboard is included in another.
Check behaviour after hiding and showing the source or switching scenes. If the browser source reloads, see whether the board reconnects to the current state or briefly shows an initial state. If it does not behave as expected, follow the provider’s instructions for source reloads and state synchronisation, and make a clear operational plan for the scorekeeper. Do not count a graphic as tested just because the page loaded once.
If something fails, diagnose one layer at a time. For a blank graphic, check visibility, layer order, URL and network access. For a wrong size or softness, verify source dimensions against the canvas and undo unintended transforms before resizing. For an unchanged score, verify the control connection and link type first; then refresh only after confirming that the source is the public display URL. This order avoids masking one problem with another.
When the file and channel are ready, a hosted, always-on stream can remove the need to keep a production computer running overnight, but it does not replace testing the scoreboard workflow used for a live match.
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
Can I add a scoreboard to OBS without a particular vendor?
Yes, provided your scoreboard service supplies a display URL that OBS can load as a Browser source. The service is responsible for the graphic and controls; OBS is responsible for placing that graphic into your programme. Check the current instructions for both products, as the link types and settings vary.
Can I update the score from a phone while vMix is running?
You can use a separate phone, tablet or computer for the scorekeeper control page while vMix handles the production. First confirm in rehearsal that edits on the control device reach the display input. Keep the control page distinct from the public display URL.
Why is the score graphic blank or the wrong size?
For a blank graphic, check that the source is visible, above the video layer, using the display URL and able to reach the service over the network. For sizing problems, set the source dimensions to the actual canvas resolution and reset unintended crop or transform settings before repositioning it.
Will the score update automatically once I add the URL?
Not necessarily. The display source and control page must be set up correctly, reachable and tested together; a URL alone does not ensure that score changes will appear. Rehearse score and clock changes on the same devices and connection planned for the event.