Play Storeフィーチャーグラフィック ガイド

The feature graphic is a mandatory asset for any app published on the Google Play Store. It appears as a large banner at the very top of your store listing page, above your screenshots and description. When your app is featured in curated collections, editorial picks, or promotional placements within the Play Store, the feature graphic is often the only visual element shown alongside your app name and icon.

Think of the feature graphic as a billboard for your app. It needs to communicate your value proposition instantly, without requiring the viewer to read small text or study fine details. The graphic is displayed at various sizes depending on the context: full width on your listing page, smaller thumbnails in promotional placements, and sometimes cropped to different aspect ratios for editorial features. This variability means your design must work well at multiple sizes and crops.

Unlike screenshots, which show your actual app interface, the feature graphic is a marketing asset. It should convey the mood, purpose, and personality of your app rather than demonstrate specific features. Games tend to use character art or dramatic scenes. Productivity apps use clean, abstract compositions with a strong headline. Social apps often feature lifestyle photography or illustrations of people connecting. The most effective feature graphics share one trait: they tell you what the app is about within a single glance.

Google requires the feature graphic to be exactly 1024 x 500 pixels. This is a landscape format with a roughly 2:1 aspect ratio. The file must be in JPEG or 24-bit PNG format with no alpha transparency. There is no official maximum file size listed, but keeping it under 1 MB ensures fast loading across all devices and network conditions.

The most important technical consideration is the safe zone. Although you upload a 1024 x 500 image, Google crops and scales this graphic differently depending on where it is displayed. On your listing page, users see the full graphic. In promotional placements and curated collections, the graphic may be cropped to a 16:9 or even narrower aspect ratio, cutting off the left and right edges. To handle this safely, keep all critical content (your app name, tagline, key visual elements) within the center 860 x 480 area. Anything outside that zone risks being cut off.

If your app has a promo video on YouTube, the feature graphic also serves as the video thumbnail overlay. A play button icon appears centered on the graphic, so avoid placing important text or visual elements in the exact center where the play button will cover them. Design with the assumption that a circular play icon will sit in the middle of your image. Place your headline and key visuals slightly above or below center, or to the left and right of center, to ensure nothing important gets hidden behind the play button.

The strongest feature graphics follow a simple formula: one clear visual focus, a short headline, and a bold color palette that stands out in the Play Store feed. Resist the urge to cram multiple messages, screenshots, or feature lists into a single 1024 x 500 image. At the sizes where this graphic typically appears, complexity becomes noise.

Start with your color palette. Use your app brand colors as the primary background, but increase saturation and contrast compared to what you use in the app itself. The Play Store environment is visually busy, with dozens of apps competing for attention on every screen. A muted or low-contrast feature graphic will fade into the background. Bold, vibrant colors grab attention. Dark backgrounds with bright accent colors tend to perform well, as do gradient backgrounds that create visual depth without distraction.

For typography, use a single headline of 3 to 6 words. This should be your core value proposition or a compelling tagline. Set the text in a bold sans-serif font at a size large enough to read comfortably on a phone screen. Test readability by viewing your design at 50% zoom on your monitor; if the text becomes hard to read at that size, it is too small for mobile devices. Avoid script fonts, thin weights, or decorative typefaces that sacrifice legibility for style.

Include a visual element that represents your app: an app icon, a simplified device mockup showing one key screen, a character illustration, or a relevant object. This visual should complement the headline, not compete with it. Place text and visual elements on opposite sides of the composition to create balance. If your headline is on the left, place the visual element on the right, and vice versa. This layout naturally guides the eye across the graphic and prevents the design from feeling lopsided or cluttered.

You have several options for creating a Play Store feature graphic, ranging from manual design tools to dedicated generators that produce results in minutes.

Canva is the most accessible option for non-designers. It offers pre-built templates specifically sized for Google Play feature graphics. You select a template, swap in your app name, tagline, and brand colors, and export. The templates are professionally designed and cover common styles like gradient backgrounds with device mockups, illustrated scenes, and minimalist text-based layouts. The free tier is sufficient for most needs, though the Pro tier unlocks additional templates and assets.

