Google Play Developer Page Header Image Size (2026)

I read Google's Play Console help on developer pages on 9 November 2026. I also checked the developers behind 30 popular Play apps to see who has a page and what files they use.

Below is each image, the setup steps and what big developers actually upload.

A developer page is your brand's own page on Google Play. It shows a large header image, your developer icon, a short line about your brand and your apps.

Google calls it a Developer account page in its Play Console help on developer profiles. You get a fixed web address for it, which you can share anywhere.

The page also lets you feature one app at the top. Your other published apps still appear below it.

You can see a live example on Google LLC's developer page. It shows a full width header, the Google icon and one featured app.

You need at least one published app on Google Play before you can create a developer page.

The page is optional. Google says that if you don't set one up, your apps still appear in your developer-specific app collections on Google Play.

That fallback is a plain list. In my sample, apps from developers with no page linked the developer name to an app list address, not to a developer page.

So the page is worth making once you have two or more apps. With one app, the store listing already does most of the work.

Here's everything the developer page asks for.

Only two images are needed. That makes the developer page one of the smallest design jobs on Google Play.

The header is the large image across the top of your developer page. Google asks for 4096 x 2304 pixels.

That's a 16 to 9 shape, the same as most TV screens and video thumbnails. If you design for video already, you can start from a familiar canvas.

It's a very large canvas. A 4096 pixel width means your header stays sharp on big desktop screens.

When I checked the page code, Google's store asked its image server for a 3840 x 2160 copy of each header. So the full size matters on large displays, even if phones show it smaller.

The header must be a JPG or a 24-bit PNG with no alpha. Alpha means a transparency layer.

In practice, that means a fully opaque image. Every pixel needs a solid color, with no see-through areas.

If you export from a design tool, turn off transparency before you save the PNG. Or save the header as a JPG, which never carries transparency.

This rule matches the feature graphic on your store listing. Google's help asks for JPEG or 24-bit PNG with no alpha there too.

Google's help page doesn't give a safe zone for the header. So I'd keep your logo and any text near the middle, in case a screen shape trims the edges.

A few habits help a header work at a glance.

1. 1Show your brand or your best known characters, not a busy collage.
2. 2Use little or no text, since your name and promotional text already sit on the page.
3. 3Pick colors that match your developer icon.
4. 4Check it at phone size before you upload.

For a game studio, your best known characters make a strong header. For an app maker, your logo on a simple background is often enough.

The developer icon is your brand's square image on the page. Google asks for 512 x 512 pixels, as a 32-bit PNG.

A 32-bit PNG can carry transparency. So unlike the header, the icon can have see-through areas.

This is the same size and format Google asks for in your app icon. Its listing help says the app icon is a 32-bit PNG with alpha, at 512 x 512 pixels, with a 1024 KB limit.

A company logo usually works better here than one app's icon. It covers every app you publish, including future ones.

Your developer page also shows a short line of promotional text. Google gives you up to 140 characters to describe your brand.

That's about one sentence. Google's own developer page uses this line: "Apps from Google to help you get the most out of your day, across all your devices." It runs to 83 characters.

You can translate the promotional text, too. In Play Console, the Add translations option lets you write it for other languages.

Keep the line about what users get from your apps. Your apps' names already appear below it.

Two more fields are optional. They're simple, but both are worth filling in.

The featured app sits near the top of your page. Google suggests choosing an app that's widely distributed in many countries, to help your page reach more people.

Your other published apps still appear on the page. Featuring one doesn't hide the rest.

The website field takes your brand or company's official site. Add it if you have one, since it gives users a direct way to learn more about you.

Google's help gives the steps. The page lives in your account settings, not in any single app's settings.

1. 1Sign in to Play Console.
2. 2Go to Manage account, then Account details, then Play developer profile.
3. 3Upload your developer icon and header image.
4. 4Add your promotional text and any translations.
5. 5Add your website and featured app if you want them.
6. 6Save your changes.

Before you add anything, Google reminds you that all content must follow Google Play policies.

Your page isn't live the moment you save it. Google gives these timings.

So plan a new page a day before you share its link. Updates to a page that's already live move faster.

I opened the store pages of 30 popular apps and games on 9 November 2026. Then I checked whether each app's developer had a developer page.

Seventeen of the 30 did. Thirteen didn't, and their name linked to a plain app list instead.

Game makers leaned toward having one. Nine of the 11 game makers in the sample had a page, against 8 of the 19 app makers.

For the 17 developers with a page, I checked the full size of each header and icon file the store served.

Every header matched Google's size exactly. That suggests the upload form holds you to it.

Google may convert files after upload, so the served format may not be what each developer sent. But both JPEG and PNG are clearly common.

The developer page and your store listing use different images. Here's how they compare.

The icons share a size, but the header is far larger than the feature graphic. It also has a different shape, at 16 to 9 rather than about 2 to 1.

So you can't just stretch your feature graphic into a header. Make each one at its own size. Our store listing asset checklist lists every image a listing needs.

We make PlayMockUp, so weigh this part with that in mind. Our tool frames app screenshots in phone and tablet mockups.

A developer page header doesn't need app screenshots. Brand art usually works better there, so a mockup isn't the right tool for it.

Your store listing is where mockups help. Framed screenshots show your app on a real device, which is what people check before they install.

You can frame your screenshots in our free mockup generator. For the icon side, our icon size guide covers Google Play and the App Store.