Figma Community video carousel before plugin install
Use the Community media carousel to show the plugin in motion before asking for an install, because a thumbnail alone cannot explain workflow tools well enough.
Why this can grow a startup
Workflow products usually lose the user before the first click because the listing never shows what the thing actually does. Figma gives plugin publishers a better surface than most marketplaces: a thumbnail plus a carousel of images and videos. That means the page can behave like a short demo instead of a static poster. The difference matters most for plugins and widgets, where the buyer is deciding whether the workflow is obvious enough to trust in their own file.
Source-backed example
Figma's plugin publishing flow includes a thumbnail plus up to nine images and videos in the carousel, and its audience-growth guide recommends using previews to show the resource in action.
Source-reported evidence
Source: Figma Learn: Publish plugins to the Figma Community
Plugin listings can include a 1920 x 1080 thumbnail plus up to 9 images and videos in the carousel.
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 Marketplaces, Conversion, Onboarding is relevant to plugin listings, visual proof, install conversion 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 Marketplaces and Conversion, using evidence from Figma Learn: Publish plugins to the Figma Community as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next 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
Build creator and community systems around real incentives, trust, and repeat participation.