Figma and Adobe Express are better choices if you want more design control. Figma lets you create the graphic from scratch with precise positioning, custom typography, and exportable components. Adobe Express provides a similar template-based workflow to Canva but with tighter integration into the Adobe ecosystem. Both tools require more design knowledge than Canva but produce more customizable results.

ScreenMagic generates feature graphics as part of its AI-powered app store asset creation workflow. You provide your app information and brand assets, and the tool produces a feature graphic alongside your screenshots, ensuring visual consistency across your entire Play Store listing. This integrated approach is valuable because a feature graphic that visually matches your screenshot style creates a more cohesive and professional listing page. When the feature graphic, screenshots, and icon all share a consistent color palette and design language, users perceive higher quality and are more likely to install.

For developers who prefer code-based solutions, tools like Bannerbear and Placid offer API-driven graphic generation. You define a template with variables (app name, tagline, icon URL, colors) and the API generates the image programmatically. This approach is useful for apps that need to generate feature graphics at scale, such as white-label platforms or app builders that create listings for multiple apps.

Google requires a feature graphic at exactly 1024 x 500 pixels, no exceptions. The accepted formats are JPEG or 24-bit PNG with no alpha transparency, since the Play Store flattens any transparency to white before display. There is no published hard limit on file size, but Google recommends keeping the file under 1 MB so the banner loads instantly on 3G networks in markets like India, Indonesia and Brazil. A 200 to 600 KB file is the sweet spot, large enough to keep gradients smooth but small enough to load before users scroll.

The single most important constraint is the safe zone. Although you upload a 1024 x 500 image, Play Store cropping is aggressive and unpredictable. On the listing page users see the full banner, but in Featured collections, top charts, search results and the Apps & Games tab, the graphic is recropped to anything from 16:9 to 4:3. Keep all critical content (logo, headline, app icon, character art) inside a central 924 x 400 zone, leaving 50 px of buffer on the left and right edges and 50 px top and bottom. Anything outside that rectangle will eventually be cut off on at least one surface.

If you attach a YouTube promo video, the feature graphic also acts as the video thumbnail with a 96 x 96 px play button rendered in the geometric center. Avoid putting your logo or headline at coordinates 464 to 560 horizontal and 202 to 298 vertical, that area is dead pixels behind the play icon. Headspace, Calm and Notion all push their wordmarks to the upper-left or lower-right quadrant for exactly this reason. Verify your design by viewing it at 360 px wide on a phone, anything that fails the squint test at that size fails on the Play Store.

You do not need a designer or Photoshop license to ship a clean 1024 x 500 banner. Canva offers around 80 free Google Play feature graphic templates pre-sized to the exact dimensions, searchable under "Google Play feature graphic" in the template library. Most include the central safe zone marked as a guide layer, so you can drop your logo, swap brand colors and export a Play-ready PNG in under 10 minutes. The free tier is enough, the Pro tier mainly unlocks stock photography and brand kits.

Figma has community plugins like "App Store Screenshot" and "Mockup Plugin" that include 1024 x 500 frames with safe zone overlays. Figma is the better option if you already maintain a design system, since you can pull tokens from your existing styles and stay consistent with the rest of your brand. Adobe Express sits between Canva and Figma, free templates with more typography control than Canva but less flexibility than Figma.

For a faster path that keeps the feature graphic visually consistent with your screenshots and icon, ScreenMagic generates a 1024 x 500 banner alongside your full Play Store asset set from a single brief. Once you have a draft, the [Screenshot Resizer](/tools/screenshot-resizer) converts source assets to exact 1024 x 500 px without manual cropping, and the [Listing Preview](/tools/listing-preview) shows you exactly how the banner will render in the live Play Store layout next to your icon, screenshots and short description before you upload anything to Google Play Console. That preview catches around half of the safe zone mistakes that would otherwise only show up after publish.

Google does not publish an official rejection list for feature graphics, but the Play Console review team flags the same five issues over and over. Knowing them in advance saves a 48-hour review cycle. The most common rejection is text that is too small to read, anything under 36 px on the 1024 x 500 canvas tends to fail the readability bar Google applies for accessibility. Keep headlines at 60 to 90 px and limit body text to a single subline at 32 to 40 px.

