# 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. - Canonical HTML: https://growth.iangoh.com/growth-ideas/jetbrains-plugin-screenshots-show-the-ide-workflow/ - Source: [plugins.jetbrains.com](https://plugins.jetbrains.com/docs/marketplace/best-practices-for-listing.html) - GrowthDex source hub: [JetBrains Marketplace Docs: Best practices for listing your plugin](/sources/jetbrains-marketplace-docs-best-practices-for-listing-your-plugin-plugin/) - Last checked: 2026-06-06T10:04:00Z - Rarity: rare - Budget: low - Channels: Marketplaces, Conversion, Product - Stages: jetbrains marketplace, visual proof, activation, developer tools ## Why this can grow 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. ## Ian's take From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. For this tactic, I would watch one clear growth signal before putting more time or budget behind it. ## Action plan 1. Define one narrow startup segment where jetbrains plugin screenshots show the ide workflow can create a measurable lift. 2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Conversion channel. 3. Use the evidence from plugins.jetbrains.com to set the first version of the message, format, and audience. 4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal. 5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook. ## 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. ## Adjacent tactics in the same lane - [JetBrains plugin first 40 characters carry the preview card](/growth-ideas/jetbrains-plugin-first-40-characters-carry-the-preview-card/) - same source, 1 shared channel, 2 shared stages - [JetBrains plugin tags fit the real search](/growth-ideas/jetbrains-plugin-tags-fit-the-real-search/) - same source, 1 shared channel, 2 shared stages - [JetBrains plugin verified vendor badge before scale push](/growth-ideas/jetbrains-plugin-verified-vendor-badge-before-scale-push/) - 2 shared channels, 2 shared stages - [GitHub Marketplace feature card preview before brand refresh](/growth-ideas/github-marketplace-feature-card-preview-before-brand-refresh/) - 2 shared channels, 1 shared stage ## Read GrowthDex essays Browse the plain-English essay index at [GrowthDex Blog](/blog/). ## Related GrowthDex essays - [The JetBrains plugin page should finish the IDE trust check](/blog/the-jetbrains-plugin-page-should-finish-the-ide-trust-check/) - marketplaces, SEO, brand trust ## Advisory If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.