Landmark DocsDashboard →

ON STREAM

Elements & overlays

Everything that shows up on your stream (alert pop-ups, the chat box, a goal bar, a subathon timer) is an element. You build and style an element once, then use it on an overlay next to other elements, or on its own as one OBS browser source. Edits to an element show up everywhere it is used.

Two kinds of element

Alerts: one-shot, fired by a trigger
An alert plays once when something happens: someone follows, subscribes, sends a gift, cheers bits, raids or tips. It animates in, holds for a few seconds, then closes. The starter alerts are New follow, New subscriber, Gift received, Tip ($5+), Cheer (bits), Raid and New Landmark member (someone joined Landmark through your referral link). There is also a catch-all When anyone does anything and a Speech (read aloud) element, both off until you turn them on. Several alerts can show at once: stacking is a setting on the alert, and stacked alerts share the slot as a cluster instead of waiting in line. You choose which way the cluster grows and how many show.
Widgets: on screen the whole stream, react to the live feed
A widget stays up for the whole stream and updates as events arrive. The built-in ones include the Chat box, Goal bar, Counter, Timer, Prize wheel, Confetti, Skills menu, Media share, Soundboard, Poll, Giveaway, Schedule, Landmark Camera status, Live captions and Screen FX (which needs Landmark Desktop running). The Elements catalog has the full list. Goals, counters and timers are meters: the server counts for them, so the dock, chat commands and rules all drive the same number you see on stream. Widgets have no Triggers section. You set them up with their own settings (max messages, goal target, seconds per sub and so on).

Your starter elements are added the first time you open Elements. Older accounts get newly added starters on their next visit.

Triggers: when an alert fires

Each alert has one or more triggers. A trigger reads like a sentence (“When someone on some platform does something”) and any trigger that matches fires the alert.

  • Platform. Pick Any platform or Specific. Any platform matches the same event across Twitch, YouTube, Kick, Rumble and TikTok. Specific narrows it to one.
  • Event. Follow, subscribe, gift, cheer, tip or Super Chat, raid, redemption, like, or a new Landmark member. The list only offers what the chosen platform sends. For example, Kick has no Super Chat (Kicks arrive as named gifts), and Twitch is the only platform that sends raids.
  • Landmark tips. A tip on your tip page is a cash tip. It shows up as the event super chat on the platform Landmark. A tip paid with coins is the event tip on the platform Portal. A rule matches one platform and one event exactly, so an alert for “when someone tips” carries both rules. The Tip ($5+) starter covers both, and the AI assistant sets up the pair for you. A coin tip counts at one cent per coin, so a $5 floor means 500 coins.

Once you pick an event, more fields appear so the alert fires only on what you want:

Amount
A floor on tips, Super Chats, cheers and gifts: a dollar amount (tips of $5+) or a count (1,000 bits, 100 Kicks). Choose how it compares: at least (the default), exactly or more than. Add several triggers on the same event with different floors to run small, medium and huge versions.
Tier
For Twitch subs and gift subs, a minimum tier (Tier 1+, 2+ or 3). Twitch reports Prime subs as Tier 1. YouTube member levels are names, not ranks, so tier is not offered there.
Gift kind and specific gift
On Kick you can split gift subs from paid gifts. On Kick and TikTok you can pin the trigger to one gift from the catalog.
Reward
For redemptions, pick Specific reward to fire on one reward only. The list has your Twitch channel point rewards and your Landmark Skills (MineControl effects, Screen FX, sounds and more). A Landmark Skill matches however it was set off: coins, a tip, bits, a gift or the dock.

Skill sound alerts

To play a sound when one of your Skills fires, add the Skill sound alert from Elements, pick the Skill under its trigger, and swap in your own sound under Media. It shows a small card with who redeemed it. The sound control on a MineControl Skill opens this alert with that Skill already picked.

Every alert that is in use and matches the event fires, each in its own slot. Priority decides the order when one alert has several matching triggers. The catch-all “When anyone does anything” matches every viewer action, so once you turn it on and use it, it plays next to your other alerts. Leave it off unless you want that.

Editing an element

Open any element from Elements to land in the editor: a live preview on the left that replays on every change, and sections on the right.

  • Style: accent color, entrance animation and on-screen time, plus the element's own settings, grouped under small headings. Settings can be colors, sliders, numbers, text, picks, toggles, platforms, or a list of rows you add, remove and drag into order (a milestone ladder, a prize list).
  • Text: a headline and subtitle, with variable chips like {user}, {amount} and {gift_name} filled in from the real event.
  • Voice: optional text to speech that reads the event aloud on the overlay. Off by default. Test voice plays it for you.
  • Media, Variables and Recent fires: attach a sound or image, see the values an element saves for itself, and review the last events that fired it. Goals, counters and timers keep their totals per placement, so they show a Current total section instead of Variables.

