[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post:google-play-feature-graphic-guide":3},{"post":4,"related":119},{"id":5,"title":6,"slug":7,"excerpt":8,"status":9,"publishedAt":10,"updatedAt":11,"coverImageUrl":12,"coverImageAlt":13,"readingMinutes":14,"wordCount":15,"source":16,"focusKeywords":17,"category":22,"tags":27,"author":46,"html":48,"toc":49,"coverImageCredit":26,"coverImageCreditUrl":26,"seoTitle":100,"seoDescription":101,"faq":102,"noindex":118},"cmvxc1ygs000408kxialwq22g","Google Play Feature Graphic: Size, Rules and Design Tips","google-play-feature-graphic-guide","A Google Play feature graphic must be a 1024 × 500 px JPEG or 24-bit PNG with no alpha channel. Keep the focal point centered, use vivid colors, skip device imagery and words like \"#1\" or \"Free,\" then A\u002FB test it in Play Console.","published","2026-11-01T04:31:33.036Z","2026-11-01T04:31:33.053Z","https:\u002F\u002Frzg4dr9ak9vfbaym.public.blob.vercel-storage.com\u002Fblog\u002F2026-11\u002Fgoogle-play-feature-graphic-guide-cover-mvxc1wno-wcGO89c2QgIIK5ANyF94gQRh1LjQDh.jpg","Android phone mockups next to a Google Play feature graphic design guide",8,1780,"auto",[18,19,20,21],"google play feature graphic","feature graphic size","play store feature graphic design","google play store listing",{"id":23,"name":24,"slug":25,"description":26},"cmvxaybv0000607icji6ezyp6","App Store Optimization","app-store-optimization",null,[28,32,35,39,43],{"id":29,"name":30,"slug":31},"cmvxaybuh000207icl8qm96nh","app store screenshots","app-store-screenshots",{"id":33,"name":34,"slug":34},"cmvxaybuz000507ichpv2j0iu","aso",{"id":36,"name":37,"slug":38},"cmvxbz972000008kxigja0le6","device mockups","device-mockups",{"id":40,"name":41,"slug":42},"cmvxaybtd000107icufwenxb9","google play","google-play",{"id":44,"name":45,"slug":45},"cmvxbz975000208kxi3iyhypr","marketing",{"name":47,"avatarUrl":26},"Nexa Admin","\u003Cp>A Google Play feature graphic is a 1024 × 500 px JPEG or 24-bit PNG (no alpha channel). You need one to publish, and it is the wide banner at the top of your Google Play store listing. The ones that work keep the focal point in the center, use vivid colors and leave out device imagery and promotional words like \"#1\" or \"Free.\"\u003C\u002Fp>\n\u003Cp>This guide covers the official specs, the design rules Google publishes in Play Console Help, where the graphic shows up and how to test it. It also explains where device mockups belong on your listing, because the feature graphic is not that place.\u003C\u002Fp>\n\u003Cimg loading=\"lazy\" decoding=\"async\" src=\"https:\u002F\u002Frzg4dr9ak9vfbaym.public.blob.vercel-storage.com\u002Fblog\u002F2026-11\u002Fgoogle-play-feature-graphic-guide-mockup-mvxc1xko-v3xzFJ4hQMoQVkQ3XWGnyp1nuXkuwA.jpg\" alt=\"Pixel 9 Pro and Galaxy Z Fold7 mockups on a vivid gradient matching a Google Play feature graphic\" width=\"1200\" height=\"630\" \u002F>\n\n\u003Ch2 id=\"what-is-a-google-play-feature-graphic\">What is a Google Play feature graphic?\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>A Google Play feature graphic is a horizontal 1024 × 500 px banner that represents your app on Google Play. It covers your preview video and also appears in large-format app collections.\u003C\u002Fstrong> Think of it as your listing's billboard. Your icon handles recognition, and the feature graphic sets the mood and the value proposition.\u003C\u002Fp>\n\u003Cp>According to Google's \u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogleplay\u002Fandroid-developer\u002Fanswer\u002F9866151?hl=en\" target=\"_blank\" rel=\"noopener\">preview assets guidelines\u003C\u002Fa>, the feature graphic is used:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>as the cover image for your preview video, if you have one (users tap a play button overlaid on the graphic to watch);\u003C\u002Fli>\n\u003Cli>in large-format app collections, including ads;\u003C\u002Fli>\n\u003Cli>for games, in large-format groups of recommended games.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>So the same image has to work as a video thumbnail, a promo tile and a brand banner. Most of the design rules below come from that.\u003C\u002Fp>\n\n\u003Ch2 id=\"what-size-is-the-google-play-feature-graphic\">What size is the Google Play feature graphic?\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>The Google Play feature graphic must be exactly 1024 px wide by 500 px tall and saved as a JPEG or a 24-bit PNG without transparency.\u003C\u002Fstrong> Google's help page lists no file-size limit for it, unlike the 1024 KB cap on the app icon. A file in the low hundreds of kilobytes is still the sensible target.\u003C\u002Fp>\n\u003Cp>Here is how the feature graphic size compares with the other Google Play store listing assets, according to Google's \u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogleplay\u002Fandroid-developer\u002Fanswer\u002F1078870?hl=en\" target=\"_blank\" rel=\"noopener\">graphic assets requirements\u003C\u002Fa>:\u003C\u002Fp>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\u003Cth>Asset\u003C\u002Fth>\u003Cth>Size\u003C\u002Fth>\u003Cth>Format\u003C\u002Fth>\u003Cth>Key rule\u003C\u002Fth>\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\u003Ctd>Feature graphic\u003C\u002Ftd>\u003Ctd>1024 × 500 px\u003C\u002Ftd>\u003Ctd>JPEG or 24-bit PNG (no alpha)\u003C\u002Ftd>\u003Ctd>Required to publish; focal point in the center\u003C\u002Ftd>\u003C\u002Ftr>\n\u003Ctr>\u003Ctd>App icon\u003C\u002Ftd>\u003Ctd>512 × 512 px\u003C\u002Ftd>\u003Ctd>32-bit PNG (with alpha)\u003C\u002Ftd>\u003Ctd>Max 1024 KB; no badges suggesting rank or price\u003C\u002Ftd>\u003C\u002Ftr>\n\u003Ctr>\u003Ctd>Phone screenshots\u003C\u002Ftd>\u003Ctd>320–3840 px per side; recommended 1080 × 1920 (portrait) or 1920 × 1080 (landscape)\u003C\u002Ftd>\u003Ctd>JPEG or 24-bit PNG (no alpha)\u003C\u002Ftd>\u003Ctd>Up to 8 per device type; at least 4 recommended for apps\u003C\u002Ftd>\u003C\u002Ftr>\n\u003Ctr>\u003Ctd>Tablet \u002F Chromebook screenshots\u003C\u002Ftd>\u003Ctd>1,080–7,680 px, 16:9 or 9:16\u003C\u002Ftd>\u003Ctd>JPEG or 24-bit PNG (no alpha)\u003C\u002Ftd>\u003Ctd>Minimum of 4\u003C\u002Ftd>\u003C\u002Ftr>\n\u003Ctr>\u003Ctd>Preview video\u003C\u002Ftd>\u003Ctd>YouTube URL\u003C\u002Ftd>\u003Ctd>Public or unlisted, not monetized\u003C\u002Ftd>\u003Ctd>Only the first 30 seconds autoplay\u003C\u002Ftd>\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>A common upload error is exporting a PNG that still has an alpha channel. If Google Play Console rejects your file, flatten it onto a solid background or export it as JPEG.\u003C\u002Fp>\n\n\u003Ch2 id=\"what-does-google-recommend-for-feature-graphic-design\">What does Google recommend for feature graphic design?\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Google recommends a centered focal point, vibrant colors, no fine detail, localized text, and no device imagery or promotional language.\u003C\u002Fstrong> These points come from the \"highly recommended\" section of the Play Console preview assets guidance. Some surfaces add UI overlays, and Google warns that ignoring the placement rules can make your graphic ineligible for those formats.\u003C\u002Fp>\n\n\u003Ch3 id=\"1-keep-key-elements-out-of-the-cutoff-zones\">1. Keep key elements out of the cutoff zones\u003C\u002Fh3>\n\u003Cp>Google tells developers to \"keep prominent visuals and the focal point towards the center of the graphic.\" Your logo, app name, slogan and main UI should stay away from the edges, which can be cropped on some surfaces. Put purely decorative background elements near the edges.\u003C\u002Fp>\n\n\u003Ch3 id=\"2-design-around-the-play-button\">2. Design around the play button\u003C\u002Fh3>\n\u003Cp>If you add a preview video, Google Play places a play button over the feature graphic. Your composition still has to make sense with a circle on top of it. Put the key visual in the center area, but keep short text slightly off-center so the button doesn't cover it.\u003C\u002Fp>\n\n\u003Ch3 id=\"3-use-vivid-color-not-white-black-or-dark-gray\">3. Use vivid color, not white, black or dark gray\u003C\u002Fh3>\n\u003Cp>Google advises against \"pure white, black, or dark gray as these colors can easily blend in with Google Play's background.\" Pick a saturated brand color or a gradient that matches your icon and in-app palette. This keeps the listing consistent, and the banner won't fade into light or dark mode.\u003C\u002Fp>\n\n\u003Ch3 id=\"4-extend-the-icon-don-t-repeat-it\">4. Extend the icon, don't repeat it\u003C\u002Fh3>\n\u003Cp>Google suggests that brand elements should extend your app icon rather than duplicate it. A giant copy of the icon wastes the space. Use the graphic for what the icon can't show: the core benefit, a hero illustration or the mood of the product.\u003C\u002Fp>\n\n\u003Ch3 id=\"5-skip-fine-detail\">5. Skip fine detail\u003C\u002Fh3>\n\u003Cp>Small UI text, thin lines and busy textures \"will not be visible on many phone screens,\" Google notes. Use a few large shapes and at most one short line of copy.\u003C\u002Fp>\n\n\u003Ch3 id=\"6-leave-out-device-frames-badges-and-claims\">6. Leave out device frames, badges and claims\u003C\u002Fh3>\n\u003Cp>Google's avoid list includes device imagery, Google Play or other store badges, third-party trademarks you don't have permission to use, and performance or price language such as \"Best,\" \"#1,\" \"Free\" or \"Sale.\" Time-sensitive content is also discouraged. If you run a seasonal message, replace it as soon as the period ends.\u003C\u002Fp>\n\n\u003Ch3 id=\"7-localize-it-and-add-alt-text\">7. Localize it and add alt text\u003C\u002Fh3>\n\u003Cp>Translate any text in the graphic for each market. Leave room for longer languages, because a headline that fits in English may wrap in German. Google also asks for alt text of 140 characters or fewer that doesn't begin with \"photo of\" or \"image of.\"\u003C\u002Fp>\n\n\u003Ch2 id=\"where-do-device-mockups-belong-on-a-google-play-listing\">Where do device mockups belong on a Google Play listing?\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Device mockups belong in your screenshots and your off-store marketing, not in the feature graphic, because Google explicitly lists device imagery as something to avoid in feature graphics.\u003C\u002Fstrong> Plenty of listings ignore this rule. Following it is the easy way to keep your graphic eligible for every format.\u003C\u002Fp>\n\u003Cp>Screenshots have their own rules. For apps, Google recommends at least four screenshots at 1080 px minimum, showing real UI. It recommends prioritizing UI in the first three, keeping taglines under 20% of the image, and leaving out calls to action. A device frame around real UI fits within those rules as long as the UI stays large and readable. For when a frame helps and when it just takes up space, see \u003Ca href=\"\u002Fblog\u002Fwhen-to-use-device-mockups\">When to Use Device Mockups (and When Plain Screenshots Win)\u003C\u002Fa>. For writing short overlay text, \u003Ca href=\"\u002Fblog\u002Fapp-store-screenshot-captions-tips\">our caption tips\u003C\u002Fa> also apply to Google Play.\u003C\u002Fp>\n\u003Cp>Mockups are also useful around the listing: on your landing page, in launch posts, in press kits and as frames in the YouTube preview video. Google suggests the video and the feature graphic share the same palette and story.\u003C\u002Fp>\n\n\u003Ch2 id=\"how-to-build-matching-play-store-assets-with-mockiso\">How to build matching Play Store assets with mockiso\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Use a design tool such as Figma for the flat 1024 × 500 px feature graphic. Use mockiso for the device-framed screenshots and marketing images that sit around it.\u003C\u002Fstrong> Here is a workflow that keeps everything in the same visual style:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Pick your brand gradient first.\u003C\u002Fstrong> Choose a vivid color pair that matches your icon. Use it as the feature graphic background and reuse the same colors everywhere else.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Create a project in mockiso.\u003C\u002Fstrong> \u003Ca href=\"\u002Fregister\">Sign up\u003C\u002Fa>, click New project and choose an Android device such as Pixel 9 Pro, Galaxy S24 or a foldable like Galaxy Z Fold7. The full list is on the \u003Ca href=\"\u002F#devices\">devices section\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Drop in your screenshot.\u003C\u002Fstrong> Click to upload, drag and drop, or paste with Ctrl\u002FCmd+V.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Choose an angle.\u003C\u002Fstrong> Front works best for store screenshots where the UI must stay readable. Hero left\u002Fright or float suit social posts and your website.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Match the backdrop.\u003C\u002Fstrong> Set a gradient backdrop with the same colors as your feature graphic, or export with a transparent background and place the device in your own layout.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Add a short caption if needed.\u003C\u002Fstrong> Use the optional headline and subline, and keep the text well under Google's 20% guideline.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Use duo or trio layouts\u003C\u002Fstrong> to show consecutive screens in a single marketing image.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Export.\u003C\u002Fstrong> Choose a store or social canvas size preset, then export PNG, JPEG or WebP. For Google Play, upload a JPEG or a PNG without transparency.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Everything renders in the browser, so you can redo all angles after a UI update in minutes. 2× export, batch ZIP export and the watermark-free output are on paid plans; see \u003Ca href=\"\u002Fpricing\">pricing\u003C\u002Fa> for current limits.\u003C\u002Fp>\n\n\u003Ch2 id=\"how-do-you-a-b-test-a-google-play-feature-graphic\">How do you A\u002FB test a Google Play feature graphic?\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>You can A\u002FB test a feature graphic with store listing experiments in Google Play Console, comparing up to two variants against your current listing.\u003C\u002Fstrong> According to \u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogleplay\u002Fandroid-developer\u002Fanswer\u002F12053285?hl=en\" target=\"_blank\" rel=\"noopener\">Google's experiments documentation\u003C\u002Fa>, default graphics experiments can test the icon, feature graphic and screenshots. Localized experiments can also include descriptions.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Where:\u003C\u002Fstrong> Play Console → Grow users → Store presence → Store listings, then click Set up in the Experiment column.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Limits:\u003C\u002Fstrong> Per app, you can run one default graphics experiment or up to five localized experiments at the same time.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>What to test:\u003C\u002Fstrong> Change one thing per variant: a different hero visual, a warmer or cooler background, or text versus no text. If you change several things at once, you won't know which one made the difference.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Let the experiment run until Play Console reports a clear result. Weekday and weekend traffic often behave differently, so a few days of data can mislead.\u003C\u002Fp>\n\n\u003Ch2 id=\"pre-upload-checklist\">Pre-upload checklist\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Exactly 1024 × 500 px, JPEG or 24-bit PNG, no alpha channel.\u003C\u002Fli>\n\u003Cli>Logo, app name and key visual in the central area, out of the edge cutoff zones.\u003C\u002Fli>\n\u003Cli>Readable even with a play button over the center (if you have a video).\u003C\u002Fli>\n\u003Cli>Vivid background, not pure white, black or dark gray.\u003C\u002Fli>\n\u003Cli>No device frames, store badges, \"#1,\" \"Best,\" \"Free\" or \"Sale.\"\u003C\u002Fli>\n\u003Cli>Text localized for each market; alt text of 140 characters or fewer.\u003C\u002Fli>\n\u003Cli>Colors consistent with the icon, screenshots and preview video.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"key-takeaways\">Key takeaways\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>The Google Play feature graphic is 1024 × 500 px, JPEG or 24-bit PNG with no transparency, and it is required to publish.\u003C\u002Fli>\n\u003Cli>It works as the preview video cover and appears in large-format collections, so center the focal point and design around the play button.\u003C\u002Fli>\n\u003Cli>Google recommends vivid colors and advises against pure white, black or dark gray, device imagery, store badges and claims like \"#1\" or \"Free.\"\u003C\u002Fli>\n\u003Cli>Put device mockups in screenshots and off-store marketing, and keep the feature graphic flat and brand-led.\u003C\u002Fli>\n\u003Cli>Test up to two feature graphic variants at a time with Play Console store listing experiments.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"conclusion\">Conclusion\u003C\u002Fh2>\n\u003Cp>A strong Google Play feature graphic is mostly about restraint: one clear visual, one color story, nothing important near the edges. Pair it with screenshots in the same palette and the listing looks consistent from the banner down to the last screenshot.\u003C\u002Fp>\n\u003Cp>When you're ready to create the device-framed screenshots and marketing images, \u003Ca href=\"\u002Fregister\">start a free mockiso trial\u003C\u002Fa>. Every new account gets 24 hours of Pro, no card required.\u003C\u002Fp>",[50,54,57,60,64,67,70,73,76,79,82,85,88,91,94,97],{"id":51,"text":52,"level":53},"what-is-a-google-play-feature-graphic","What is a Google Play feature graphic?",2,{"id":55,"text":56,"level":53},"what-size-is-the-google-play-feature-graphic","What size is the Google Play feature graphic?",{"id":58,"text":59,"level":53},"what-does-google-recommend-for-feature-graphic-design","What does Google recommend for feature graphic design?",{"id":61,"text":62,"level":63},"1-keep-key-elements-out-of-the-cutoff-zones","1. Keep key elements out of the cutoff zones",3,{"id":65,"text":66,"level":63},"2-design-around-the-play-button","2. Design around the play button",{"id":68,"text":69,"level":63},"3-use-vivid-color-not-white-black-or-dark-gray","3. Use vivid color, not white, black or dark gray",{"id":71,"text":72,"level":63},"4-extend-the-icon-don-t-repeat-it","4. Extend the icon, don't repeat it",{"id":74,"text":75,"level":63},"5-skip-fine-detail","5. Skip fine detail",{"id":77,"text":78,"level":63},"6-leave-out-device-frames-badges-and-claims","6. Leave out device frames, badges and claims",{"id":80,"text":81,"level":63},"7-localize-it-and-add-alt-text","7. Localize it and add alt text",{"id":83,"text":84,"level":53},"where-do-device-mockups-belong-on-a-google-play-listing","Where do device mockups belong on a Google Play listing?",{"id":86,"text":87,"level":53},"how-to-build-matching-play-store-assets-with-mockiso","How to build matching Play Store assets with mockiso",{"id":89,"text":90,"level":53},"how-do-you-a-b-test-a-google-play-feature-graphic","How do you A\u002FB test a Google Play feature graphic?",{"id":92,"text":93,"level":53},"pre-upload-checklist","Pre-upload checklist",{"id":95,"text":96,"level":53},"key-takeaways","Key takeaways",{"id":98,"text":99,"level":53},"conclusion","Conclusion","Google Play Feature Graphic: Size, Rules & Design Tips","Google Play feature graphic specs (1024 × 500 px), Google's design rules, the play-button overlay and how to A\u002FB test it. Get a checklist before you upload.",[103,106,109,112,115],{"q":104,"a":105},"Is the feature graphic required on Google Play?","Yes. Google Play Console asks for a 1024 × 500 px feature graphic as part of the main store listing graphics. It is used even if you never add a preview video, for example in large-format collections and ads.",{"q":107,"a":108},"Can I use a PNG with a transparent background for the feature graphic?","No. Google requires a JPEG or a 24-bit PNG without an alpha channel. Flatten the image onto a solid or gradient background before uploading, or export it as JPEG.",{"q":110,"a":111},"Should I put text on my Google Play feature graphic?","Short text is allowed, but keep it minimal, readable on small phone screens and localized for every market. Avoid performance or price claims such as \"Best,\" \"#1,\" \"Free\" or \"Sale,\" which Google lists as things to avoid.",{"q":113,"a":114},"Does the feature graphic affect search ranking on Google Play?","Google does not document any link between the feature graphic and search ranking. Its value is visual: it shapes first impressions and conversion on the listing and in large-format placements. Measure its impact with store listing experiments.",{"q":116,"a":117},"Do I need a different feature graphic for each language?","Google recommends localizing graphic and branding text for different markets and languages. If your graphic has no text, one version can work everywhere. If it has a headline, create translated versions and attach them to the matching localized listings.",false,[120,147,172],{"id":121,"title":122,"slug":123,"excerpt":124,"status":9,"publishedAt":125,"updatedAt":126,"coverImageUrl":127,"coverImageAlt":128,"readingMinutes":129,"wordCount":130,"source":16,"focusKeywords":131,"category":136,"tags":140,"author":146},"cmvxfbv3s000008laxxudp6p6","App Store Screenshot Trends 2026: 8 Styles Worth Using","app-store-screenshot-trends-2026","The biggest App Store screenshot trends in 2026 are outcome-first hero frames, panoramic sets, angled 3D devices, frameless UI crops, dark mode frames, Liquid Glass UI, multi-device sets and bold color blocking. Use each one only where store rules allow it.","2026-11-01T06:03:14.087Z","2026-11-01T06:03:14.105Z","https:\u002F\u002Frzg4dr9ak9vfbaym.public.blob.vercel-storage.com\u002Fblog\u002F2026-11\u002Fapp-store-screenshot-trends-2026-cover-mvxfbswd-UOXv8F72iD9KsroJvKVVlI6aS3E1h8.jpg","Designer reviewing app store screenshot trends on a smartphone",7,1706,[132,133,134,135],"app store screenshot trends","device mockup styles","app screenshot design","google play screenshots",{"id":137,"name":138,"slug":139,"description":26},"cmvxbz973000108kxliuusz0h","Design","design",[141,142,143,144,145],{"id":29,"name":30,"slug":31},{"id":33,"name":34,"slug":34},{"id":36,"name":37,"slug":38},{"id":40,"name":41,"slug":42},{"id":44,"name":45,"slug":45},{"name":47,"avatarUrl":26},{"id":148,"title":149,"slug":150,"excerpt":151,"status":9,"publishedAt":152,"updatedAt":153,"coverImageUrl":154,"coverImageAlt":155,"readingMinutes":129,"wordCount":156,"source":16,"focusKeywords":157,"category":162,"tags":163,"author":171},"cmvxdcd9n000108ie52zhuyou","App Store Screenshot Rejection: 12 Mistakes to Fix First","app-store-screenshot-rejection-mistakes","Most App Store screenshot rejections come from a few fixable mistakes: splash or login screens instead of the app in use, prices or \"free\" claims, other-platform imagery, real user data, and wrong sizes or transparent PNGs. Google Play adds bans on rankings, awards and promo text.","2026-11-01T05:07:38.406Z","2026-11-01T05:07:38.411Z","https:\u002F\u002Frzg4dr9ak9vfbaym.public.blob.vercel-storage.com\u002Fblog\u002F2026-11\u002Fapp-store-screenshot-rejection-mistakes-cover-mvxdcaal-ub0WBB8VDHnDSXyybdr1RF0PiD9W1e.jpg","iPhone and Pixel 3D mockups illustrating how to avoid an App Store screenshot rejection",1671,[158,159,160,161],"app store screenshot rejection","guideline 2.3.3","google play screenshot policy","app screenshot checklist",{"id":23,"name":24,"slug":25,"description":26},[164,165,166,167,168],{"id":29,"name":30,"slug":31},{"id":33,"name":34,"slug":34},{"id":36,"name":37,"slug":38},{"id":40,"name":41,"slug":42},{"id":169,"name":170,"slug":170},"cmvxce04r000708kx59ilvqys","launch",{"name":47,"avatarUrl":26},{"id":173,"title":174,"slug":175,"excerpt":176,"status":9,"publishedAt":177,"updatedAt":178,"coverImageUrl":179,"coverImageAlt":180,"readingMinutes":14,"wordCount":181,"source":16,"focusKeywords":182,"category":187,"tags":188,"author":194},"cmvxd9hwr000008ieqz0egwe3","3D vs Flat Mockups: When Each Style Works Best","3d-vs-flat-mockups","Use flat mockups when the interface has to be read: the first App Store screenshots, documentation and UI walkthroughs. Use 3D mockups when you need atmosphere and depth: hero images, launch posts, landing pages and later screenshots in the set.","2026-11-01T05:05:24.452Z","2026-11-01T05:05:24.459Z","https:\u002F\u002Frzg4dr9ak9vfbaym.public.blob.vercel-storage.com\u002Fblog\u002F2026-11\u002F3d-vs-flat-mockups-cover-mvxd9ftz-c3k0Epl1aqu4M8NidiHM2Fpi44N79r.jpg","Designer comparing 3D vs flat mockups of a mobile app on a smartphone",1912,[183,184,185,186],"3d vs flat mockups","3d device mockups","flat device mockup","app screenshot mockup style",{"id":137,"name":138,"slug":139,"description":26},[189,190,191,192,193],{"id":29,"name":30,"slug":31},{"id":33,"name":34,"slug":34},{"id":36,"name":37,"slug":38},{"id":40,"name":41,"slug":42},{"id":44,"name":45,"slug":45},{"name":47,"avatarUrl":26}]