Skip to main content
PlayMockUp
Guide8 min read

GitHub Marketplace Logo and Screenshot Rules (2026)

RVBy Rohit
An open laptop on a desk in a bright office

The Short Answer

Quick answer: A GitHub Marketplace listing needs a logo of at least 200 x 200 pixels, shown inside a round badge with a background color you pick. The feature card background is 965 x 482. You can add up to 5 screenshots, each at least 1200 pixels wide, and all with the same aspect ratio. Keep the very short description to 40 to 80 characters, and don't put words in your logo.

The rest of this guide covers each rule, and what the 30 most popular apps actually upload.

What I Checked

On 16 November 2026, I read GitHub's guide to writing a listing description for your app. It holds every image and text rule for Marketplace listings.

Then I pulled the 30 most popular apps from GitHub Marketplace, using its own popularity sort. For each one, I measured every screenshot, checked the logo GitHub serves, and read the short description.

The list runs from Render, LovableBot and GitGuardian through CircleCI, Slack and Snyk, down to Sourcery and Builder.io. That came to 95 screenshots in all.

Every Image at a Glance

Here's the full set of images a listing uses.

ImageRuleWhere it shows
LogoAt least 200 x 200, cropped to a squareEvery listing, in a round badge
Badge colorYou pick oneBehind the logo
Feature card965 x 482 background, plus a text colorTop of the Marketplace homepage, if featured
ScreenshotsUp to 5, at least 1200 wide, one shapeYour app's landing page

The logo and feature card both need a custom image. You set all of these while you draft your listing, and the draft shows a preview of the logo and card as you go.

The Logo: 200 x 200 or Larger

GitHub asks for a logo of at least 200 x 200 pixels, so it won't need to be scaled up when your listing goes live.

GitHub crops every logo to a square. Its guide recommends a square image with your logo in the center, so nothing important sits near the edges.

For best results, GitHub suggests a transparent background. Then the badge color shows through, and your logo looks like it belongs on the badge.

If your source logo is a vector, export a PNG at 400 x 400 or more. That's twice the minimum, and it's the size GitHub served for most logos in my sample.

The Badge Color

Every Marketplace listing shows the logo inside a round badge. You choose the badge's background color.

GitHub's tip is to match it to your logo's background. If your logo has a white background, pick white. If it's transparent, pick the color that makes the logo look best.

Get this wrong and you'll see a square of one color sitting inside a circle of another. That looks broken at any size.

The Marketplace homepage has a dark background, so test your badge against dark too. A light logo on a light badge can still disappear if the logo itself has no edge.

Keep Words Out of the Logo

GitHub's guide is direct: avoid logo images with words or text in them. Text doesn't scale well on small screens.

That rules out a common habit, the wordmark logo, where your app's name is the logo. On a small round badge, the letters turn into a smudge.

Your name already shows next to the badge. So the logo only needs a mark or symbol people can spot.

If your brand only has a wordmark, use its first letter, or a simple shape from it. Test it at the size it'll show in search results, not at the size you designed it.

The Feature Card: 965 x 482

A feature card shows your logo and name on a custom background image. GitHub shows it when your app is one of the four apps picked at random for the top of the Marketplace homepage.

GitHub's rules for it are short:

  1. 1The background image is 965 x 482 pixels.
  2. 2Use a pattern or texture. It helps the card stand out on the dark homepage, and it should match your brand.
  3. 3Pick a text color for your app's name that reads clearly over the background.

Since your name is laid on top, keep the busy parts of the pattern away from where the text sits.

Screenshots: Up to 5, 1200 Wide

You can upload up to five screenshots for your app's landing page, and drag them into any order. Each can have an optional caption.

GitHub says images must be high resolution, at least 1200 pixels wide. It also asks you to show as much of the interface as you can, so people see what the app does.

Put your strongest screenshot first. On a landing page, that's the one most people see before they decide whether to read on.

One caution: the 1200 pixel rule is about width. A tall, narrow image can still fail it, even with lots of pixels.

One Shape for Every Screenshot

GitHub asks for all screenshots to have the same height and width, or aspect ratio. The reason is practical: different shapes make the page jump as people click from one image to the next.

The simplest way to meet this is to pick one size, like 1600 x 1000 or 2400 x 1800, and export every screenshot at exactly that size.

If some screens are wider than others, don't stretch them. Place each one on a background of the same size instead, so the frame stays fixed while the content changes. That keeps the gallery steady and still shows the real interface.

Crop Out the Browser

Many Marketplace apps run in a browser, so their screenshots often start as browser captures. GitHub asks you to keep only the page content.

