Overlays and elements

Elements are StreamChum's overlays: chat, alerts, countdowns, and custom widgets. Group them into a themed collection, brand the set, then drop each URL into Studio or OBS as a browser source. Browse free packs or build your own.

Three kinds

• Chat: unified chat overlay with look settings (font, outline, stack, animation) and feed filters (hide ! commands, bots, your own messages, first-time vs regular). Twitch GIFs from chat render next to emotes on this overlay and in Live Center. YouTube and Kick do not send GIFs this way.
• Dynamic: multi-scene alerts for subs, raids, Ko-fi, hype trains, with merge tags in one source. Incoming Twitch raids can play a public clip from the raider's channel; if they have none, the overlay still shows name and viewer count.
• Custom: describe a widget in Element Builder, preview it, paste the URL. Builder turns spend creative AI credits on a paid plan. First builds and restyles get a look at the overlay before it is treated as finished. A restyle rewrites look and motion and keeps behavior. Ask the builder for live captions and the widget listens for caption packets from a transcribed Studio mic. Ask for chat or chat lines on a custom widget (hangman, floating bubbles, on-screen lines) and it can listen for filtered chat (not a second live chat feed). Ask for a 2D pixel character that walks, waves, or shoots and Element Builder mints named sprite sheets and plays them in the overlay (it does not fake a walk by sliding a still PNG).

Each element has its own overlay URL. The app does not show that URL until you reveal it. Treat it like a password. If you enable voice or Memory write on a source, StreamChum rotates the token: paste the new URL into Studio or OBS.

A themed collection can also keep Studio scenes (Intro, Playing, BRB). After you lock the look, the collection page shows the generated theme so you can refine it. Build a starter show can then generate those scenes and matching overlays onto the pack (Intro, Playing, Chatting, and BRB by default). That spends Element Builder credits per overlay and runs in the background. Studio pauses scene editing and profile switches until the final generated layout loads; Chat stays available. You can skip it. Open Edit theme in Studio (cog next to a profile), then Save scenes to pack, to write the current profile's layouts onto the pack. Overlay placement comes along. Camera, game, and window captures become empty slots. Reusing that pack on a new profile, or installing it from the marketplace, seeds those scenes. Open a published pack on the free stream elements site to see those scenes laid out. Pick devices in Element Settings on that PC. OBS still gets the pack as browser sources; it does not get those scene layouts yet. Event-element scenes (sub and raid alert states in the web editor) are a different thing.

Do not put overlay URLs in public scene collections you share. Anyone with the URL can display that overlay.