Google Playストア スクリーンショット完全ガイド

Google Play accepts screenshots in JPEG or 24-bit PNG format (no alpha transparency). Each screenshot must have a minimum dimension of 320 pixels and a maximum of 3840 pixels on any side. The aspect ratio cannot exceed 2:1, meaning the longer side can be at most twice the shorter side. You must upload a minimum of two screenshots and can upload up to eight per device type.

For phone screenshots in 2026, design at 1080 x 2400 pixels. This resolution matches the Pixel 9, Samsung Galaxy S25, and the vast majority of modern Android phones. The older 1080 x 1920 standard still works technically but looks dated, especially if you use device frames. Modern Android phones have taller displays, and your screenshots should reflect that.

For tablets, Google supports 7-inch (1200 x 1920) and 10-inch (1600 x 2560) sizes in separate upload slots. For Chromebooks, use 1920 x 1080 in landscape orientation. For Android TV, use 1920 x 1080 landscape. For Wear OS, use 384 x 384 pixels. Each form factor has its own section in the Google Play Console, and providing screenshots for every form factor your app supports improves your listing quality score.

The feature graphic is a special asset at exactly 1024 x 500 pixels. It appears at the top of your listing page, in search results, and in various browse placements throughout the Play Store. If you add a promo video, the feature graphic becomes the video thumbnail. Despite its prominent placement, the feature graphic is the most frequently neglected visual asset on Google Play. Invest real design effort here.

Google also accepts a promo video (YouTube URL), a TV banner (1280 x 720), and a Daydream 360 stereoscopic image if applicable. While not all of these are required, providing a complete set of visual assets signals quality to both Google's algorithms and potential users.

Play Store screenshot design follows many of the same principles as App Store design, but with important platform-specific considerations. Android users have different expectations, and the Play Store displays screenshots differently than the App Store.

Use Android device frames exclusively. This is the most common mistake developers make on Google Play: recycling iOS screenshots with iPhone frames. Android users notice immediately, and it signals that the Android version of your app is an afterthought. Use Pixel 9 or Samsung Galaxy S25 frames to show your app is optimized for the platform. If you don't want device frames, use a frameless layout with a branded background.

Material Design aesthetics resonate with Android users. You don't need to follow Material Design guidelines strictly, but incorporating rounded corners, subtle shadows, and Google's design language creates a native feel. Screenshots that look distinctly iOS-styled on Google Play create subconscious friction for Android users who are accustomed to Material Design patterns.

Your first two screenshots carry the most weight. In Play Store search results, users typically see only two to three screenshots in a horizontal scroll. These initial frames must communicate your app's core value instantly. Lead with your strongest benefit, not a feature tour. Write a clear headline in three to six words and pair it with a compelling app screen.

Design with the feature graphic in mind. The feature graphic (1024 x 500) appears above your screenshots on your listing page and in various browse contexts. It should complement your screenshot style rather than feel disconnected. Use the same color palette and typography to create visual coherence. The feature graphic is your app's billboard, so make it bold, clear, and benefit-focused.

Consider the diversity of Android screens. Your screenshots need to look good on everything from a budget phone with a 720p display to a flagship with a 1440p panel. Design at the recommended resolutions and avoid placing critical text or content at extreme edges where different aspect ratios might crop it.

The feature graphic is unique to Google Play and has no equivalent on the Apple App Store. At 1024 x 500 pixels in landscape format, it appears prominently at the top of your listing, in search results, in "similar apps" carousels, and in editorial features. For many users, the feature graphic is the first visual impression of your app.

Treat your feature graphic as a billboard advertisement. It needs to communicate your app's value proposition in a single glance. Include three elements: a compelling headline (three to five words), a visual element that represents your app (icon, product shot, or key UI element), and a clean background that makes both the text and visual pop.

Don't just slap your app icon on a solid color and call it done. This lazy approach is used by roughly 40% of apps on Google Play, which means doing anything more creative immediately sets you apart. Show your app in action, feature a key benefit, or create an aspirational scene that represents what users get from your app.

