Twitch Clip Alert: How to Get Notified When Someone Clips Your Stream (2026 Guide)

By Paul d'Anjou, Twitch growth expert June 14, 2026

TLDR

• Twitch does NOT send a native clip notification when a viewer clips your stream, as of June 2026.
• The Creator Dashboard Activity Feed lists clips after the fact, with no push, email, or mobile alert.
• Four working paths cover 100% of streamer use cases: overlay alert (Streamlabs, StreamElements, Sound Alerts, Lumia), Discord bot with webhook, Helix API polling for devs, externalized workflow pipeline like Snowball, the app I'm building for this clipper workflow.

Verdict in 30 seconds

If you stream solo, set up a Streamlabs or Sound Alerts overlay clip alert in 4 clicks, visible during your live. If you run a community Discord or a clipper team, plug in a Discord bot like Wizebot or a Make.com scenario that pushes each clip to a dedicated channel. If you code, polling the GET /helix/clips Helix route every 60 seconds feeds any webhook you want. And if your clips come from an externalized clipper team, the workflow pipeline (Snowball, the solution I built for this exact case) is what matters, not unit alerts.

The comparison table at the bottom of the page summarizes cost, latency, and target profile per method. The sections that follow detail the exact path.

Why Twitch doesn't notify clips natively

A 2024 r/Twitch thread (Notification for attempted clips) crystallizes the problem. A streamer asks: "Is there a way to get an alert when someone clips my stream?" Every reply confirms the same thing. Twitch pushes no notification.

Activity Feed vs push notification

The Twitch Creator Dashboard exposes an Activity Feed that lists recent events: follows, subs, raids, cheers. Viewer-created clips show up there too, but as a history row, with no pop-up, no sound, no mobile push. You can open the Dashboard and see "X clipped your stream" 3 days later. Too late to ride the viral window.

Auto Clips Alpha is not a notification

The official Twitch Auto Clips documentation clarifies a nuance that traps half the competing articles. Auto Clips Alpha is an auto-creation feature: Twitch creates the clip for you when chat activity spikes. But Twitch doesn't notify you that the clip was created. Neither Auto Clips nor manual viewer clips fire a push alert. Confusing the two leads to recommending Auto Clips as a notification solution, which is wrong.

Documented pain on the streamer side

Beyond the Reddit thread, the Lumia Stream community has maintained a clip alert tutorial via webhook since 2022, a sign that the need is recurring. Until Twitch ships a native channel.clip.create EventSub event, the workaround goes through third-party tools or homemade code.

Method 1: Real-time overlay alert (Streamlabs, StreamElements, Sound Alerts, Lumia)

The fastest and most visible path during the live. The alert pops on your scene (and on your OBS canvas), with sound and animation, the moment a viewer clips.

Streamlabs (4 clicks, free)

1. Open Streamlabs Dashboard.
2. Go to Alert Box, click Add Widget, then Twitch Clips.
3. Enable the Clip Created sub-event.
4. Copy the widget URL and add it in OBS as a Browser source.

Streamlabs supports sound and image customization. The free plan is enough for a solo streamer.

StreamElements (no-cost alternative)

StreamElements offers the same on the Streamer Dashboard, under Activity Feed Settings. The Clip Created event fires identically to Streamlabs, with HTML/CSS template control for power-users.

Sound Alerts (custom audio alert)

Sound Alerts is useful if you want to decouple the clip alert from a visual animation and tie it to a short sound (e.g., "clip incoming!" in your own voice). Twitch OAuth integration.

Lumia Stream (advanced webhook)

Lumia Stream lets you wire the clip alert to smart lights like Hue or Nanoleaf: your room flashes blue when someone clips. Niche use case but loved by IRL streamers.

Shared limitation

All 4 tools only work while you're streaming. If someone clips your VOD 4 hours after the live ends, no alert fires. That's the natural overlay boundary: they listen to your active OBS session.

Method 2: Discord notification via bot

To catch post-stream clips too and feed a community or clipper team, the Discord channel is the right surface.

Wizebot and Streamlabs Cloudbot

Wizebot exposes in its dashboard, under Modules Discord, a Send all clips to Discord automatically option. 5-minute setup: invite the bot, pick the target channel, activate the module. Streamlabs Cloudbot ships an equivalent on the Streamlabs side.

Direct Discord webhook via Zapier or Make.com

More flexible and independent from third-party bots. Make.com publishes a Share new Twitch clips on a Discord channel template that polls your Twitch account every 15 minutes and posts each new clip to the Discord webhook URL of your target channel. The Make.com free plan holds up to 1,000 operations per month.

Pick the right Discord channel

Three typical cases:

• A #raw-clips channel open to the whole community: maximum engagement, potential noise at high volume.
• A #mods-clips channel reserved for the mod team: quality triage before public relay.
• A private #team-clips channel for your clipper team if you have one: feeds their raw material queue.

For a deeper guide on the Discord layer alone, see the dedicated piece on auto-posting your Twitch clips to Discord.

Method 3: Helix API polling for devs

If you code (or have a dev on your team), full control goes through the Twitch Helix API. No native push event exists on clip creation as of June 2026: you poll the GET /helix/clips?broadcaster_id= route on an interval (60 seconds is enough), compare IDs against clips already seen, and push new ones to whichever webhook you want (Discord, Slack, Notion base, internal dashboard).

