JetBrains plugin screenshots show the IDE workflow
Fill the media block with legible screenshots or short motion that show the plugin inside the JetBrains product instead of decorative desktop scenes.
Why this can grow a startup
Technical buyers want to picture the plugin in the editor they already use. JetBrains' media guidance is valuable because it pushes screenshots toward that decision: show the relevant product UI, keep the text readable, use clean aspect ratios, and strip out unrelated clutter. The result is a shelf that teaches the workflow instead of asking the user to imagine it from generic branding.
Source-backed example
JetBrains recommends screenshots of plugin features at a minimum 1200 by 760 pixels, says they should display the relevant JetBrains product interface, and warns against mismatched aspect ratios, unrelated branding, personal information, or desktop backgrounds.
Source-reported evidence
Source: JetBrains Marketplace Docs: Best practices for listing your plugin · Browse JetBrains Marketplace Docs: Best practices for listing your plugin tactics
JetBrains recommends screenshots at a minimum of 1200 × 760 pixels and uses the media block as the first element users see on the plugin page.
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, Product is relevant to jetbrains marketplace, visual proof, activation 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 JetBrains Marketplace Docs: Best practices for listing your plugin as context—not as a promised result.
- Record a baseline for: Share of target users completing the product's first-value 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.
SOURCE HUB
More tactics from JetBrains Marketplace Docs: Best practices for listing your plugin
Explore related GrowthDex examples and evidence connected to JetBrains Marketplace Docs: Best practices for listing your plugin.
Open JetBrains Marketplace Docs: Best practices for listing your plugin source hub