Test fire at the top plays the element in the preview and on any open OBS overlay at the same time, so you can check it before going live.

Where an element is used

The bar at the top of the editor says where the element shows, for example Used on Main overlay and its own OBS source. Edits update it everywhere it is used.

  • Not used yet. The bar offers Add to an overlay and Use on its own. The library has the same two buttons on each card, and the Not used yet filter lists every element you made that is not showing anywhere.
  • Use on its own copies a browser source URL that shows only this element. Paste it into OBS as its own source. It is the same link as ⋯ More → Copy OBS source. You need no overlay for it.
  • Add to an overlay places it on one of your overlays. Then use Position it in Overlays to move and size it.

Composing onto an overlay

An overlay is a 1920×1080 canvas you arrange elements on, and OBS shows it with one URL. A new overlay comes with your starter alert slots. Add widgets yourself. Changes on the canvas only change that placement (position, size, layer and its settings), never the base element.

  1. Go to Overlays and pick or create an overlay.
  2. Press + Add element and pick an alert or a widget.
  3. Drag to move and pull the corners to resize. Each element shows a live preview, so the canvas is what OBS will show.
  4. Select an element to open its panel. Settings (this overlay) changes its settings for this placement only, and Edit base element → opens the element itself. Use ▶ Test event to watch it react.
  5. Press Copy URL for the whole overlay, or Copy element URL to give one placement its own browser source, and paste it into OBS.

Sharing an element

  • ⋯ More → Share link publishes a link anyone can open. The page shows a live preview, the code, and Add to my account. Updating your element and sharing again keeps the same link.
  • ⋯ More → Export JSON downloads the element as a file. On Elements, Import takes a file or pasted JSON.
  • A shared or imported element lands in your library as your own copy. It is never placed on an overlay until you choose to use it.

Generate with AI

Generate with AI in Elements, and the assistant panel inside the editor, build or change an element from a plain description. It writes the look, the settings, the triggers and the code, and shows the result live so you can apply it with one press or ask for a change.

  • Model choice. Pick Best, Balanced or Fast in the panel. Your pick is saved and used next time.
  • It shows its progress. While it writes, the panel says it is building and then checking the element. Nothing changes until you apply it.
  • It only uses what exists. It uses the events and data in the window.landmark API, sets up both rules for a tip alert, uses list settings for anything repeatable, and points you to a built-in element when one already does the job.
  • Readable code. The code it writes is laid out on separate lines with a comment on each part, so you can read and change it.
  • It shows it working. For a widget that reacts to the live feed it fires a sample event into the preview. For a widget driven by a chat command it makes the command too.
  • Needs upgrade. A chip on an element built before the current system opens the assistant with an upgrade request. It keeps the look and the settings the same and only changes the wiring, so your totals carry over.

Starters are locked: duplicate to change the code

You can rename, restyle, retarget and tune the starter elements, but their HTML, CSS and JS are read only. Press Duplicate to customize in the editor for your own copy with everything editable. The original stays as it was. Starters cannot be deleted, only turned off.

Any element is just code

Every built-in, the chat box and wheel included, is code that runs in a sandboxed frame against the window.landmark runtime. So you, or the AI assistant, can build anything the starters do not cover: a leaderboard, a plinko board, a custom celebration. Open Custom code on your own element to edit its HTML, CSS and JS, plus a Properties panel for its settings. The code has no network access, so live data reaches it as events.

// A widget. Follow the chat feed:
landmark.on("chat", (e) => {
  const p = e.payload || {};
  addLine(p.user, p.text);
});

// An alert. Read the event that fired it:
const name = landmark.event.payload.user;

// A Landmark tip is two events, coin tips and cash tips:
landmark.on("tip", addTip);
landmark.on("superchat", (e) => { if (e.platform === "landmark") addTip(e); });

// Read a setting tuned in the editor:
const max = landmark.config.max_messages;

// Keep a count across OBS reloads:
await landmark.vars.set("count", n);

Every member of window.landmark, every event type with its payload, the settings controls (list included) and the limits are in the window.landmark API reference. The Docs → link under Custom code opens it.

In OBS

  • The background is always transparent, so elements sit on top of your scene. Do not set a background color on the browser source.
  • Some feeds belong to a built-in element. A custom element cannot read the Landmark Camera status, Poll, Giveaway, Schedule, Profit or Skills feeds unless that built-in is placed on the same overlay. Use the built-in for those.
  • Reloading the source loses nothing that matters. Goals, counters and timers come back from the server, and custom elements restore what they saved with landmark.vars.
  • An element on its own source is scaled to fill it. Give the source the same shape as the element's box so nothing is letterboxed.

Next: add your overlay to OBS as a browser source →

Last updated · October 19, 2026

Elements & overlays · Landmark