The second frequent rejection is low contrast between text and background. Google enforces a minimum 4.5:1 contrast ratio loosely on feature graphics, light gray text on a white background or thin colored text on a busy gradient gets pulled. Run your design through a contrast checker before upload. The third issue is copyrighted material, character art that resembles Mario, Marvel logos, sports team marks or any movie still will trigger an automated takedown. Use original illustrations or properly licensed stock.

The fourth rejection bucket is anything that looks like an ad. Banners with "DOWNLOAD NOW", "FREE LIMITED TIME", giant arrow callouts, fake notification badges or simulated 5-star rating widgets are treated as deceptive marketing and removed. The Play Store wants the banner to feel editorial, not promotional. The fifth issue is brand misuse, using the Google Play logo, Android robot, Apple App Store badge or Google's own product names like "Gmail" or "YouTube" inside your feature graphic without permission. Apps from Duolingo and Spotify avoid every one of these traps, their feature graphics show only their own brand assets and a single short headline.

The feature graphic is not just decoration, it is the single largest visual on the listing above the fold and the only image visible in Featured banners on the Play Store home tab. Internal A/B tests run by larger ASO agencies consistently show that swapping the feature graphic alone moves install conversion rate by 7 to 18 percent, similar in magnitude to swapping the first screenshot. For apps that get most of their organic traffic from Featured placements rather than search, the feature graphic can move conversion by 25 percent or more.

Three patterns drive the lift. First, headline clarity. Banners with a benefit-led headline of 4 to 8 readable words ("Sleep better tonight" for Calm, "Learn a language for free" for Duolingo) outperform banners with no text or a generic tagline by roughly 22 percent in mid-funnel install rate. Second, character or product focus. Banners that feature a single recognizable element (the Headspace meditation character, the Notion logo on a clean gradient, the Spotify wordmark with a music wave) outperform busy collages because the eye locks onto one anchor in under 800 ms.

Third, color contrast against the Play Store chrome. The Play Store uses a white or near-white background on most surfaces, so feature graphics with a dark or saturated color block in the center grab the eye. Banners that use white or pale backgrounds blend into the page and get scrolled past. When you run Play Store Experiments under the "Graphics" experiment type, the feature graphic is one of the variables you can isolate, run a 50/50 split for at least 7 days with 1,000+ visitors per arm before declaring a winner. Most teams skip this test because the feature graphic feels like a "nice to have", that is exactly why fixing it is one of the highest ROI ASO actions for an app under 100k installs per month.

Google Play serves 190+ countries and the feature graphic can be localized for every store listing language you publish, yet roughly 80 percent of apps ship the same English banner everywhere. Localizing the banner for your top 5 to 10 markets typically lifts install conversion by 10 to 20 percent in non-English locales, on par with localizing screenshots. The 1024 x 500 canvas does not change, but the text inside it must adapt.

Translation expansion is the biggest practical issue. A 5-word English headline like "Track every penny daily" becomes 7 to 9 words in German ("Verfolge jeden Cent jeden Tag taglich") and the original 60 px font no longer fits inside the 924 x 400 safe zone. Plan for 30 percent text expansion when designing the master file, leaving slack on the right side of the headline. French and Spanish run roughly 20 percent longer than English. Russian sits at parity but uses Cyrillic glyphs that need a font with proper coverage. Arabic and Hebrew are right-to-left, you must mirror the entire layout, not just translate the text, so the headline anchor moves from the upper-left to the upper-right of the safe zone.

Japanese and Korean go the other direction. Strings are 30 to 50 percent shorter in character count but each glyph needs more vertical breathing room and a CJK-aware font like Noto Sans CJK or Pretendard. Cramming Hiragana, Katakana and Kanji into a 60 px Latin-style font produces blurry, hard to scan text that looks amateurish to local users. Apps like LINE, Kakao and Mercari adjust their feature graphic font weight and size by locale, not just the string. ScreenMagic auto-generates locale variants of your feature graphic from translated input strings, handling RTL mirroring and CJK font swaps so you do not have to maintain 10 separate Figma files for the same banner.