Custom Power-ups made the menu bigger
Twitch's May 2026 monetization updates made this question more urgent. Twitch said eligible monetizing streamers can create Custom Power-ups that let chat spend Bits to trigger stream effects, choose actions, or influence what happens live. Twitch also expanded monetization tools more broadly in 2026, which means more creators now have native support tools sitting next to third-party paid moments.
That is good for creators, but it can make the viewer menu messy. A streamer may now have Channel Points, Bits, subs, Hype Trains, Custom Power-ups, direct tips, paid TTS, sound alerts, viewer uploads, polls, and merch goals all competing for attention. If every lane promises the same kind of moment, viewers get confused and moderators end up explaining pricing during the stream.
The clean move is to decide what each lane is for. Custom Power-ups are good for Twitch-native Bit moments that should feel quick and platform-connected. Paid TTS is better when the viewer is buying a message that needs a browser-source voice, moderation, pronunciation control, replay rules, and sometimes cross-platform availability. Sound alerts are for short audio interruptions. Viewer uploads are visual moments that need review. Keep those jobs separate.
- Custom Power-up: short Twitch-native action, priced in Bits, clear on-stream effect.
- Paid TTS: message or joke read aloud through a controlled browser source.
- Sound alert: short audio hit with cooldown and scene rules.
- Viewer upload: image or media submission that needs preview, crop, and approval.
- Poll or wheel: viewer influence with clear limits and no gambling-shaped promises.
Price by interruption level
Do not price rewards only by how funny they sound in a list. Price by interruption level. A small overlay sticker is cheaper because it uses a corner of the scene and does not require the streamer to stop talking. A TTS message costs more because it competes with the streamer's voice and can derail timing. A viewer upload costs more because a moderator must inspect the content before it hits OBS.
Use a four-level model. Level one is background support, like a badge, tiny overlay, or non-verbal animation. Level two is a short on-stream effect, like a sound, sticker, or quick caption. Level three interrupts the host, like paid TTS, voice filter, or question card. Level four changes the stream plan, like choosing a challenge, picking the next route, or triggering a special segment.
This model keeps pricing fair without pretending every reward has equal cost. Viewers can see why a short sticker is cheaper than a thirty-second TTS. Mods can enforce rules because the levels match real production work.
- Level one: low-motion badge, tiny sticker, or support label.
- Level two: short alert, sound, or visual effect under five seconds.
- Level three: TTS, question card, voice effect, or highlighted message.
- Level four: stream choice, challenge, scene change, or special segment.
Keep paid TTS away from the cheap lane
Paid TTS should not be the cheapest paid action unless the stream is built around constant audio interruptions. TTS uses the streamer's ears, the audience's ears, and the moderator's judgment. It can be hilarious, but it also has the highest chance of stepping on a conversation, sponsor read, ranked match, guest segment, or serious moment.
The safer setup is to make basic visual effects cheaper and TTS more deliberate. A viewer who wants to support can buy a small visual moment. A viewer who wants the streamer's attention can pay more for TTS and accept stricter rules. That does not punish viewers. It protects the stream from becoming a nonstop voice queue.
StreamableBot helps here because paid TTS can live in a browser source with moderation, replay rules, voice selection, and queue controls. Twitch Custom Power-ups can still exist for native Bit-powered actions, but TTS should stay in the lane where the streamer and mods can manage it properly.
- Do not let cheap TTS fire during sponsor reads, guest interviews, or serious segments.
- Use stricter moderation for TTS than for small visual alerts.
- Cap message length by tier.
- Use cooldowns by scene, not only by viewer.
- Give moderators pause, skip, replay, and reject controls.
Avoid duplicate viewer promises
The viewer menu should not sell the same promise in three places. If Custom Power-up, paid TTS, and Channel Points all say make me say something funny, viewers will choose by price and then argue when the cheaper one has fewer controls. Write the promise differently for each lane.
For example, a Custom Power-up might trigger a five-second plushie overlay. Paid TTS reads a message in a selected voice after mod approval. Channel Points can request a free non-guaranteed prompt that may be skipped. A tip alert can thank the viewer with a short message but not guarantee a voice read. Each action now has a different expectation.
The menu copy should be plain. Do not hide limits in a long rules page. Put the important difference in the command, checkout label, or overlay title. Viewers accept limits better when the product itself is clear.
- Custom Power-up: instant or near-instant effect with a narrow action.
- Paid TTS: approved voice message with length and safety limits.
- Channel Points: free request or queue suggestion with no paid guarantee.
- Tip alert: support message, not always a full TTS read.
- Viewer upload: visual submission that can be rejected or delayed.
Moderators need a price map too
Pricing is not only for viewers. Moderators need to know why one reward is handled differently from another. If a low-cost sticker fails, the mod might simply replay it. If a high-cost TTS gets cut off by a scene change, the mod may owe a replay or credit according to the stream's rules. If a challenge reward arrives during a unsafe moment, the mod may need to hold it until later.
Put the price map in moderator notes. Each reward should have fulfillment rules, replay rules, rejection reasons, and a pause rule. The mod should know whether a reward can be delayed, skipped, credited, or refunded outside the live show. That prevents on-stream arguments about money.
Payment docs matter here. Stripe explains that disputes are formal claims through card networks and immediately reverse payment while evidence is handled. PayPal says refunds can be full or partial within a defined window and cannot be canceled once issued. Streamers do not need to quote payment docs live, but they should understand that refund language has consequences.
- Fulfilled: viewer got the promised on-stream moment.
- Replay: moment failed because of browser source, audio, or scene timing.
- Credit: streamer keeps the payment path internal and offers another moment later.
- Reject: message or upload violates rules before fulfillment.
- Refund path: handled off-stream by the account owner, not by chat debate.
Test the menu during different stream modes
A price ladder that works during Just Chatting can fail during ranked games, IRL walking, sponsor segments, or collabs. Test the menu in modes. In focus mode, allow low-motion visual rewards and hold TTS. In hangout mode, open TTS and questions. In sponsor mode, use approved alerts only. In chaos mode, allow higher-interruption rewards for a limited window.
The important part is that the viewer-facing menu changes with the mode. If TTS is paused, the command should say paused. If Custom Power-ups are open but paid uploads are closed, the page should say that. Viewers should not pay for a moment and learn the mode changed afterward.
StreamableBot should act like a production menu, not a random list of triggers. The cleaner the modes, the easier it is to earn without turning the show into an argument about fulfillment.
- Focus mode: visual alerts only, TTS held or disabled.
- Hangout mode: TTS, questions, uploads, and light sounds open.
- Sponsor mode: approved alerts, no risky messages, no surprise uploads.
- Guest mode: lower volume, stricter copy, slower queue.
- Chaos window: short timed segment where louder rewards are allowed.
Other resources
Use these references to keep Twitch-native monetization, paid TTS, and payment workflows aligned instead of guessing from old channel setups.
- Twitch Blog: New ways to turn community participation into earnings.
- Twitch Blog: Monetization for All.
- Twitch Help: Channel Points Guide for Creators.
- Stripe Docs: Disputes.
- PayPal Help: How do I issue a refund?
Quick answers
Should Custom Power-ups replace paid TTS?
No. Custom Power-ups are a good Twitch-native Bit lane for short effects. Paid TTS should stay separate when you need voice control, moderation, queue rules, replay handling, and cross-platform browser-source playback.
How should I price paid TTS compared with small alerts?
Price TTS higher than low-motion visual alerts because it interrupts audio, needs stronger moderation, and often requires the streamer to react. Small stickers or labels can sit in a cheaper support lane.
Can Channel Points, Custom Power-ups, and paid TTS all coexist?
Yes, if each one has a different promise. Channel Points can test free ideas, Custom Power-ups can trigger short native effects, and paid TTS can sell controlled voice moments with clear rules.
What should moderators know before paid moments open?
They need the reward tiers, pause rules, rejection reasons, replay rules, escalation path, and which stream modes allow each reward. Pricing is only useful if mods can enforce the promise.