Finish the layout and copy the stream URL
Open the run, select Stream and adjust at least arrangement, alignment, names, types and background. The header Copy URL button copies the general view. If OBS must keep a specific layout, use Copy pinned URL inside that arrangement: the link is locked and keeps that layout even if you later select another one in the panel.
It must be the layout view URL, never the admin URL. Paste it into a private browser window first: if you can only see the team and cannot edit, it is correct.
Create a Browser Source
- Select the scene where the team will appear.
- Under Sources, select + and choose Browser Source.
- Create a new source and give it a clear name, such as NuzPoke · Team.
- Leave Local file off and paste the URL.
- Enter the width and height of the area you want to use.
- Confirm and position the source on the OBS canvas.
NuzPoke already has a transparent page background. You do not need chroma key, color cropping or custom CSS.
Choose a full canvas or a fitted source
Use your OBS base resolution—such as 1920 × 1080—and place the team with NuzPoke alignment. This makes changing corners easy.
Reduce width and height to the team area and position it in OBS. It uses fewer resources but leaves less room to change alignment.
Avoid scaling a tiny source until it becomes huge. Give it sensible width and height, transform it, and hold Alt while dragging an edge if you need to crop.
Reuse the existing source instead of creating a fresh copy. This reduces active browser instances and preserves state.
Keep the page active between scenes
To keep NuzPoke listening and avoid replaying its load when you return, leave these options off:
Use Refresh cache of current page only as a recovery step if the source stops or after replacing its URL.
The event connection attempts to recover after an interruption and receives the saved state again. After a resource update, the overlay may reload on the next real game change. Deployment or reconnection alone does not guarantee an immediate reload.
Start at 30 FPS with one source
Thirty frames per second is usually enough. Use 60 FPS when motion is central to the design and OBS stays smooth during a demanding scene.
- Reuse the source across scenes.
- Do not use width or height greater than the output canvas.
- Use a static style or turn off Animate sprites to save resources.
- Reduce width and height when the overlay only occupies a small area.
- Check the result with the game, alerts and camera active together.
Do not judge performance in an empty scene. Recreate the heaviest broadcast situation and update the team while OBS records.
If something is missing or not updating
With OBS open, add, reorder and remove a member. If all three arrive without a reload, the source is ready.
If another tab disconnected editing, select Carry on here before repeating the test. If everything updates except the arrangement, check whether OBS uses a pinned URL: that link keeps its layout when you select another one in the panel.
Recommended resolutions and sizes
The Browser Source does not have to match the captured game resolution, but it should match the space it will occupy on the OBS canvas.
These are starting points, not required dimensions. Always inspect the output resolution and a small screen because the editor preview can hide readability problems.