Plan one badge image for each intended tenure milestone, then upload through Kick’s Community subscription-badge controls. Kick documents transparent PNG artwork and automatic progression with subscription duration. Check the uploader for current numeric limits instead of importing another platform’s badge sizes.
A badge sequence assigned to the correct milestones, with a recorded upload map and readable progression.
In this guide
Before you start
- An eligible channel with access to subscription badge controls.
- A list of the milestone slots actually shown in the dashboard.
- Transparent PNG exports and a preserved editable badge master.
Start with the actual job
A badge system is a timeline, so the order matters as much as the individual drawings. Pick a stable object that can grow or change: a lantern gains a frame, a gem gains a facet or a plant gains a leaf. Keep the visual difference clear when the image is small.
If you are moving an identity from another service, reuse the design language rather than blindly reusing every export. Platform upload rules and visible sizes can differ. The dashboard is the final place to confirm the currently accepted file requirements.
Work through the setup
Copy the available milestones
Open Streamer Dashboard, Channel and Community, then the subscription-badge area. Write down the labels in their displayed order.
Look for: You have a real destination map before assigning any artwork.
Build a labeled proof sheet
Place each draft badge beside its intended milestone. Review the sequence in a single row or column at a small size.
Look for: A swapped stage or an indistinguishable pair becomes visible before upload.
Export transparent copies
Export PNG files with descriptive names such as lantern-stage-03. Inspect each against dark and light backgrounds and comply with limits shown by the current uploader.
Look for: The badge edges are deliberate and the filename cannot be mistaken for a duration label.
Assign, save and review
Upload one file at a time to the matching slot, then save the changes. Compare the dashboard’s final sequence with the proof sheet.
Look for: The configured progression matches the plan instead of depending on memory.
Compare the decisions
| Situation or element | Decision | Check |
|---|---|---|
| Milestone label | Copy from dashboard | Avoid assuming another platform’s sequence |
| Asset name | Use a stage plus design name | Keep exports easy to sort |
| Visual difference | Change shape or structure | Do not rely only on color |
| Existing community | Explain the update | Preserve familiar identity where possible |
Review the result and keep the master
Record which stages are intentionally left unchanged. A full redesign is not always needed when only one badge looks weak. Keeping a familiar silhouette can help long-standing subscribers recognize their place in the sequence after an update.
When a viewer’s badge differs from the latest exported file, compare the configured milestone, the member’s relevant tenure and the platform’s current behavior before replacing the artwork.
Still stuck?
A badge has a solid square background
Inspect the exported PNG’s alpha rather than the editor checkerboard alone.
The order looks wrong
Compare each saved dashboard slot with the labeled proof sheet and correct the individual mismatch.
The upload control is unavailable
Check current channel eligibility and permissions; resizing artwork will not unlock the feature.
Want graphics that already fit? Browse emote packs (they work on Kick too) ↗
Sources & references
Primary-documentation review checked on 4 November 2026, with original practical editing and review steps. Platform requirements are sourced; design choices are editorial recommendations. No hands-on upload, account access, screenshot capture or comparative performance test is claimed.
- Kick — Subscription badges ↗Checked 2026-11-04
- W3C WAI — WCAG 2.2 Quick Reference ↗Checked 2026-11-04
Spotted something out of date? Let Alex know.
How we put our guides together ↗