How to add NuzPoke to OBS

Before OBS

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 URL inside that arrangement: the link is locked and keeps that layout even if you later select another one in the panel.

Check the link

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.

Individual arrangement selector with four layout URLs — Each button copies a URL locked to its arrangement.

Setup

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.

Composition

Choose a full canvas or a fitted source

Full canvas

Use your OBS base resolution—such as 1920 × 1080—and place the team with NuzPoke alignment. This makes changing corners easy.

Fitted area

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.

Several scenes

Reuse the existing source instead of creating a fresh copy. This reduces active browser instances and preserves state.

Continuity

Keep the page active between scenes

To keep NuzPoke listening and avoid replaying its load when you return, leave these options off:

Shutdown source when not visibleOff. When enabled, OBS unloads the page when hidden.

Refresh browser when scene becomes activeOff. Live changes arrive without a scene-change reload.

Use Refresh cache of current page only as a recovery step if the source stops or after replacing its URL.

Performance

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.

Realistic test

Do not judge performance in an empty scene. Recreate the heaviest broadcast situation and update the team while OBS records.

Diagnosis

If something is missing or not updating

The source is emptyOpen the URL in a browser, confirm the run has a team and check the full link was copied.

The background is blackReset the source properties and check that no background or filter was added.

Changes do not arriveVerify admin and stream belong to the same run, then refresh the cache once.

The team is clippedIncrease width or height, reset cropping and review spacing.

Resource use is highUse 30 FPS, reduce dimensions, reuse the source and try static sprites.

Entrances replay on scene changeTurn off automatic refresh when the scene becomes active.

Final check

With OBS open, add, reorder and remove a member. If all three arrive without a reload, the source is ready.

Starting values

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.

1920 × 1080Use the full canvas and position the block with NuzPoke alignment. This is the most flexible setup.

1280 × 720Suitable for 720p output; check names and types at the real output size.

Horizontal stripStart at 1920 × 300 for 6×1 and adjust height for names, types and spacing.

Side columnStart at 360 × 1080 for 1×6 and increase width if nicknames are clipped.

Corner blockTry 720 × 520 for 3×2 or 520 × 720 for 2×3 and validate over the actual game.

These are starting points, not required dimensions. Always inspect the output resolution and a small screen because the editor preview can hide readability problems.

Next guideNuzPoke layouts and animations