The Short Answer
Quick answer: A JetBrains plugin logo is one SVG file at 40 x 40 pixels, named pluginIcon.svg, with an optional pluginIcon_dark.svg for dark themes. It shows at 40 x 40 in lists and 80 x 80 on detail pages. Screenshots should be at least 1200 x 760, all in the same aspect ratio. Keep the plugin name to 1 to 4 words and 20 characters, with a hard limit of 60.
The rest of this guide covers each rule, and what the 30 most downloaded plugins actually use.
What I Checked
On 16 November 2026, I read two JetBrains pages: the plugin logo guide in the IntelliJ Platform SDK docs, and the Marketplace's guide to listing your plugin. Together they set every image and text rule for a plugin page.
Then I pulled the 30 most downloaded plugins from the JetBrains Marketplace's public API. For each one, I measured the logo file and every screenshot, and noted whether it adds a video.
That came to 28 logos and 120 screenshots. The sample runs from JetBrains AI Assistant, at about 258 million downloads, to Material Theme UI, at about 19 million.
Every Listing Item at a Glance
Here's what a plugin page takes, and where each item comes from.
| Item | Rule | Set in |
|---|---|---|
| Logo | SVG, 40 x 40 | pluginIcon.svg |
| Dark logo | Optional SVG, 40 x 40 | pluginIcon_dark.svg |
| Screenshots | 1200 x 760 or larger, one aspect ratio | Admin panel |
| Video | YouTube link, under 5 minutes suggested | Admin panel |
| Name | 1 to 4 words, 20 characters suggested, 60 max | plugin.xml |
| Description | First 40 characters in English | plugin.xml or page |
| Tags | At least one | Upload form |
The split matters. The logo and name ship inside the plugin, so changing them means a new version. Screenshots, video and the page description can change any time.
The Plugin Logo: 40 x 40 SVG
JetBrains asks for one logo file at one size: 40 x 40 pixels. The IDE and the Marketplace scale it to two display sizes.
| Where | Shown at |
|---|---|
| Plugin list in the IDE's Plugin Manager | 40 x 40 |
| Plugin details screen in the IDE | 80 x 80 |
| Plugin page on JetBrains Marketplace | 80 x 80 |
The file must be an SVG, so it stays sharp at both sizes. It goes in the META-INF folder of the plugin's main JAR file. In your project, that means the resources/META-INF folder.
It's worth checking your design at both sizes before you ship. Details that read well at 80 pixels can turn to mush at 40.
Padding and Shape Sizes
The logo shouldn't fill the whole 40 x 40 square. JetBrains asks for at least 2 pixels of transparent padding around the edge, and gives exact sizes for basic shapes.
| Shape | Size inside the 40 x 40 file |
|---|---|
| Square | 32 x 32 |
| Circle | 36 across |
| Wide rectangle | 36 x 26 |
| Tall rectangle | 26 x 36 |
The square gets the most padding because a filled square looks heavier than a circle of the same width. JetBrains calls this visual weight. The goal is a logo that looks the same size as its neighbors in a list, whatever its shape.
Light and Dark Logos
JetBrains IDEs run in light and dark themes, and your logo has to work on both. The guide says to make sure it's visible on light and dark backgrounds.
If one design can't do that, ship two files. pluginIcon.svg is the default. If you add pluginIcon_dark.svg, the dark file is used only with dark IDE themes, and the default file is used only with light ones.
For colors, JetBrains suggests using the colors of your technology's existing logo, after checking its license terms. If there's no logo to borrow, it points you to the Action Colors Palette in its icon guidelines.
Keep the Logo File Small
JetBrains wants the logo file small, ideally under 2 to 3 kB. That's one reason it insists on SVG.
It also warns against converting a bitmap to SVG with an automatic tool. The result is often 100 kB or more, because the tool traces every pixel as a shape.
The top plugins mostly get this right. In my sample, the middle logo was 1,859 bytes, 15 of 28 were under 2 kB, and 21 were at 3 kB or less. The largest was 80,960 bytes, about 40 times the middle one.
Draw the logo as a vector from the start, and you'll stay well inside the limit.
Screenshots: 1200 x 760 or Larger
The listing guide says the Media section is the first thing users see on a plugin page. You add screenshots and a video there, in the admin panel, after you upload the plugin.
The minimum recommended screenshot size is 1200 x 760 pixels. GIFs that show the plugin in action are fine, and so is overlay text that explains what a screenshot shows. You can add informational slides too.
One rule is easy to miss: don't upload screenshots with different aspect ratios. Pick one shape, such as 1200 x 760 or exactly double it at 2400 x 1520, and use it for every image.
What to Show in Screenshots
JetBrains lists what it wants and what it doesn't.
| Do | Don't |
|---|---|
| Show the interface of the JetBrains IDE your plugin runs in | Mix aspect ratios |
| Use the default IDE theme | Show your plugin in a misleading way |
| Keep text sharp and readable | Advertise other products or brands |
| Include only what's relevant | Include personal information |
| Show desktop backgrounds or browser windows |
Theme plugins are the exception to the default theme rule. They must show the style they add, so a theme's screenshots should show the theme itself.
Crop each screenshot to the IDE window or the part of it your plugin changes. A desktop wallpaper around the edges breaks the rule.
Video: Under 5 Minutes
If you have a product video on YouTube, you can add its link in the Media section. JetBrains suggests a short promo or demo under 5 minutes, and says a video can help users engage with your listing.
Few top plugins use one. Only 5 of the 30 in my sample had a video link: GitHub Copilot, Full Line Code Completion, Space, Package Checker and Kubernetes.
A short screen recording of your plugin's main task is enough. If you can't fit it in 5 minutes, show one feature well rather than every feature quickly.
The Plugin Name: 20 Characters or Less
The name comes from the name tag in plugin.xml. JetBrains suggests 1 to 4 words and no more than 20 characters. The hard limit is 60, but the guide strongly recommends staying short.
Its list of don'ts is specific:
- 1Don't use the word Plugin. Docker, not Docker Plugin Support for IntelliJ IDEA.
- 2Don't add generic words like Support, Tool or Integration.
- 3Don't put JetBrains or an IDE name in it. Compatible products show separately.
- 4Don't use emoji, version info or slogans.
Write it in title case, with Latin characters. Language packs are the only exception to that.
The First 40 Characters of the Description
The description comes from plugin.xml by default, but you can edit it on the plugin's page without a new version. It shows in the IDE's Plugin Manager and on the Marketplace.
The first 40 characters matter most. They must be in English and work as a short summary, because the Marketplace uses them on the plugin's preview card. You can't edit the card text separately.
JetBrains also asks you to skip marketing words like simple, lightweight or professional, and to avoid claims users can't verify. Bullet points that list your main benefits work better.
Images Inside the Description
You can put images in the description, but JetBrains would rather you use the Media section for them.
If you do embed images, keep them between 600 and 800 pixels wide. Images in the description can't be zoomed, so a wide screenshot shrinks until its text is hard to read. They also need to look right in two places: the Marketplace website and the Plugin Manager inside the IDE.
The safe split is simple. Put full screenshots in Media, where people can open them large. Use description images only for small, focused crops, like one button or one popup.
What 30 Top Plugins Use for Screenshots
Of the 30 plugins, 20 had screenshots. Together they held 120 images, and the middle plugin had 4.
| Screenshot size | Images |
|---|---|
| 2400 x 1520 | 25 |
| 600 x 500 | 13 |
| 1200 x 760 | 6 |
| 1920 x 1080 | 5 |
| 2581 x 1549 | 5 |
| 2880 x 1800 | 4 |
The most common size, 2400 x 1520, is exactly twice the 1200 x 760 minimum. Five JetBrains plugins use it: Junie, Docker, GitHub, GitLab and Kubernetes. Package Checker uses 1200 x 760 itself for all six of its images.
In all, 99 of 120 screenshots met the minimum. Most were PNG files, and six were GIFs.
Gaps in the Sample
Even the biggest plugins skip parts of the guide.
- 1Ten of 30 had no screenshots at all. That includes Dart, Flutter, Vue.js and IdeaVim.
- 2Two had no custom logo. Subversion and ExternalAnnotations showed none in the API.
- 3Several mixed shapes. Space pairs 2880 x 1800 images with a 1600 x 1200 one, and Full Line Code Completion mixes three shapes.
- 4Five of 20 had a screenshot under 1200 x 760.
These plugins likely get away with it because many people already know them by name. A new plugin doesn't have that. For you, a full Media section is one of the few ways to show what you built before someone installs it.
Where PlayMockUp Fits
PlayMockUp makes store images for apps. Its mockup editor frames your screenshots and adds caption text, which JetBrains allows as overlay text. Export every image at the same size, such as 2400 x 1520, so they share one aspect ratio.
For caption ideas, our guide to screenshot captions that convert covers short lines that tell a viewer what each image shows.
If your tool also ships for VS Code, our VS Code Marketplace guide covers that store's PNG icon, banner color and README image rules.
Frequently asked questions
What size is a JetBrains plugin logo?
40 x 40 pixels, as an SVG named pluginIcon.svg in the plugin's META-INF folder. The IDE shows it at 40 x 40 in lists and 80 x 80 on detail screens.
Can I use a PNG for my JetBrains plugin logo?
No. JetBrains requires SVG, so the logo stays small and sharp at both display sizes. Draw it as a vector rather than converting a PNG, which can create files of 100 kB or more.
What size should JetBrains Marketplace screenshots be?
At least 1200 x 760 pixels, all in the same aspect ratio. The most common size among the top 30 plugins was 2400 x 1520, exactly double the minimum.
How long can a JetBrains plugin name be?
The hard limit is 60 characters, but JetBrains recommends 1 to 4 words and no more than 20 characters. Leave out the word Plugin and any IDE name.
How do I make an app icon that works at small sizes?
Keep one simple shape, few details and strong contrast. Our [app icon size guide](/blog/app-icon-size-guide-play-store-app-store-2026) covers how to design one mark that holds up in small lists and large pages.
Build the mockup in your browser.
Drop a screenshot into a real device frame and export at the exact store size — free, no signup.