Minimal Node.js sample:

import fetch from 'node-fetch'

const broadcasterId = '123456789'
const seen = new Set()

async function pollClips() {
  const res = await fetch(
    'https://api.twitch.tv/helix/clips?broadcaster_id=' + broadcasterId + '&first=10',
    {
      headers: {
        'Client-Id': process.env.TWITCH_CLIENT_ID,
        Authorization: 'Bearer ' + process.env.TWITCH_APP_TOKEN,
      },
    },
  )
  const { data } = await res.json()
  for (const clip of data) {
    if (seen.has(clip.id)) continue
    seen.add(clip.id)
    await fetch(process.env.DISCORD_WEBHOOK, {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({
        content: 'New clip: ' + clip.title + ' by ' + clip.creator_name,
        embeds: [{ url: clip.url, image: { url: clip.thumbnail_url } }],
      }),
    })
  }
}

setInterval(pollClips, 60_000)

Hosting works on a 5 USD/month VPS, a Raspberry Pi at home, or a serverless function (Vercel, Cloudflare Workers). Target profile: streamer-dev, agency, or technical team that wants to route clips per game to different channels.

Method 4: Externalized workflow pipeline (clipper team)

If you already have 2 or 3 clippers producing your clips from VODs, the unit alert isn't the right tool anymore. What you want is to see every clip that ships (clippers and viewers combined) land in a shared editing table, with status, game, duration, ready-to-publish or queued.

That's the role of a dedicated workflow pipeline. Snowball, the platform that ingests Twitch clips and pushes them through a vertical editing table for streamer teams, picks up clips as they're created (by you, your viewers, your external clippers), pre-cuts them to 9:16 with auto-subtitles, and drops them into a TikTok / Shorts / Reels scheduling table. You stop getting 47 alerts a day; you open a table view, validate the queue, publish in batches.

Which streamer profile gets real ROI here? Typically the streamer who already externalizes 5 to 10 hours of editing per week, pays a video editor 200 to 300 USD per month, and wants to recover or divide that cost. The workflow pipeline doesn't replace the Streamlabs alert (useful during the live), it takes over the layer above.

Comparison table: 4 methods

To extend your clip stock beyond the live, also consider clipping from a Twitch VOD after the fact. And once the pipeline is fed, see the piece on repurposing Twitch clips to TikTok for the distribution layer.

Pick the method that fits your profile

• Solo streamer, under 10 avg viewers: Streamlabs Alert Box in 4 clicks, done. You need visibility during the live, not infra.
• Autonomous streamer, 50 to 500 viewers, active Discord: Wizebot or the Make.com template to Discord. You catch live AND post-stream clips, your community sees them, engagement restarts.
• Streamer-dev or agency: in-house Helix polling, per-game routing, Slack for the tech team, Discord for the community.
• Streamer with externalized clipper team: workflow pipeline like Snowball, the all-in-one tool for Twitch streamers and clipper teams, which surfaces clip arrival as a feed and powers the editing table. Unit alerts become secondary, the flow is what matters.

If you're new to the distribution layer, also see how to download your Twitch clips for workflows that need the source file.

Conclusion

Twitch does not natively notify clips on your stream, and probably won't anytime soon given how long the request has been open on the dev UserVoice. But 4 operational paths cover 100% of cases, from the 4-click overlay for the solo streamer to the workflow pipeline for the externalized clipper team.

Pick the method that fits your profile and set it up before your next stream. The worst option is letting clips pile up in the Creator Dashboard Clips tab and discovering them 3 days later when the context is dead.

FAQ

Are Twitch streamers notified when you clip?

No, not natively as of June 2026. Twitch sends no push, email, or in-app notification when a viewer clips your stream. The Creator Dashboard Activity Feed lists clips after the fact, with no real-time alert. Auto Clips Alpha auto-creates clips on chat spikes but does not notify the streamer either.

How do I set up a Twitch clip alert in Streamlabs?

Open Streamlabs Dashboard, go to Alert Box, click Add Widget, then choose Twitch Clips. Enable the Clip Created sub-event, customize the sound and animation, then add the widget URL in OBS via a Browser source. The alert fires on every new clip during your live stream.

Can the streamer see who clipped?

Yes. The Creator Dashboard Clips tab shows a Clipped By column with the viewer's username for each clip. The view is available after the fact, but no real-time alert is pushed during the live by default.

Can I get a Discord notification on every new clip?

Yes, via a bot like Streamlabs Cloudbot, Wizebot, or Sammi, or via a Zapier or Make.com scenario that polls the Twitch Helix API and posts the payload to a Discord webhook. This is the most common path for streamers with a mod team or clipper team.

Does Auto Clips Alpha notify the streamer?

No. Auto Clips Alpha auto-creates clips based on chat activity, but it sends no notification to the streamer. Clips appear in the Creator Dashboard Clips list with no push alert.

How many clips can be made on my stream without me knowing?

Unlimited if the Allow Viewers to Create Clips toggle is on in Creator Dashboard, Settings, Channel. There is no native rate limit on viewer-side clipping. If you set up none of the 4 methods in this guide, you'll discover clips the next day in the Clips tab.