Google Play 스크린샷 리젝트 원인 및 해결 체크리스트 (2026)
Google Play screenshot rejection usually comes down to one of three problems: the file does not meet Google's asset requirements, the screenshot does not accurately represent the app experience, or the store listing violates metadata and promotion policies.
This guide was fact-checked on June 17, 2026 against Google's preview asset requirements, metadata policy, store listing best practices, and policy violation resubmission guidance.
Start With the Exact Enforcement Message
Do not guess. Google says to read the policy named in the enforcement message, check Notifications and email, then make the required changes. If the issue is a screenshot or metadata violation, the fix may be only a store listing asset update. If the issue is tied to the app itself, you may need a compliant app bundle as well.
Common Google Play Screenshot Rejection Reasons
1. The screenshots are the wrong format or dimensions
Google Play requires at least two screenshots across device types to publish a store listing. General screenshot files must be JPEG or 24-bit PNG with no alpha channel, have a minimum dimension of 320 px, have a maximum dimension of 3840 px, and the longest side cannot be more than twice the shortest side.
2. The image is blurry, stretched, compressed, or rotated wrong
Google's guidance says screenshots should be high-quality images with the proper aspect ratio and should not be blurry, distorted, pixelated, stretched, compressed, upside down, sideways, or skewed.
3. The screenshots do not show the actual in-app experience
Google recommends that screenshots demonstrate the actual in-app or in-game experience, focusing on core features and content. Avoid using generic marketing art as a substitute for the app UI.
4. Text overlays violate metadata rules
Google warns against screenshots and store graphics that include store performance claims, ranking claims, accolades, price or promotional information, or calls to action like "download now" or "install now." Keep screenshot taglines factual and tied to app functionality.
5. The screenshot text is too small or takes over the image
Google says taglines should be used only if necessary and should not take up more than 20% of the image. It also warns against small text and backgrounds that compete with the text because they may not be visible on many phone screens.
6. The screenshots are not localized with the listing
Google recommends localizing graphic and branding text for different markets. Its store listing best practices also say that for screenshots containing text, you should provide separate screenshots and promotional videos for each language you support.
7. Device-specific screenshots do not follow device-specific rules
Some Google Play surfaces have extra requirements. For example, Wear OS screenshots should show only the app interface, avoid device frames and additional text or backgrounds, use a 1:1 aspect ratio, and be at least 384 x 384 px. Android TV requires at least one TV screenshot before publishing a TV app, and Android XR requires 4 to 8 screenshots with an 8:5 aspect ratio.
8. The listing uses restricted or misleading content
Google's metadata policy covers screenshots and promotional images. It prohibits misleading, irrelevant, excessive, improperly formatted, or inappropriate metadata. It also warns against unrelated keyword blocks, unattributed testimonials, misleading symbols, and unsuitable public listing imagery.
How to Fix the Rejection
- Open the enforcement message and identify the exact violated policy.
- Remove non-compliant screenshots from every affected store listing and locale.
- Export compliant JPEG or 24-bit PNG files with no alpha channel.
- Check dimensions, aspect ratio, rotation, and visual quality.
- Replace marketing-only images with actual in-app or in-game screens.
- Remove ranking, award, price, discount, and install-call-to-action claims.
- Localize screenshot text for each translated listing.
- Update any affected release tracks if the policy issue is tied to an app bundle.
Do Rejections Hurt Your Developer Account?
Google says rejections do not impact the standing of your Google Play Developer account, and if an update to an existing app is rejected, the previously published version remains available on Google Play. However, Google also warns not to republish a rejected app until the policy violation has been fixed. Repeated app rejections or removals can contribute to more serious enforcement.
Pre-Upload Checklist
- At least two screenshots across device types are present.
- Files are JPEG or 24-bit PNG with no alpha channel.
- Dimensions are within 320 px and 3840 px, with a valid aspect ratio.
- Screenshots show actual app or game experience.
- No ranking, award, install, discount, or price claims appear in graphics.
- Text overlays are short, large, and localized.
- Special device surfaces follow their own rules.
- All tracks and listings are updated before resubmission.
관련 ASO 가이드
- Google Play graphics checklist: audit screenshots, feature graphics, app icons, and preview videos together.
- Google Play feature graphic size: fix feature graphic dimensions, file type, and layout problems.
- Google Play screenshot requirements: confirm file format, dimensions, and device-specific rules.
자주 묻는 질문
Why were my Google Play screenshots rejected?
Common causes include wrong file format, invalid dimensions, screenshots that do not show the actual app experience, misleading text overlays, ranking claims, price claims, or device-specific rule violations.
Do Google Play screenshots need to show the app?
Yes. Google says screenshots must demonstrate the actual in-app or in-game experience and focus on core features and content.
Can repeated Google Play screenshot issues hurt my account?
A single rejection does not affect developer account standing, but Google warns that repeated or serious policy violations can lead to stronger enforcement.