How to Make Twitch Alerts in 2026 — The Complete Guide

Your Twitch alerts are the first thing new followers experience. Generic default alerts blend in with every other channel running the same widget platform. Custom alerts make your stream feel intentional — and a well-timed animation on a subscribe or a raid is often the moment that turns a one-time viewer into a regular.

This guide covers every practical way to get there in 2026: what each method actually costs, how long it takes, how to wire the result into OBS, which alert types deserve the most attention, and how to fix the two problems that break almost every new alert setup — it not showing up, and its background not being transparent.

The Four Ways to Make Twitch Alerts

Every option below solves the same problem — get an animated graphic to fire over your gameplay when an event happens — but they trade off cost, time, and how unique the result looks.

1. Template Packs

Sites like OWN3D, Nerd or Die, and the Streamlabs Store sell (or give away) pre-designed alert packs: a matched set of follow/sub/raid/donation animations, usually themed. You browse a catalogue, buy or activate a pack, then import or link it into your alert widget.

Cost: Streamlabs Store themes run free to around $30 per pack as one-time purchases. OWN3D Pro is a subscription — pricing fluctuates with promotions but typically lands around $8–12/month (roughly $90/year), covering most of the library; individual packs can also be bought a la carte. Nerd or Die runs a similar free-plus-paid model.

Time: 10–30 minutes from picking a pack to seeing it fire on stream, most of which is import and configuration, not decision-making.

The catch: you're choosing from a shared catalogue. The same pack you activate is available, unchanged, to every other subscriber. Quality is generally high — OWN3D's flagship packs in particular are professionally produced — but the design was made in advance, for everyone, not for your channel specifically.

2. Your Widget Platform's Built-In Customization

Both Streamlabs and StreamElements let you reskin their default alert box for free: swap colors and fonts, adjust timing, upload a custom sound. StreamElements goes a step further and accepts custom HTML/CSS plus uploaded video files as alert media, and its browser-based overlay builder lets you assemble alerts, a donation ticker, and a chat box into one hosted URL.

Cost: Free. This is the zero-dollar option.

Time: 5–15 minutes to get something live.

The catch: you're still working within a pre-built template's structure — you're changing colors on someone else's animation, not creating a new one. Experienced viewers recognize the stock Streamlabs and StreamElements alert boxes on sight.

3. Commission a Designer

You can hire a motion designer on Fiverr, Upwork, or a similar freelance marketplace, or build alerts yourself in After Effects if you have the skills.

Cost: Highly variable. A single simple alert commission commonly starts around $50; a full themed pack (follow, sub, raid, donation, plus a matching overlay) from an experienced designer can run past $300. DIY in After Effects costs your time instead of money, but expect a real learning curve if you haven't used motion graphics software before.

Time: Freelance turnaround is typically days to weeks, not minutes — and revisions add more rounds. DIY can take anywhere from an evening to many weekends depending on skill level.

The catch: you get full creative control and a genuinely unique result, but this is the slowest and least predictable method on this list. It's the right call if you have a specific, detailed vision and can wait for it.

4. AI Generation

Tools like [AlertForge](/twitch-alerts) generate the animation itself from a text prompt — you describe the alert ("a glowing portal erupts, particles scatter, fades cleanly") and the AI renders a new transparent video that didn't exist before, rather than picking from a catalogue or reskinning a template.

Cost: Credit-based subscriptions from [$15/month for 240 credits](/pricing) up to $129/month for 1,800 credits, or one-time credit packs starting at $5 for 30 credits if you just want to try it. There's no free tier.

Time: Each render takes a few minutes; most people generate a handful of variations before landing on the one they want, so budget 15–30 minutes for a full alert set including review.

The catch: generation has some variance — you may need two or three attempts to get the motion behavior you described, and it costs more than a template pack if you're only setting alerts up once and never touching them again.

Cost and Time Comparison

| Method | Typical Cost | Setup Time | You Own the File? | |---|---|---|---| | Template pack (OWN3D, Nerd or Die, Streamlabs Store) | Free–$30/pack; OWN3D Pro ~$8–12/mo (~$90/yr) | 10–30 min | Yes after purchase (OWN3D); varies elsewhere | | Built-in widget customization | Free | 5–15 min | No — platform-locked | | Freelance designer / DIY | Roughly $50–$300+ per pack (freelance); time cost only if DIY | Days to weeks (freelance) | Yes | | AI generation (AlertForge) | $15–$129/mo, or $5–$35 one-time packs | 15–30 min incl. iteration | Yes |

