Short answer
For BTTV, prepare the emote like a Twitch chat asset, upload it under the right account, enable it for the channel, and remember that only viewers using BTTV will see it.
Who this is for
This guide is for Twitch creators who want a simple BTTV upload workflow after making an emote in MakeEmoji.
BTTV traffic is practical and bottom-funnel for streamers. The post should clarify visibility and channel setup so creators do not blame the image file for extension behavior.
Recommended starter set
BTTV account connected to Twitch.
Readable static or animated emote file.
Channel slot or personal upload target.
Short emote code.
Extension testing browser.
Backup Twitch-native export.
Workflow
Step 1
Export for small chat
Use a tight crop and high contrast. BTTV viewers still see emotes at chat size, so the Twitch readability test applies.
Step 2
Upload and enable
After uploading, make sure the emote is enabled where viewers expect it. Uploaded but disabled emotes are a common source of confusion.
Step 3
Set expectations
BTTV visibility depends on viewer setup. Tell your community if the emote requires an extension.
Quality checklist
- Check current BTTV requirements before upload.
- Avoid long names.
- Test on a viewer account.
- Keep a static fallback.
- Explain extension requirements to chat.
Common mistakes
- Assuming BTTV emotes are native Twitch emotes.
- Using tiny details because the dashboard preview looks large.
- Forgetting to enable the emote.
- Not communicating viewer requirements.
Next steps
FAQ
Can everyone see BTTV emotes?
No. Viewers generally need BTTV support enabled. Native Twitch emotes have broader visibility.
Can MakeEmoji export BTTV-ready art?
MakeEmoji can create the emote asset. You should still verify current BTTV upload requirements before submitting.
Should I use BTTV or Twitch native emotes?
Use Twitch native emotes for broad subscriber value. Use BTTV for extra culture, experiments, and extension-friendly communities.