Auto-post Twitch clips to Discord: 5 methods compared (2026)

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

TLDR

• Your community clips your best stream moments, but without an automatic relay, those clips die inside Twitch's Clips tab and nobody ever sees them again.
• Five methods exist in 2026 to push every Twitch clip into a Discord channel: turn-key bot, no-code workflow, or a custom webhook driven by your own backend.
• Once clips flow into Discord, the next obvious step is reformatting for TikTok and Shorts, which tools like Snowball, the platform that automates Twitch clips to TikTok, handle without an extra dashboard to open.

Verdict in 30 seconds

If you want something running within 30 minutes, pick Streamcord or ClipManager, invite the bot to your server, choose the target channel, done. If you want clips to also fan out to Slack, Notion or an Airtable, route through Make.com. If you want full control and accept 30 minutes of setup, a small Node.js script that polls the Twitch Helix API and POSTs to a Discord webhook gives you maximum freedom.

The comparison table near the end summarizes cost, complexity and latency by method. The sections below walk you through the exact setup for each.

Why automate Twitch clip sharing to Discord

When a viewer clips during your live, the clip lands inside your Twitch Clips tab. Nobody else gets notified. Your Discord community, the same people who spend their evenings talking about your stream, has zero chance of stumbling onto those clips unless you do the manual copy-paste work yourself.

The problem scales fast. A 4-hour stream can yield 10 to 15 clips. Multiply by three or four streams per week and you're looking at 30 minutes per session archiving links into Discord, or quitting. Most people quit.

Three use cases justify the automatic relay:

• Community engagement. Viewers re-post the clips, drop a reaction, kick off a discussion. The #clips channel becomes the running memory of your stream.
• Clipper archive. If you've stood up a Discord for your clippers, see the guide on setting up a Discord for your community, a raw #clips channel feeds them ready-made source material.
• TikTok pre-pipeline. Your best Discord clips become the candidates for vertical 9:16 reformatting toward TikTok, Reels and Shorts. The Discord channel acts as a first human filter before editing.

On the Twitch side, no native push event exists for clip creation as of June 2026. The official EventSub documentation lists no stable channel.clip.create event. The standard backend approach to detect a new clip remains regular polling of the Helix /clips endpoint. That's exactly why the bots and workflows below exist.

Method 1: Streamcord (easiest, free tier)

Streamcord is the most-deployed Discord bot for Twitch announcements. More than 700k servers use it according to the streamcord.io homepage. Automatic clip sharing ships in the free plan.

Exact path:

1. Go to streamcord.io and click Add to Discord.
2. Authorize the bot on your server (you need to be admin).
3. In your target channel, type /twitch clips subscribe [your-twitch-handle] (replace with your real handle).
4. Streamcord will now post every new clip from your channel into that Discord channel.

Pros: zero Twitch-side config, working in 2 minutes, no third-party account to create.

Cons: no keyword filter (every clip flows through), no batching (one message per clip), one Twitch account per server on the free tier. Past roughly 20 clips/day, the #clips channel gets noisy.

Method 2: ClipManager (clip-focused, lightweight)

ClipManager is the lighter cousin of Streamcord. It does one thing: post Twitch clips to a Discord channel. No go-live announcements, no chat commands, no meta-channel noise. Worth picking when you want a clean, clip-only signal.

Exact path:

1. Visit the ClipManager listing on discord.bots.gg and click Invite.
2. Authorize on your server.
3. Run the slash command /setup and follow the prompts to link your Twitch channel and pick the destination Discord channel.

Pros: extremely low cognitive load, no settings to learn, single-purpose so it doesn't bloat your server's bot list.

Cons: fewer customization knobs than Streamcord, smaller community so less third-party tutorial content. Confirm the bot is still actively maintained before committing (project listing pages can lag reality).

Method 3: Streamer.bot plus Auto Twitch Clip Scanner (full control, free)

Streamer.bot is the open-source swiss army knife that power-users adopt to automate roughly everything around their stream. Free, Windows-only, very active community. For Discord clip relay, you pair Streamer.bot with the community extension Auto Twitch Clip Scanner.

Exact path:

1. Download Streamer.bot from streamer.bot.
2. Connect your Twitch account via OAuth inside Streamer.bot.
3. Install the Auto Twitch Clip Scanner extension from the Extensions tab.
4. Configure the Clip Created trigger inside the extension.
5. Create a Send Message action that POSTs the clip title, URL and thumbnail to a Discord webhook URL (generated under Channel Settings, Integrations, Webhooks).
6. Run Streamer.bot in the background during your live sessions.

Pros: total control over the Discord payload (rich embed with thumbnail, duration, clip creator), conditional logic (only relay clips longer than 30 seconds for example), zero recurring cost.

Cons: Windows only, real learning curve, assumes your streaming PC runs continuously or that you accept missing clips during downtimes. Pick it if you're already on Streamer.bot for other chat or stream automations.

Method 4: Make.com or IFTTT (no-code visual)

If you want neither a dedicated Discord bot nor a Python script, Make.com (formerly Integromat) ships a ready-to-use template: Share new Twitch clips on a Discord channel.

Exact path:

1. Create a free account on make.com.
2. Search for the template Share new Twitch clips on a Discord channel.
3. Connect your Twitch account (OAuth) and your Discord server (via webhook URL).
4. Pick the polling interval (15 minutes by default on the free tier).
5. Activate the scenario.

Pros: no third-party bot on your server, multi-destination support (Discord plus Slack plus Notion plus Airtable in the same scenario), visual interface.

Cons: 1000 operations per month on the Make.com free tier (covers roughly 60-80 clips per month at 15-minute polling). IFTTT offers an equivalent applet but is capped at 2 free applets per account since 2020. Latency (15 minutes minimum on the free tier) is longer than the real-time bots.

Method 5: Custom Discord webhook with your backend

The most powerful and flexible method. You host a small script that polls Twitch's Helix API every minute and POSTs each new clip to a Discord webhook. Docs on both sides: Helix Clips API and Discord webhooks.

Minimal Node.js snippet:

import fetch from 'node-fetch'

const TWITCH_TOKEN = process.env.TWITCH_APP_TOKEN
const TWITCH_BROADCASTER_ID = '123456789'
const DISCORD_WEBHOOK = process.env.DISCORD_WEBHOOK_URL
let lastSeenId = null

async function pollClips() {
  const res = await fetch(
    `https://api.twitch.tv/helix/clips?broadcaster_id=${TWITCH_BROADCASTER_ID}&first=5`,
    {
      headers: {
        'Client-Id': process.env.TWITCH_CLIENT_ID,
        Authorization: `Bearer ${TWITCH_TOKEN}`,
      },
    },
  )
  const { data } = await res.json()
  const fresh = data.filter((c) => c.id !== lastSeenId)
  for (const clip of fresh) {
    await fetch(DISCORD_WEBHOOK, {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({
        content: `**${clip.title}** by ${clip.creator_name}`,
        embeds: [{ url: clip.url, image: { url: clip.thumbnail_url } }],
      }),
    })
  }
  if (data[0]) lastSeenId = data[0].id
}

setInterval(pollClips, 60_000)

Pros: sub-minute latency, keyword routing by clip title, multi-channel Discord by game, fully customizable Discord embed, zero third-party billable dependency.

Cons: you need a server (Raspberry Pi, 5-dollar VPS, serverless on Vercel or Cloudflare) and the ability to read 30 lines of code. Pick it past 100 clips per day, or when you want to route clips by game into different Discord channels.

5-method comparison table

Once your clips pile up in #clips and Discord becomes the first qualitative sort, the obvious next layer is vertical distribution. Snowball, the all-in-one tool for Twitch streamers and creators, picks up the Twitch clips coming off your live, pre-cuts them into 9:16, adds captions, and schedules them to TikTok, Reels and Shorts. It's the layer that stacks on top of the Discord relay, not a substitute.

Pick by your weekly volume

• Fewer than 10 clips per week: Streamcord, 2 minutes, done. You don't need more.
• 10 to 50 clips per week: ClipManager if you want a clean clip-only channel, or Make.com if you also need to push into Notion or Slack at the same time.
• More than 50 clips per week or routing by game: custom Node.js webhook, or Streamer.bot if you already run it.

To grow your clip pool, also clip your VODs after the fact. That's what keeps the Discord pump running on weeks when your live sessions were quieter, and it's especially useful if you're working on what makes Twitch clips go viral since you can A/B test edits offline.

FAQ

How do I automatically post Twitch clips to Discord?

Three main routes. A turn-key third-party bot like Streamcord or ClipManager, which configures in a few clicks from your Discord server. A no-code workflow on Make.com or IFTTT, which watches your Twitch clips and POSTs each new one to a Discord webhook. A custom backend script that polls Twitch's Helix /clips endpoint and POSTs the payload to a Discord webhook URL.

What's the best Discord bot for Twitch clips?

Streamcord is the safe default when you want something running in under 5 minutes with no advanced setup. ClipManager is the lightweight pick if you only want clips and no go-live noise on the same channel. Streamer.bot is the power-user choice, free and more technical, for streamers who want conditional routing or fully custom Discord embeds. For the next step, turning those Discord-relayed clips into TikTok-ready vertical video, Snowball, the AI that detects viral moments in a Twitch stream, takes over the editing layer.

How does a Discord webhook work for Twitch?

Discord generates a POST URL per channel under Channel Settings, Integrations, Webhooks. When any external service POSTs a JSON payload to that URL, Discord renders a message in the target channel. On the Twitch side, no native event pushes new clips, so the service either uses a chat-connected bot or polls the Helix /clips endpoint on a schedule.

Is Streamcord free?

Yes for core usage. Go-live announcements, clip sharing and the main commands all work on the free plan. Premium tiers add advanced filters, multiple Twitch accounts per server and higher limits. For a solo streamer who just wants clips relayed to one Discord channel, the free plan is more than enough.

Can I send Twitch clips to Discord without a bot?

Yes. Make.com and IFTTT both ship ready-made templates that watch your Twitch account and POST each new clip to a Discord webhook. That's the fastest no-code route. If you're comfortable with code, roughly 20 lines of Node.js or Python calling the Helix API and hitting your Discord webhook URL get the job done with zero third-party dependency.