Setting Up Your Alert in OBS

Whichever method you used, getting the result into OBS Studio comes down to one source type: Browser Source, pointed at your widget's overlay URL.

1. Open OBS and select the scene where alerts should appear. 2. Under Sources, click + and choose Browser. 3. Name it something like "Twitch Alerts" and click OK. 4. Paste your overlay URL into the URL field. 5. Set Width to 1920 and Height to 1080 to match a standard 1080p canvas. 6. Leave the default transparent-background Custom CSS in place — don't delete it. 7. Click OK, then drag the source above your game and webcam captures in the Sources list so alerts render on top of everything else. 8. Fire a test alert from your widget's dashboard to confirm it triggers and the background stays transparent.

That covers the hosted-overlay-URL path. If you're working with downloaded WebM files instead — via Media Source, or importing into Streamlabs/StreamElements as custom alert media — the exact field values and file-path formatting differ. See the full [AlertForge OBS setup guide](/blog/alertforge-obs-setup) for both methods, step by step.

Alert Types That Matter

Not every alert deserves the same effort. Here's what makes each type work.

Follow alerts fire the most often on most channels, so keep them short and let repetition build recognition instead of trying to make every single one a spectacle. AlertForge's own render data shows the average AI-generated alert clip settles around [8 seconds](/blog/stream-alert-statistics-2026) — long enough for an entrance, a hold, and an exit, short enough to not sit over gameplay too long. That's a reasonable target for any alert type, follows included.

Subscriber alerts are rarer and mean more, both to you and the subscriber — this is where a slightly longer, more celebratory animation earns its keep. If your sub alerts and your follow alerts look identical, you're wasting the moment.

Raid alerts need to work as a first impression for a wall of new viewers arriving at once. Prioritize legibility — the raiding channel's name and a clear welcome moment matter more than an elaborate animation the incoming viewers won't stick around long enough to appreciate on a second watch.

Donation and tip alerts get clipped and shared more than any other alert type, so the amount and message need to be readable at a glance, not buried in motion. If you want viewers to be able to trigger a custom alert directly with a tip rather than just seeing a generic "thank you," [Viewer Alerts](/viewer-alerts) lets a $5+ Stripe Checkout payment fire a custom AI-generated animation live on your overlay — a different mechanic from a standard donation notification.

Troubleshooting

The alert isn't showing up

Check these in order: the Browser Source URL is correct and complete; your streaming platform connection (Twitch/YouTube/Kick) is active in your widget dashboard; the source isn't hidden behind another source or toggled off in the Sources list; and if you're using a local Media Source file, that Loop and Restart playback are configured the way you expect. Most "nothing happens" reports come down to one of these four.

The background isn't transparent (green box, black box, or fringing)

This is almost always a format or filter problem, not a bug in your widget. The short version: transparent alerts need to be VP9-encoded WebM files, and any leftover Chroma Key or Color Key filter on the source will interfere with native alpha. For the full diagnostic checklist — including exact ffprobe commands to verify the codec and fixes for each specific symptom — see [Transparent WebM Alerts for OBS: The Complete Guide](/blog/transparent-webm-alerts-obs-2026).

FAQ

Do I need OBS to make Twitch alerts work? OBS Studio (or an OBS-based client like Streamlabs Desktop) covers the vast majority of setups, since Browser Source is the standard way every alert widget — Streamlabs, StreamElements, or a hosted overlay URL — gets displayed on stream. StreamElements also has an OBS.Live extension that embeds its dashboard directly inside OBS.

How long should a Twitch alert be? Four to eight seconds is the practical range for most alert types. Longer and you risk covering gameplay or chat during an active moment; shorter and the animation doesn't have time to read. AI-rendered alerts across AlertForge's dataset average [8 seconds](/blog/stream-alert-statistics-2026).

Can I use the same alerts on YouTube and Kick, not just Twitch? Yes — a transparent WebM file or a Browser Source overlay URL isn't platform-specific. The alert itself doesn't know or care which platform triggered it; that routing happens in your widget (Streamlabs, StreamElements) or your overlay tool, not in the alert file.