A practical desktop setup is to run a speedrun timer, configure it for your game and category, then add its window to an OBS scene. A capture card is not needed for the timer; console players may need one only if they want to bring console gameplay into the PC running OBS.
The timer and the gameplay are separate sources in your scene. You can capture the timer window directly, or use a browser overlay if your chosen timer supports a compatible one. Before going live, check that the timer is legible, the split timing follows the category rules, and the layout does not hide important gameplay.
Choose and configure a speedrun timer
Start with a timer that suits the game and the way you intend to time the run. LiveSplit is a common desktop starting point: its project page describes a configurable display, Speedrun.com integration, game-time support and auto-splitting where a supported game splitter is available. Those features are conditional; they do not mean every game has an auto-splitter or that every timing method is interchangeable.
For a first setup, keep the goal modest: get a timer running on your computer, make its text readable at stream size, and ensure you can start, pause or reset it deliberately. LiveSplit's downloads page recommends reading its FAQ and introductory material before starting. Follow the current instructions there for the version you download, since interface details may change.
Check the timer's requirements and supported features before relying on them. A timer may run independently of the game, while automatic detection or a browser overlay depends on game-specific or project-specific support. If the game has no supported splitter, manual splits can still show progress, but you will need to trigger them yourself.
It helps to distinguish the timer from the broadcast software early. The timer measures or displays the run; OBS assembles gameplay, timer and any other sources into the scene that is recorded or streamed. If you already use OBS, add the timer to a copy of your gameplay scene first rather than changing the scene you depend on for a live broadcast. If you are still choosing a streaming workflow, our overview of software for high-resolution YouTube streams can help you think through the role of each application.
Set up the run and splits
A split is a checkpoint in the run. For example, a game might have checkpoints for reaching a first area, defeating a boss and completing the final objective. The displayed rows let viewers see current progress and, depending on the timer configuration, compare a segment with a previous or target time.
Set up the game and category you are actually running. If a compatible split file exists for that category, load it and check that its segment names and order match the rules you intend to follow. Otherwise, create the checkpoints yourself. Avoid borrowing a file just because its game title matches: categories may use different routes, completion conditions or timing conventions.
Read the current rules for the game and category from the relevant community or leaderboard before deciding how to time the run. Timing standards can vary. Do not assume a timer's default is the one your category expects, and do not assume that a displayed time proves a run meets the rules. The timer is a presentation and tracking tool; the category rules determine what counts.
Before adding the timer to OBS, practise starting a run and advancing through a few splits. Confirm that the names fit the display, that the order is right, and that reset or pause controls behave as expected. If automatic splitting is available for the game, test it against the game state and category rules rather than treating the feature label as a guarantee. Manual control is a reasonable choice when you prefer to decide exactly when a split occurs.
For a stream, the viewer needs only the information that helps follow progress. A long list of narrow segment names may be useful to you at full desktop size but difficult to read in a small video. Edit labels carefully, remove information you do not need on screen, or use a more compact layout. Keep a full split file for your own timing if you want, and make the on-screen view serve the viewer.
Add the timer window to OBS
The straightforward route is to capture the timer application window. Open OBS and the timer, select the scene where you want the display, then add a Window Capture source and choose the timer window. The exact names and controls can differ across OBS versions and operating systems, so use the current OBS interface and help if a menu item is labelled differently.
A community answer on Speedrun.com describes capturing the timer window in OBS. Treat this as a general workflow rather than a verified, version-specific OBS tutorial. After selecting the window, check the OBS preview: the timer should appear, update as you interact with it, and remain visible when you switch back to the game.
If the preview is blank or does not update, check that you selected the correct window and that the timer is open. Window-capture behaviour can vary with the application, display settings and system. Try the available capture method and confirm it in a recording rather than assuming that seeing the timer on your desktop means OBS is receiving it correctly.
Add the timer as its own source so you can resize, position, hide or show it without altering the game capture. Use OBS's preview to size it relative to the final canvas, not just your monitor. A timer that looks comfortably large on a desktop can occupy too much of a 1080p stream layout when reduced on a phone, while a very small timer may disappear at that same viewing size.
Record a short test before using the scene live. Start a run, advance at least one split, and check the resulting video for legibility, updates and unintended obstruction. This catches problems that the static preview cannot show, such as a cropped label or a timer that freezes when another window is focused. For an ongoing broadcast, include this kind of visual check in a broader live-stream monitoring routine.
Use a browser overlay if supported
A browser overlay is an alternative to capturing the timer window. In this setup, the timer or a companion tool provides a page or data feed that OBS can display with a Browser Source. It can make it easier to style a timer or integrate it with other on-screen elements, but it is not a universal feature of speedrun timers.
Check the documentation for the exact timer and overlay combination you plan to use. OpenSpeedRun, for example, documents an optional local WebSocket overlay server for an OBS browser source in its project documentation. Its server is off by default and must be enabled according to that project's instructions. This example does not establish that LiveSplit or another timer offers the same feature, or that the setup works unchanged on every system.
Before choosing the browser route, confirm which application provides the overlay, whether it must be running alongside the timer, and what address or configuration OBS needs. Follow the project's instructions rather than guessing a local address or changing settings that are not documented. If an overlay depends on a local connection, test that connection from OBS itself; a browser page opening in your normal browser does not necessarily prove the OBS source is configured correctly.
The browser route is useful when its supported layout is easier to read or customise than the timer window. The trade-off is another compatibility and configuration step. If the timer does not document a compatible overlay, use window capture instead of assuming a generic browser source can read its timing data.
| Approach | Useful when | Check before relying on it |
|---|---|---|
| Timer window capture | You want a direct, simple display from a desktop timer | OBS is capturing the correct window and the text remains legible in a recording |
| Browser-source overlay | Your timer or companion tool documents a compatible feed | The required server or connection is enabled and OBS can display the overlay |
| Console gameplay through a PC | You want console video in a PC-based OBS scene | The console, capture path and PC setup are compatible; the timer remains a separate software source |
Place the timer without blocking gameplay
Put the timer where the game leaves useful visual space. Look for a corner or margin that is consistently quiet, but check more than one moment in play. A health bar, minimap or subtitle area may move or appear only during particular scenes. A placement that looks clear at the title screen can cover information once the run starts.
Use a test recording to judge the layout at normal viewing size. Keep the timer large enough for its digits and split names to be read, but not so large that it becomes the main image. If the split list is long, consider showing fewer rows or shortening labels rather than shrinking every line until it is unreadable.
Contrast matters as much as size. A timer with text that blends into bright or moving gameplay can be hard to follow. If the timer allows a background, border or text colour adjustment, choose a treatment that remains distinct over the game without hiding more of it than necessary. Check both dark and bright gameplay scenes, and make sure the display remains visible when the game changes camera or location.
Do not rely on a single screenshot. A speedrun moves through different menus, animations and environments, and some games place important prompts near the screen edges. Watch a short recording with sound and motion, and check the view on a smaller screen if that is where much of your audience watches. Make one change at a time—position, size or styling—so you can see which adjustment improves readability.
If the timer is only useful during the run, make it easy to hide for menus, breaks or scenes where it would cover important content. In OBS, keeping it as a separate source lets you toggle it without rebuilding the scene. If you plan distinct starting, gameplay and break scenes, duplicate or adapt the layout and verify each scene before streaming. For a channel that also rotates through pre-recorded content, the scene setup is separate from the process of switching videos automatically in OBS.
Route console gameplay through a PC if needed
A console player can still use a software timer. The question is how the gameplay reaches the broadcast scene. If you are streaming directly from the console, a PC-based OBS scene may not be part of your setup. If you want OBS on a PC to combine console gameplay with the timer, you need a way to bring the console's video into that computer.
A capture card can be part of that console-to-PC video route. It does not create, run or improve the timer; the timer remains software running on the PC and is added to the OBS scene as another source. Whether a capture card is needed depends on the console, the streaming method and the video path you choose. Check your console and capture-device documentation before buying hardware, since this guide does not recommend a particular model or confirm compatibility for every combination.
Once gameplay is visible in OBS, add the timer using window capture or a documented compatible browser overlay. Keep the gameplay and timer as separate sources so you can adjust their size and position independently. Test the full route together: console picture, game audio, timer updates and the final recording. A capture path that works for video does not automatically confirm that audio or the timer is configured correctly.
If you play on a PC, the game and timer may both be available to OBS without a console capture path. You still need to verify that the game capture and timer source coexist in the scene and that the timer stays readable over the game. The hardware question concerns getting gameplay into the scene, not whether the timer itself can be displayed.
Test the complete scene before going live
Treat the scene as a small production setup, not just a timer pasted over a game. Make a short local recording with the actual game, category and timer layout. Check that the run starts as intended, split updates are visible, audio remains as expected, and no important game information is hidden. If you use a browser overlay, repeat the test after restarting OBS or the overlay tool so you know what must be open for the scene to work.
Keep a simple fallback in mind. If an overlay stops responding, you may be able to switch to the timer window or hide the source while you troubleshoot, provided you tested that alternate arrangement in advance. Do not promise viewers a particular timing display if you have not checked it in the live scene. A clear, functioning game view is more useful than an elaborate overlay that fails during the run.
When you change the game, category, display size or capture method, test again. Such changes can alter the split list, timer window or available screen space. For a stream that runs for extended periods, a quick scene check after software updates or a layout change can catch a source that no longer points to the intended window. Our guide to keeping a YouTube live promo running after a Windows update covers the separate operational risk of updates interrupting a PC-based broadcast.
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
Do I need a capture card to show a speedrun timer?
No. The timer is software and can be added to an OBS scene as a window or, where supported, a browser overlay. A capture card may be relevant if you need to route console gameplay into the PC running OBS, not for the timer itself.
Can I use a browser source with any timer?
No. Browser overlays are specific to timers or companion tools that support them, and setup can require extra configuration. Check the chosen project's current documentation; if it does not provide a compatible overlay, window capture is a practical alternative.
Should I use automatic splits?
Only if the game and category have a supported, suitable splitter and its behaviour matches the timing rules you intend to follow. Otherwise, configure manual splits and practise advancing them. Confirm the rules for your category rather than relying on a timer default.
How can I tell whether viewers will be able to read the timer?
Record a short test and watch it at the size your audience is likely to see, including on a smaller screen if relevant. Check the digits and split labels during moving gameplay, not only in a static preview, and move or resize the source if it obscures useful information.