Variety Streamers: Stop Manually Toggling 50 Reward Slots

Twitch gives you 50 reward slots. That sounds like plenty until you stream more than one game. Rewards that make sense for one game are useless or distracting in another, and there’s no built-in way to swap sets. You either toggle them one by one before every stream or you just leave everything on and hope for the best.

Streamers have been requesting some kind of grouping or profile system for a while now, but it’s the kind of feature that’s either technically complex to implement or just hasn’t been prioritized yet. Either way, if you want this solved today you’re looking at third-party tools.

The catch is that most tools can’t actually do it either, and the reason why is worth understanding before you spend an afternoon setting something up.

Why most tools can’t help (and the ones that can require a tradeoff)

Twitch’s Channel Points API has a restriction that most streamers never hear about but it explains a lot. Every reward is tied to whatever created it. If you made a reward on the Twitch dashboard, only the dashboard can modify it. If Streamer.bot created it, only Streamer.bot can toggle or edit it. Twitch calls this the client ID, and no tool can manage rewards that belong to a different client ID, not even rewards on the same channel.

This means if you want a tool to manage your rewards, you have to recreate them through that tool. Your existing rewards, the ones you set up with the right icons and costs and cooldowns, can’t just be “imported.” You’re rebuilding each one from scratch inside whichever tool you pick.

That’s the tradeoff. The setup cost is real. But once your rewards live inside a tool that understands grouping, you stop spending time before every stream toggling things manually.

It also explains some things you might have run into already. If you’ve ever wondered why a bot could see your rewards but not change them, or why an extension asks you to recreate rewards you already have, this is why. It’s not a bug or a missing feature in the tool. It’s a platform-level restriction and there’s not much any of us can do about it. Every tool that manages rewards has to work within this constraint.

The client ID rule: Any tool that manages rewards can only control rewards it created. You’ll need to recreate your existing rewards inside whichever tool you pick. This applies to every API-based tool, not just the ones covered here.

Making the best of manual toggling

Before reaching for a tool, there are a few things you can do to make the manual approach less painful.

Keep your reward count well under 50. It’s tempting to create a reward for everything, but every reward you add is one more thing to manage when you switch games. Think about which rewards actually need to be game-specific and which work across everything you play. Community rewards like “choose my loadout name” or “hydrate” don’t need to change per game. The fewer game-specific rewards you have, the less toggling you do.

Use naming prefixes to group your rewards visually. If you prefix game-specific rewards with the game name, like “7DTD: Spawn Zombie” or “MC: Give Item,” you can sort by name in the dashboard and all the rewards for one game cluster together. This makes toggling faster because you’re not hunting through a random list.

It helps your viewers too. They can scan the reward list and immediately see which rewards are relevant to what you’re playing right now.

Pick a consistent color per category. All your horror game rewards in red, creative stream rewards in blue, always-on community rewards in green. Between the prefixes and colors you end up with a visual system that’s quick to scan even without any tooling.

If you do have game-specific rewards, get in the habit of disabling rather than deleting them. Disabled rewards still count toward the 50 limit, but they’re invisible to viewers and they keep all their settings. Deleting and recreating is where the real time sink is.

Manual checklist: Use naming prefixes per game (e.g., “7DTD: Spawn Zombie”). Pick a consistent color per category. Disable rewards instead of deleting them. Keep game-specific rewards to a minimum.

For some streamers this is honestly enough. If you play two or three games and only have a handful of game-specific rewards per game, spending a minute toggling before stream is manageable. The problem really hits when you’re rotating through more games or you’ve built out deep interactive reward sets per game. That’s when you need a tool.

The Chrome extension workaround

There’s one tool that sidesteps the client ID restriction entirely. A Chrome extension called Twitch Reward Profiles lets you save snapshots of which rewards are enabled and disabled, then switch between them with a click. It works because it’s not using the API at all. It interacts directly with the Twitch dashboard in your browser, toggling rewards the same way you would manually, just faster.

The setup is simple. You toggle your rewards how you want them for a particular game, save that as a profile, and repeat for each game. When you want to switch, you pick the profile and it flips everything for you. No need to recreate your rewards anywhere. It works with the rewards you already have.

It’s free, it has a 5-star rating from its 177 users, and it’s the lowest-effort solution if you just want the toggling to stop.

The tradeoff is that Twitch’s terms of service don’t look favorably on tools that automate interactions with their site through the browser. The extension works by scripting clicks on the dashboard DOM rather than going through official channels, and that puts it in a grey area. It’s unlikely Twitch is actively looking for people using a 177-user Chrome extension, but it’s worth knowing the risk is there.

