Overlay packs have a completion problem. The download happens, the zip gets unpacked, and then the instructions say to add a source per element — and somewhere around the fourth one it stops being worth the evening. Most packs people buy end up partly installed or not installed at all. This is a different route: rather than reproducing the pack’s structure in your scene list, you upload the pieces you actually use and put them on keys. The pack stops being a folder and becomes a deck page.
Rather than adding a source per file, upload the pack’s pieces to Kloot’s Media tool and pin each one to a deck key. Alerts and stingers fire once; frames and plates hold until you toggle them off. Everything plays through one Kloot browser source. A full pack needs Creator ($15/mo) for its 50-item allowance.
You set it up here
It lands here — fired by hand
What you’ll build
The pieces of your overlay pack you actually use, each on its own deck key, running through the single browser source already in your scene.
Before uploading anything, split the files by how they behave. Things that play once and clear — stingers, alerts, celebration animations — are Fire items. Things that stay on screen — webcam frames, panel plates, chat backdrops, starting-soon art — are Hold items. That single distinction determines every setting later, and it is faster to decide it once over a folder than file by file.
Be ruthless about the third pile: pieces you will never actually press. A pack of forty rarely has more than eight you use weekly, and item counts are finite.
Paste your Kloot overlay URL into one Browser source, sized to your canvas. This is the part that replaces the pack’s own install instructions — every piece you upload plays through this one source, so there is no source-per-element step and no scene list to maintain. It does not reduce sources you already have for other software; it just does not add any.
Drag several files in at once. Each is probed in your browser before it uploads, so a file with the wrong format or an unexpected length flags immediately rather than after the transfer. WEBM and MP4 go straight through; a .MOV is converted server-side into alpha-preserving WEBM, which takes a minute or two per file and is a Creator feature. Storage is a flat 500 MB on every plan.
Upload the .MOV files first and let them convert while you set up the ones that went straight through. The queue is not blocking.
Open each piece and look at the preview. Kloot renders it on a checkerboard for a reason: on a solid backdrop a genuinely transparent file and a broken export look identical, and a pack assembled from mixed sources often contains both. Catching a grey box here costs ten seconds; catching it live costs a moment.
Fire items need a position and, if you want to override the clip’s own length, a duration up to 30 seconds. Hold items need a position and a scale, and a layer — behind your widgets or in front. Everything is stored against the 1920×1080 canvas, so a pack laid out once lands identically every stream.
Pin the pieces to one deck page so the whole pack is one screen. Each key wears its own artwork and video keys play their thumbnail, which is what makes a page of eight similar alerts usable — you find them by motion rather than by reading labels. That page is on your phone too, so the pack is reachable without alt-tabbing.
Upload once, then it is one press. Here is the whole loop — what you do, what the overlay shows, and what your viewers actually see.
Drag a folder of alerts, frames and sounds into the Media tool. Each file is probed in your browser first for length, dimensions and whether it actually carries transparency, so anything that will not work says so before it uploads rather than halfway through.
WEBM and MP4 go straight through. A QuickTime .MOV is converted server-side to alpha-preserving VP9, which takes a minute or two — the item shows as processing and cannot be fired until it is ready, rather than pretending and failing on stream. Conversion is a Creator feature.
Pin the item to a key. The key takes the clip’s own artwork rather than a generic glyph, and video keys play their thumbnail — because a stinger’s opening frame is often nearly empty, and two alerts from one designer’s pack routinely share it. You recognise your own clips by motion.
A Fire item plays once and hides itself. A Hold item stays up until you press again, looping if it has anything to loop. Nothing triggers on its own — there is no chat integration and no event listener anywhere in Kloot, so a clip only ever goes out because you pressed something.
A Fire item ends on its own. A held frame waits for the same key again. If a clip’s decoder ever dies mid-playback the renderer hides it rather than leaving the last frame frozen on your stream — the switch stays reading ON, which is honest about what actually failed.
Every other tool draws something Kloot designed. This is the one that draws what you brought:
When: A folder of alerts, stingers and frames is sitting on your drive because there was never anywhere to put them.
Why it works: The work is done and the money is spent. Media is the part that was missing — a place to put the files and a key to fire them from.
When: Your channel has a look, and the effects on your deck do not share it.
Why it works: Generic effects read as generic. Firing something a viewer recognises as yours is a different signal entirely, and it costs one upload.
When: You have a PNG frame that fits your layout better than any template.
Why it works: Held media takes your own file at your own position and size, and stays up all stream. No template to compromise with.
When: An overlay pack downloaded, unzipped, and abandoned because wiring it into OBS meant a source per file.
Why it works: Upload the files, pin the ones you use, ignore the rest. The pack becomes a deck page instead of a folder.
A clip you fire, a frame you hold, a still you put up. Every preview below sits on the same checkerboard the panel uses, so transparency reads as transparency.
The stinger, the alert, the celebration — one press, then gone.
A sub lands, you press the key, your designer’s animation plays over the game and clears itself. Fire clips may play for up to 30 seconds; past that a clip is a scene rather than an effect, and Kloot points you at Hold instead.
Momentary key — press, it playsThe webcam border or overlay plate that stays up all session.
Your own transparent PNG at your own position and size, holding a corner until you toggle it off. Video holds loop rather than freezing on their last frame, so an ambient background actually stays ambient.
Switch — press on, press offYour logo
A logo, a rules card, a sponsor plate, a QR you drew yourself.
Images cost nothing to hold and are exempt from the two-video concurrency limit, so a still can sit on screen alongside whatever else you are firing.
Switch — up until you clear itA held frame sits behind your widgets and holds its corner; a fired clip takes the front layer for as long as it plays. Both ride the one browser source you already added.
No. Every piece plays through the one Kloot overlay URL, which is the main practical difference from the install instructions most packs ship with. To be precise: Kloot does not reduce your existing source count either — it just does not add one per element.
Two on Free, 50 on Creator ($15/mo), and 200 on Pro ($25/mo). A pack is why Creator exists — two items is a taste, not an install. Storage is a flat 500 MB on every plan.
Yes. Kloot converts a .MOV to alpha-preserving WEBM for you, reading the transparency off the decoder rather than trusting what the container claims. Conversion is a Creator feature, and it takes a minute or two per file.
Those are rejected with a note telling you what to export instead — .PSD, .AEP and similar are project files, not something a browser can render. Export the finished piece as PNG, WEBM or MP4 first.
That depends on your licence with the designer, and it is worth reading. Kloot plays the file you upload and makes no claim about your right to use it — you are asked to confirm you have that right when you upload.
Yes, because nothing re-animates them. Kloot has no motion presets, no entrance animation and no tint to layer on top — the creator baked the motion into the file, and adding a second animation system over it is the specific failure this tool avoids.
Upload the pieces you actually press, pin them to one deck page, and fire them from the browser source already in your scene. Creator’s 50 items is where a pack fits.
See plansFree plan (2 items) · Creator $15/mo (50) · Pro $25/mo (200)