Leave out the address bar, the title bar and the toolbar icons. GitHub says they don't scale well to smaller screens, and they take space from your app.

This is the opposite of Flathub, which wants the full window with its title bar and shadow. Each store has its own idea of a clean screenshot.

A quick fix is to capture with your browser's own screenshot tool, which grabs just the page area.

No Borders, Short Captions

Two more rules finish the screenshot set.

First, don't add boxes or borders. GitHub already shows your screenshots inside a box on the landing page, so your own frame would double it up.

Second, keep captions short. GitHub says captions work best when they're short and snappy.

A caption works best when it names one thing the screenshot proves, like Review comments on every pull request. If a caption needs two sentences, the screenshot is probably trying to show too much at once.

The Very Short Description

This line sits under your app's name on the Marketplace homepage. GitHub recommends 40 to 80 characters, and sets clear style rules:

  1. 1Describe what the app does. Don't write a call to action, like Manage your projects. Write Manages your projects instead.
  2. 2Don't repeat the app's name.
  3. 3Use sentence case. Capitalize only the first word and proper nouns.
  4. 4No full stop at the end, and never more than one sentence.
  5. 5Use a serial comma in lists.
  6. 6Don't call people users.

The listing name itself can be up to 255 characters, but it can't match an existing GitHub account unless that account is yours.

Introductory and Detailed Descriptions

Your landing page has two longer texts.

FieldLengthNotes
Introductory description150 to 250 characters recommendedRequired, starts with your app's name
Detailed descriptionUp to 1,000 charactersOptional, 3 to 5 value propositions

GitHub asks for the active voice, periods instead of exclamation marks and no acronyms unless they're well known, like API.

Each value proposition gets a short title, formatted as a level three heading, then one or two sentences. The detailed description only shows when someone clicks Read more, so put your key point in the introduction.

What 30 Top Apps Do With Screenshots

Here's how many screenshots the 30 most popular apps upload.

ScreenshotsApps
None1
1 to 28
3 to 412
59

CircleCI was the only one with none. Of the 95 screenshots, 91 were PNG, and 93 met the 1200 pixel width rule. The 2 that didn't came from GitGuardian and WakaTime.

The shape rule was missed more often. Of the 23 apps with two or more screenshots, 13 kept one shape for all of them. The other 10 mixed shapes, including CodeRabbit, which mixed one tall portrait image with wide ones.

Logos and Descriptions in the Sample

I asked GitHub for each logo at 400 x 400. 18 came back at that size. The other 12 came back smaller, from 180 to 366 pixels, which suggests their uploads were smaller. GitGuardian's came back at 180 x 180, under the 200 pixel minimum.

19 of the 30 logos use a transparent background, as GitHub suggests. Of the 11 with a solid background, 8 set a badge color that matches it exactly.

Short descriptions were looser. Only 13 of 30 stay in the 40 to 80 character range. 11 run longer, and 6 are shorter. 16 are written as commands, like Test and deploy with confidence, the style GitHub's guide warns against.

Where PlayMockUp Fits

PlayMockUp's mockup editor places screenshots on a fixed size background, which is one way to give every Marketplace screenshot the same shape. Skip the device frames and borders here, since GitHub already draws a box around each image.

If your app also ships as an editor extension, our VS Code Marketplace guide covers that store's icon and README image rules.

For browser extensions, our Chrome Web Store image guide lists its screenshot and promo tile sizes.

Frequently asked questions

What size should a GitHub Marketplace logo be?

At least 200 x 200 pixels. GitHub crops logos to a square, so upload a square image with the logo centered, ideally on a transparent background.

What size are GitHub Marketplace screenshots?

At least 1200 pixels wide, and all with the same aspect ratio. You can upload up to five, each with an optional caption, and drag them into any order.

What is the GitHub Marketplace feature card size?

The background image is 965 x 482 pixels. GitHub lays your logo and app name on top, and shows the card when your app is one of four picked at random for the homepage.

How long should the GitHub Marketplace short description be?

GitHub recommends 40 to 80 characters. Describe what the app does, use sentence case, don't repeat the app's name and don't end with a full stop.

Do JetBrains plugins use the same image rules?

No. JetBrains uses an SVG logo at 40 x 40 and screenshots of at least 1200 x 760. Our [JetBrains plugin guide](/blog/jetbrains-plugin-logo-screenshot-sizes-2026) covers each size and what top plugins upload.

Build the mockup in your browser.

Drop a screenshot into a real device frame and export at the exact store size — free, no signup.