There’s also a reliability question. If the Twitch dashboard layout changes, the extension could break until the developer updates it. With a project that small there’s no guarantee that happens quickly.

CastMate: automatic reward switching per game

After looking at a dozen streaming tools, CastMate is the one that handles this problem best. It’s free, open-source, and built around a profile system where you organize your triggers into groups. If a profile is active, any channel point rewards tied to its triggers are visible to viewers. If the profile is inactive, those rewards disappear. You don’t toggle rewards directly. You activate profiles and the rewards follow.

The part that makes this useful for variety streamers is how profiles activate. You can set a condition on any profile, like “my current Twitch category is 7 Days to Die,” and the profile turns itself on and off as your category changes. No commands, no manual toggling, no remembering to switch things before you go live. Change your game on Twitch and the right rewards show up.

CastMate also has a Stream Plans feature where you can lay out your stream as a series of segments, each with its own game category and title. As you move through segments your category updates on Twitch, your profiles react to the change, and your rewards swap automatically. It ties the whole thing together if you like to plan your streams in advance.

The same tradeoff applies here as everywhere else. Your rewards need to be created inside CastMate for it to control them, and the 50-reward limit still applies including hidden ones.

CastMate is free to download and the documentation covers the profile system in detail.

Streamer.bot: the most flexible option if you don’t mind building it yourself

Streamer.bot takes a different approach. Instead of giving you a profile system, it gives you the pieces to build one. You organize your rewards into named groups, then use actions and triggers to control which groups are enabled or disabled and when.

The core of it is reward groups. You create groups like “7DTD Rewards” or “DnD Rewards,” assign your rewards to them, and then use a sub-action called Set Group Enabled State to flip an entire group on or off at once. There’s also Set Group Paused State if you want rewards to stay visible but greyed out instead of disappearing completely.

Where it gets interesting is the Stream Update trigger. This fires whenever your stream title or game category changes, and it gives you the new game name and the old one as variables. You can wire this up so that when your category changes to 7 Days to Die, the action disables all your other game groups and enables the 7DTD group. Change to DnD and it does the reverse. The result is the same automatic switching you get with CastMate, but you’re assembling the logic yourself instead of configuring a profile.

For more complex setups, there’s a Configure Rewards sub-action that lets you set the state of multiple individual rewards in a single action rather than toggling groups. This is useful if your reward setup doesn’t break down cleanly into one group per game.

Streamer.bot has an active community with a shared extensions library, which matters when you’re building custom automation. You can import ready-made setups, including a Channel Point Kill Switch that lets you or your mods toggle reward groups on and off with a chat command. If you get stuck, there are people in the Discord who have solved whatever you’re trying to do.

The tradeoff compared to CastMate is setup time. Streamer.bot doesn’t decide how your rewards should behave based on a profile condition. You define every step of the logic: which trigger, which action, which groups get enabled, which get disabled. That flexibility is the point for a lot of users, but it also means you need to be comfortable with the action-trigger model before this approach makes sense. If you’ve never used Streamer.bot before, plan for a learning curve.

The same client ID restriction applies. Your rewards need to be created inside Streamer.bot for it to control them. Streamer.bot does make this easier than most tools. It can read your existing rewards from Twitch and you can duplicate them into Streamer.bot-owned copies directly. The only thing that doesn’t carry over is the icon, which you’ll need to re-upload manually.

The documentation covers the reward system and the sub-actions reference has the specifics on group management.

Tool comparison: Chrome extension: fastest setup, ToS grey area. CastMate: auto-switches by game category, free and open-source. Streamer.bot: most flexible, DIY setup required. All API-based tools require recreating your rewards.

What to do next

If you play two or three games and have a manageable number of game-specific rewards, start with the manual approach. Prefixes, colors, and a quick toggle routine before stream might be all you need. Don’t add tooling complexity for a problem that takes you sixty seconds to solve.

If the toggling has become a real time sink or you keep forgetting to switch things before going live, pick based on how much setup you want to do. The Chrome extension is the fastest path with the least commitment, but know the risks. CastMate is the best option if you want something that just handles it for you once it’s configured. Streamer.bot is the right choice if you’re already using it or you want full control over the logic.

Whichever route you pick, you’ll hit the same client ID tradeoff with any API-based tool. Budget time for recreating your rewards inside the tool, and do it on a day you’re not streaming. Once that initial setup is done, you shouldn’t have to think about reward management again.