Arrange your whole overlay in the browser — hunt tracker, chat, alerts, leaderboards, cam cutouts — then add it to OBS as a single browser source. Change it mid-stream and the overlay updates without you touching your scene.
18+ · Play responsibly.
What goes on a layout
Setup
Create a free account and open the stream layout editor. You start on an empty 1920×1080 canvas that matches your OBS scene exactly.
Drag widgets onto the canvas — hunt tracker, chat, alerts, leaderboard — then resize and snap them into place. Cam and gameplay cutouts punch real transparent holes so your capture sits behind the layout.
Set a background, an accent colour and a font, and every widget on the layout picks them up. Individual widgets can opt out where they need to differ.
Copy the layout's browser-source URL and add it as a single Browser source at 1920×1080. Any change you make afterwards appears on stream without touching OBS again.
Per platform
The layout itself is identical everywhere — it is a browser source, so Twitch, Kick and YouTube never see it as anything but part of your video. What differs is where the widgets read their data from, and a couple of setup details per broadcast tool.
FAQ
The arrangement of everything on screen that isn't your gameplay or camera — overlays, chat, alerts, trackers, borders and backgrounds. A layout is that whole arrangement saved as one thing, rather than a pile of separate sources you position by hand.
Yes. The editor, every widget and the resulting overlay are free, with no credit card and no watermark on paid tiers because there are no paid tiers.
Yes, and identically — the layout is a browser source in OBS or Streamlabs, so the streaming platform never sees it as anything special. What differs per platform is the data behind the widgets: chat, follows and subs are read from whichever channels you connect.
No. You place widgets on a canvas and set one accent colour and font that everything inherits. If you do want finer control, the editor accepts custom CSS.
One. The whole layout compiles to a single browser-source URL, which is the main practical reason to use one — a scene with fifteen separate sources is slow to edit and easy to knock out of alignment.
A browser source costs some CPU, but one source rendering everything is cheaper than a dozen each running their own page. Turn on hardware acceleration for browser sources in OBS and enable “Shutdown source when not visible” on scenes that don't use it.