Text on the feature graphic should be large enough to read at thumbnail size. In search results, the feature graphic is displayed quite small. If your headline disappears at reduced size, increase the font size and simplify the layout. Test readability by viewing your feature graphic at 50% zoom on your monitor.

If you include a promo video, your feature graphic becomes the video thumbnail with a play button overlay. Design for this context by keeping the center of the graphic clear of critical text (the play button will cover it) and ensuring the graphic still communicates your message even with the video overlay.

Update your feature graphic alongside your screenshots, at least quarterly. Seasonal variants can be effective, especially for lifestyle, fitness, and shopping apps. A feature graphic that matches the current season or cultural moment feels timely and signals active development.

Google Play's Store Listing Experiments are one of the most powerful yet underutilized tools available to Android developers. They let you A/B test your listing elements with real user traffic, completely free, and with proper statistical analysis. If you are not running experiments, you are leaving conversion on the table.

To set up an experiment, go to the Google Play Console, navigate to "Store presence" and select "Store listing experiments." Create a new experiment, choose what you want to test (graphics, text, or both), and upload your variant assets. Google automatically splits traffic between your control and variants, and you can run up to five variants simultaneously.

Start by testing your first screenshot. Create a variant with a different headline message and measure the conversion impact. This single test can improve your conversion by 10-25%, translating directly into more downloads. After the first screenshot, test your feature graphic, then your screenshot order, then background colors and visual style.

Each experiment needs sufficient traffic to reach statistical significance. Google requires at least 1,000 visitors per variant for meaningful results. For apps with 5,000 daily listing visitors, a simple A/B test (control vs. one variant) reaches significance in about three to five days. Lower-traffic apps may need two to four weeks.

Google shows results as estimated conversion rate changes with confidence intervals. Wait for the confidence level to reach 90% or higher before applying the winner. Ending experiments early based on preliminary data is tempting but leads to false positives. Let the math do its job.

Custom store listings take experimentation further. You can create entirely different listing pages for users coming from specific campaigns, countries, or pre-registration lists. If you run paid acquisition campaigns, create custom listings that match your ad creative. The consistency between ad and listing dramatically improves conversion for paid traffic.

Build experimentation into your routine. Run at least one experiment per quarter, always have a next test ready, and document every result. Over twelve months, four to eight experiments can compound into a 30-50% cumulative conversion improvement.

Certain mistakes appear repeatedly in Play Store listings and are easy to fix once you identify them. Eliminating these errors is often the fastest path to improving your listing performance.

Using iPhone device frames on Google Play is the most damaging and most common mistake. It tells Android users that the developer prioritizes iOS and may not care about the Android experience. Some users will skip your app entirely based on this single visual cue. Always use Pixel, Samsung Galaxy, or generic Android device frames.

Uploading low-resolution screenshots makes your listing look amateurish on modern high-resolution Android displays. Because Google accepts a wide resolution range, some developers upload screenshots that were appropriate five years ago but look blurry on current devices. Always use 1080 x 2400 pixels minimum for phone screenshots. There is no reason to go lower in 2026.

Neglecting the feature graphic is a massive missed opportunity. It appears in search results, "similar apps" sections, and editorial placements. A lazy logo-on-solid-color feature graphic wastes your most visible marketing real estate. Invest real design effort to make your feature graphic as compelling as your best screenshot.

Skipping tablet screenshots hurts your ranking on tablets and Chromebooks. Google's algorithm favors apps that provide device-specific screenshots for all supported form factors. Even if your tablet UI is the same as your phone UI, provide screenshots at tablet resolution. This small effort signals platform commitment and gives you an edge over competitors who skip it.

Copying iOS screenshots without adaptation goes beyond just device frames. iOS-styled UI elements, Apple system fonts, and iOS-specific features shown in Play Store screenshots create a jarring experience for Android users. Adapt your screenshots to feel native to the Android ecosystem. Show Android-specific UI patterns, use appropriate system fonts, and highlight Android-relevant features.

Not using Store Listing Experiments is leaving free performance gains on the table. Google provides this testing tool at no cost, with real user traffic and proper statistical analysis. Even one test per quarter testing your first two screenshots compounds into meaningful conversion improvements over a year. There is simply no good reason to skip it.