Discord App Directory five-asset carousel with best proof first
Build the App Directory carousel like a proof sequence: lead with the strongest image or video, because Discord allows only five assets and shows them in an auto-rotating top-of-page carousel.
Why this can grow a startup
Visuals on Discord's app profile are not decorative. They are the first product proof a server owner sees above the fold. Discord's profile-page guidance says teams can add up to five assets total and recommends putting the best asset first, with video first when relevant. That constraint rewards a tighter story. Instead of dumping random screenshots, teams should show the moment the app becomes useful inside Discord so the install decision gets easier before the user reads the long description.
Source-backed example
Discord's App Directory profile-page guide says the top carousel supports up to five images or videos, rotates automatically, and recommends putting the best asset first or leading with video if you have one.
Source-reported evidence
Source: Discord Developers Help: App Directory App profile pages
The App Directory carousel supports up to 5 assets total.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Communities, Brand, Conversion is relevant to discord, visual proof, app directory and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Communities and Brand, using evidence from Discord Developers Help: App Directory App profile pages as context—not as a promised result.
- Record a baseline for: Target users from this channel who complete the intended first action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.