{"id":92,"date":"2026-04-21T03:30:40","date_gmt":"2026-04-21T03:30:40","guid":{"rendered":"https:\/\/appscreenkit.com\/learn\/screenshot-size-compliance-avoid-app-store-rejection\/"},"modified":"2026-04-21T03:30:40","modified_gmt":"2026-04-21T03:30:40","slug":"screenshot-size-compliance-avoid-app-store-rejection","status":"publish","type":"post","link":"https:\/\/appscreenkit.com\/learn\/screenshot-size-compliance-avoid-app-store-rejection\/","title":{"rendered":"Screenshot Size Compliance Explained: Avoid App Store Rejection"},"content":{"rendered":"<\/p>\n<hr>\n<blockquote>\n<p><strong>TL;DR:<\/strong><\/p>\n<ul>\n<li>Meeting exact device-specific pixel, format, and content rules is essential to avoid rejection.<\/li>\n<li>Apple and Google have detailed, separate requirements for screenshot sizes, formats, and content.<\/li>\n<li>Using compliant templates and automated tools streamlines the process and prevents costly errors.<\/li>\n<\/ul>\n<\/blockquote>\n<hr>\n<p>Getting your app screenshots to look great is only half the battle. The harder half is making sure they actually meet the exact pixel dimensions, file formats, and content rules enforced by Apple and Google. <a href=\"https:\/\/developer.apple.com\/help\/app-store-connect\/reference\/app-information\/screenshot-specifications\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Screenshot size compliance<\/a> means adhering to every technical and policy requirement both stores enforce before your app goes live. Miss one spec and your submission bounces back. Miss a content rule and your listing could be suppressed or removed entirely. This guide breaks down what compliance actually requires, platform by platform, so you can ship faster and stop losing time to avoidable rejections.<\/p>\n<h2 id=\"table-of-contents\">Table of Contents<\/h2>\n<ul>\n<li><a href=\"#what-is-screenshot-size-compliance?\">What is screenshot size compliance?<\/a><\/li>\n<li><a href=\"#apple-app-store%3A-screenshot-size-and-content-requirements\">Apple App Store: Screenshot size and content requirements<\/a><\/li>\n<li><a href=\"#google-play%3A-screenshot-and-graphics-specification-explained\">Google Play: Screenshot and graphics specification explained<\/a><\/li>\n<li><a href=\"#content-compliance%3A-policies-every-screenshot-must-meet\">Content compliance: Policies every screenshot must meet<\/a><\/li>\n<li><a href=\"#streamlining-compliance%3A-tools%2C-templates%2C-and-workflow-tips\">Streamlining compliance: Tools, templates, and workflow tips<\/a><\/li>\n<li><a href=\"#the-overlooked-cost-of-non-compliance%3A-why-a-single-pixel-can-ruin-your-launch\">The overlooked cost of non-compliance: Why a single pixel can ruin your launch<\/a><\/li>\n<li><a href=\"#ensure-compliance-and-boost-conversions-with-the-right-tools\">Ensure compliance and boost conversions with the right tools<\/a><\/li>\n<li><a href=\"#frequently-asked-questions\">Frequently asked questions<\/a><\/li>\n<\/ul>\n<h2 id=\"key-takeaways\">Key Takeaways<\/h2>\n<table>\n<thead>\n<tr>\n<th>Point<\/th>\n<th>Details<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Compliance is mandatory<\/td>\n<td>Following strict screenshot specs is essential to avoid app rejection and display errors.<\/td>\n<\/tr>\n<tr>\n<td>Apple vs. Google differences<\/td>\n<td>Each store has unique size, format, and content policies\u2014never reuse screenshots without checking requirements.<\/td>\n<\/tr>\n<tr>\n<td>Content rules matter<\/td>\n<td>Showing real app use and avoiding misleading content is just as important as dimensions.<\/td>\n<\/tr>\n<tr>\n<td>Tools speed up compliance<\/td>\n<td>Templates and automation reduce errors and save hours for every release.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"what-is-screenshot-size-compliance\">What is screenshot size compliance?<\/h2>\n<p>Screenshot size compliance means every image you submit meets the device-specific pixel dimensions, file format, quantity limits, and content policies required by the app store you are targeting. It sounds straightforward, but the details are where most developers stumble.<\/p>\n<p>Think of it this way: the app stores are not just checking whether your screenshots look polished. They are running automated and human checks against a strict spec sheet. If your image is even slightly off in resolution or format, the system flags it before a human ever sees your app.<\/p>\n<p>According to Apple\u2019s official screenshot specs, compliance goes beyond pixel count. It covers file type, color mode, file size limits, the number of screenshots you can submit per device, and whether the content itself accurately represents how your app functions. Failing on any single point triggers rejection.<\/p>\n<p>Here is a quick overview of the core compliance factors every developer needs to track:<\/p>\n<table>\n<thead>\n<tr>\n<th>Compliance factor<\/th>\n<th>What it covers<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Pixel dimensions<\/td>\n<td>Exact width and height per device size<\/td>\n<\/tr>\n<tr>\n<td>File format<\/td>\n<td>PNG or JPEG (varies by store)<\/td>\n<\/tr>\n<tr>\n<td>File size<\/td>\n<td>Maximum MB per image<\/td>\n<\/tr>\n<tr>\n<td>Quantity<\/td>\n<td>Min and max screenshots per device<\/td>\n<\/tr>\n<tr>\n<td>Content accuracy<\/td>\n<td>Must show real in-app use<\/td>\n<\/tr>\n<tr>\n<td>Color mode<\/td>\n<td>RGB only, no alpha channel (Apple)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>For a deeper look at how these factors connect to the broader submission process, the <a href=\"https:\/\/appscreenkit.com\/learn\/app-store-requirements-submission-rules-visuals-convert\">app store requirements guide<\/a> covers the full picture.<\/p>\n<p>The key thing to internalize is that compliance is not a one-time checkbox. Every time Apple or Google updates device support or policy language, your existing templates can become non-compliant overnight. Staying current is part of the job.<\/p>\n<blockquote>\n<p>\u201cNon-compliance with screenshot specifications does not just slow you down. It costs you the launch window you worked months to reach.\u201d<\/p>\n<\/blockquote>\n<ul>\n<li><strong>Pixel dimensions:<\/strong> Must match the exact device resolution required<\/li>\n<li><strong>File format:<\/strong> Wrong format means instant rejection<\/li>\n<li><strong>Content accuracy:<\/strong> Screenshots must show the app actively in use<\/li>\n<li><strong>Quantity rules:<\/strong> Too few or too many screenshots per device type fails validation<\/li>\n<\/ul>\n<h2 id=\"apple-app-store-screenshot-size-and-content-requirements\">Apple App Store: Screenshot size and content requirements<\/h2>\n<p>With the basics in mind, let\u2019s explore how Apple enforces screenshot specs. Apple\u2019s requirements are among the most detailed in the industry and they update them as new hardware launches.<\/p>\n<p>For modern iPhones, the most important size to get right is the 6.9&quot; display. Apple currently requires <strong>1320\u00d72868 pixels<\/strong> in portrait orientation for this device class. The 6.5&quot; iPhone requires 1242\u00d72688, and older 5.5&quot; devices require 1242\u00d72208. For iPad Pro (6th gen, 13&quot;), the required size is 2064\u00d72752 in portrait.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/csuxjmfbwmkxiegfpljm.supabase.co\/storage\/v1\/object\/public\/blog-images\/organization-24157\/1776512382401_Hand-holding-phone-displaying-screenshot-specs.jpeg\" alt=\"Hand holding phone displaying screenshot specs\"><\/p>\n<p>Apple supports <strong>PNG and JPEG formats<\/strong> only. Images must use RGB color space with no alpha channel (transparency). The <a href=\"https:\/\/developer.apple.com\/app-store\/review\/guidelines\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">maximum file size is under 120MB<\/a> per screenshot, and you can submit between 1 and 10 screenshots per device size. The 6.9&quot; iPhone size is now mandatory for all new submissions.<\/p>\n<p><strong>Steps to prepare compliant Apple screenshots:<\/strong><\/p>\n<ol>\n<li>Identify every device size your app supports, starting with the mandatory 6.9&quot; iPhone.<\/li>\n<li>Export app UI at the correct pixel resolution for each device.<\/li>\n<li>Flatten all layers and remove alpha channels before export.<\/li>\n<li>Verify color mode is set to RGB in your export settings.<\/li>\n<li>Check file size stays under 120MB per image.<\/li>\n<li>Review content against Apple\u2019s guidelines: real app UI, no splash screens, no misleading text.<\/li>\n<li>Upload and validate inside App Store Connect before submission.<\/li>\n<\/ol>\n<table>\n<thead>\n<tr>\n<th>Device<\/th>\n<th>Required size (portrait)<\/th>\n<th>Format<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>iPhone 6.9&quot;<\/td>\n<td>1320\u00d72868 px<\/td>\n<td>PNG\/JPEG<\/td>\n<\/tr>\n<tr>\n<td>iPhone 6.5&quot;<\/td>\n<td>1242\u00d72688 px<\/td>\n<td>PNG\/JPEG<\/td>\n<\/tr>\n<tr>\n<td>iPhone 5.5&quot;<\/td>\n<td>1242\u00d72208 px<\/td>\n<td>PNG\/JPEG<\/td>\n<\/tr>\n<tr>\n<td>iPad Pro 13&quot;<\/td>\n<td>2064\u00d72752 px<\/td>\n<td>PNG\/JPEG<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Apple\u2019s content rules are equally firm. Screenshots must show the app actively in use. Splash screens, login pages shown in isolation, or any UI that does not reflect genuine app functionality will trigger a rejection. Misleading claims, including text overlays that exaggerate features, are also violations. For inspiration on what works visually within these rules, the <a href=\"https:\/\/appscreenkit.com\/learn\/app-store-visual-trends-boost-engagement-2026\">app store visual trends<\/a> resource is worth reviewing.<\/p>\n<p>Pro Tip: Match your screenshot UI to the actual build you are submitting. Apple reviewers compare the screenshots to the live app experience, and discrepancies can get your app pulled even after initial approval. For a full rundown of the submission process, see <a href=\"https:\/\/appscreenkit.com\/learn\/app-store-compliance-essential-steps-approval-quality\">app store compliance essentials<\/a>.<\/p>\n<h2 id=\"google-play-screenshot-and-graphics-specification-explained\">Google Play: Screenshot and graphics specification explained<\/h2>\n<p>After Apple, Google Play takes a slightly different approach. Let\u2019s break down what you need to know.<\/p>\n<p>Google Play requires between 2 and 8 screenshots per device type. Accepted formats are JPEG or 24-bit PNG without alpha transparency. The <a href=\"https:\/\/support.google.com\/googleplay\/android-developer\/answer\/9866151\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">minimum dimension is 320 pixels<\/a> on any side, and the maximum is 3840 pixels on any side. The aspect ratio must not exceed 2:1. For phone screenshots, Google recommends 1080\u00d71920 or 1080\u00d72400 pixels.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/csuxjmfbwmkxiegfpljm.supabase.co\/storage\/v1\/object\/public\/blog-images\/organization-24157\/1776512749150_Infographic-on-app-store-screenshot-compliance-basics.jpeg\" alt=\"Infographic on app store screenshot compliance basics\"><\/p>\n<p>One important rule that catches many developers off guard: you cannot use iOS device frames in your Google Play screenshots. Using an iPhone mockup on a Google Play listing is a direct policy violation and grounds for rejection. Content must also be free of misleading claims, pricing information shown in screenshots, or anything that misrepresents the app\u2019s actual behavior.<\/p>\n<p>Google Play also requires a <strong>feature graphic<\/strong> (1024\u00d7500 px, JPEG or 24-bit PNG) if you want your app to appear in promotional placements. This is separate from your screenshots but equally important for visibility.<\/p>\n<table>\n<thead>\n<tr>\n<th>Requirement<\/th>\n<th>Apple App Store<\/th>\n<th>Google Play<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Screenshot count<\/td>\n<td>1-10 per device<\/td>\n<td>2-8 per device type<\/td>\n<\/tr>\n<tr>\n<td>File formats<\/td>\n<td>PNG\/JPEG<\/td>\n<td>JPEG\/24-bit PNG<\/td>\n<\/tr>\n<tr>\n<td>Alpha channel<\/td>\n<td>Not allowed<\/td>\n<td>Not allowed<\/td>\n<\/tr>\n<tr>\n<td>Minimum dimension<\/td>\n<td>Device-specific<\/td>\n<td>320 px any side<\/td>\n<\/tr>\n<tr>\n<td>Maximum dimension<\/td>\n<td>Device-specific<\/td>\n<td>3840 px any side<\/td>\n<\/tr>\n<tr>\n<td>Feature graphic<\/td>\n<td>Not required<\/td>\n<td>1024\u00d7500 px required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Common pitfalls that lead to Google Play rejections:<\/p>\n<ul>\n<li>Submitting screenshots that exceed the 3840 px limit on either side<\/li>\n<li>Using an aspect ratio wider than 2:1<\/li>\n<li>Including iOS device frames or Apple-specific UI elements<\/li>\n<li>Showing pricing or promotional text in screenshot images<\/li>\n<li>Submitting fewer than 2 screenshots for a required device type<\/li>\n<\/ul>\n<p>For more detail on optimizing visuals specifically for Google Play, the <a href=\"https:\/\/appscreenkit.com\/learn\/design-google-play-visuals-maximize-app-conversions\">Google Play visuals guide<\/a> is a solid starting point. You can also cross-reference your work against the <a href=\"https:\/\/appscreenkit.com\/learn\/app-store-listing-checklist-optimize-visuals-cvr\">app store listing checklist<\/a> to catch gaps before submission.<\/p>\n<h2 id=\"content-compliance-policies-every-screenshot-must-meet\">Content compliance: Policies every screenshot must meet<\/h2>\n<p>Technical specs matter, but content guidelines are just as critical. Here\u2019s what every screenshot must communicate.<\/p>\n<p>Both Apple and Google require that your screenshots show the app in active, genuine use. That means a static splash screen, a login form shown alone, or a promotional graphic that does not reflect real UI will not pass review. The <a href=\"https:\/\/developer.apple.com\/support\/downloads\/terms\/app-review-guidelines\/App-Review-Guidelines-English-UK.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">content rules are direct<\/a>: screenshots must accurately represent the app\u2019s features and must not include misleading claims, superlatives like \u201c#1\u201d or \u201cbest,\u201d pricing information, or references to competitors.<\/p>\n<p>This is where many teams make an expensive mistake. They focus all their energy on getting the pixel dimensions right and assume the content side is just about looking good. In practice, content violations are one of the most common reasons apps get flagged during review, not dimension errors.<\/p>\n<blockquote>\n<p>\u201cInaccurate or misleading screenshots violate both Apple\u2019s and Google\u2019s policies, regardless of how technically perfect the image specs are.\u201d<\/p>\n<\/blockquote>\n<p><strong>Screenshot content do\u2019s and don\u2019ts:<\/strong><\/p>\n<ul>\n<li><strong>Do<\/strong> show real, current app UI on the target device<\/li>\n<li><strong>Do<\/strong> use text overlays that describe genuine features accurately<\/li>\n<li><strong>Do<\/strong> update screenshots every time your UI changes significantly<\/li>\n<li><strong>Don\u2019t<\/strong> include splash screens or loading states as primary screenshots<\/li>\n<li><strong>Don\u2019t<\/strong> use superlative language like \u201cworld\u2019s best\u201d or \u201c#1 app\u201d<\/li>\n<li><strong>Don\u2019t<\/strong> show competitor app names, logos, or pricing comparisons<\/li>\n<li><strong>Don\u2019t<\/strong> display pricing tiers or subscription costs inside screenshot images<\/li>\n<\/ul>\n<p>Pro Tip: Capture screenshots directly from the device or simulator using your current production build. This removes any risk that your marketing visuals drift from what reviewers actually see when they run your app. If you want to add visual flair while staying compliant, resources on <a href=\"https:\/\/appscreenkit.com\/learn\/app-screenshot-branding-tutorial-boost-downloads\">branding your app screenshots<\/a> and <a href=\"https:\/\/appscreenkit.com\/learn\/what-is-screenshot-optimization-boost-app-store-results\">screenshot optimization strategies<\/a> show how to do both. You can also explore how <a href=\"https:\/\/appscreenkit.com\/learn\/app-preview-images-boost-store-conversions\">preview images tips<\/a> apply to video previews, which follow a parallel but distinct set of rules.<\/p>\n<h2 id=\"streamlining-compliance-tools-templates-and-workflow-tips\">Streamlining compliance: Tools, templates, and workflow tips<\/h2>\n<p>To wrap up, here\u2019s how successful teams streamline screenshot compliance for every update.<\/p>\n<p>The biggest time sink in screenshot compliance is not knowing the specs. It is having to redo work every time a device size gets added or a policy shifts. The teams that stay ahead build a repeatable workflow rather than treating compliance as a one-off task.<\/p>\n<p>Size-compliant screenshots reduce review rejections and speed up app publication. The efficiency gain is real, but only if your process is built around reusable, validated templates from the start.<\/p>\n<p><strong>Steps to ensure compliance at every release:<\/strong><\/p>\n<ol>\n<li>Maintain a living spec chart covering all device sizes for both Apple and Google Play, updated every quarter.<\/li>\n<li>Use pre-built, store-validated templates as your starting point rather than building from scratch each time.<\/li>\n<li>Capture fresh UI screenshots from your current build before every submission.<\/li>\n<li>Run each image through a format and dimension check before uploading to App Store Connect or Google Play Console.<\/li>\n<li>Use bulk export tools to generate all required device sizes from a single source image.<\/li>\n<li>Review content against both Apple and Google policies before finalizing.<\/li>\n<li>Archive your screenshot sets by version so you can roll back quickly if needed.<\/li>\n<\/ol>\n<p>Pro Tip: Keep your device-by-device spec chart in a shared doc your whole team can access. When Apple announces a new iPhone size, update the chart immediately and flag any templates that need refreshing. <a href=\"https:\/\/appscreenkit.com\/learn\/pre-built-screenshot-templates-save-time-boost-quality\">Ready-made screenshot templates<\/a> built to current specs eliminate most of the manual work. A solid visuals checklist tied to each release keeps the process consistent across your team.<\/p>\n<h2 id=\"the-overlooked-cost-of-non-compliance-why-a-single-pixel-can-ruin-your-launch\">The overlooked cost of non-compliance: Why a single pixel can ruin your launch<\/h2>\n<p>Here is the uncomfortable truth most dev teams do not talk about: the cost of a single non-compliant screenshot is almost never just one hour of fixes. It is the full review cycle reset, the delayed launch window, the marketing campaign that fired on the wrong date, and the early adopter buzz that fizzled while you waited for re-approval.<\/p>\n<p>The assumption that \u201cclose enough\u201d works is what makes this so dangerous. A screenshot that is one pixel short of the required minimum, or exported in the wrong color profile, looks identical to the human eye but triggers an automated rejection. One outdated template from a previous release can cascade across six device sizes instantly.<\/p>\n<p>The real investment is not in fixing individual screenshots. It is in building a front-loaded compliance workflow that makes rejections structurally impossible. Teams that use purpose-built tools, like the ones outlined in <a href=\"https:\/\/appscreenkit.com\/learn\/advantages-mockup-tools-app-store-success\">mockup tool advantages<\/a>, stop treating compliance as a final check and start baking it into every step of the release process. That shift is what separates teams that ship on schedule from teams that are always one rejection behind.<\/p>\n<h2 id=\"ensure-compliance-and-boost-conversions-with-the-right-tools\">Ensure compliance and boost conversions with the right tools<\/h2>\n<p>Compliance does not have to mean slow. The right tools handle the technical requirements automatically so your team can focus on making screenshots that actually convert.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/csuxjmfbwmkxiegfpljm.supabase.co\/storage\/v1\/object\/public\/blog-images\/organization-24157\/1774735187544_appscreenkit.jpg\" alt=\"https:\/\/appscreenkit.com\"><\/p>\n<p>AppScreenKit is built specifically for this problem. It covers all required device and store specs for both Apple and Google Play, includes templates validated against current requirements, and lets you export every device size in one click. No manual resizing, no format errors, no guesswork. You can explore <a href=\"https:\/\/appscreenkit.com\/learn\/fast-screenshot-generation-app-store-success\">fast screenshot generation<\/a> workflows that cut your production time dramatically, or start with screenshot templates that are already sized and formatted correctly. Visit <a href=\"https:\/\/appscreenkit.com\">AppScreenKit<\/a> to start building compliant, high-converting screenshots today.<\/p>\n<h2 id=\"frequently-asked-questions\">Frequently asked questions<\/h2>\n<h3 id=\"what-happens-if-my-app-screenshots-dont-meet-size-compliance\">What happens if my app screenshots don\u2019t meet size compliance?<\/h3>\n<p>Your app submission will likely be rejected outright or your screenshots may appear distorted, cropped incorrectly, or missing entirely in the store listing.<\/p>\n<h3 id=\"can-i-use-the-same-screenshots-for-both-apple-store-and-google-play\">Can I use the same screenshots for both Apple Store and Google Play?<\/h3>\n<p>No. Each store has unique size and format requirements, including different aspect ratios, resolution minimums, and format rules, so you need tailored versions for each platform.<\/p>\n<h3 id=\"is-there-an-official-template-for-app-screenshot-sizes\">Is there an official template for app screenshot sizes?<\/h3>\n<p>Apple and Google publish official specification documentation for developers, but tools like AppScreenKit provide ready-to-use templates that are already validated against current requirements.<\/p>\n<h3 id=\"what-content-is-not-allowed-in-app-store-screenshots\">What content is NOT allowed in app store screenshots?<\/h3>\n<p>Inaccurate UI, superlative claims, login-only or splash screens, pricing information, and competitor references are all prohibited by guidelines from both Apple and Google.<\/p>\n<h2 id=\"recommended\">Recommended<\/h2>\n<ul>\n<li><a href=\"https:\/\/appscreenkit.com\/learn\/app-store-requirements-submission-rules-visuals-convert\">App store requirements: submission rules and visuals that convert \u2013 AppScreenKit<\/a><\/li>\n<li><a href=\"https:\/\/appscreenkit.com\/learn\/app-store-compliance-essential-steps-approval-quality\">App store compliance: Essential steps for approval and quality \u2013 AppScreenKit<\/a><\/li>\n<li><a href=\"https:\/\/appscreenkit.com\/learn\/app-store-visual-trends-boost-engagement-2026\">App store visual trends to boost engagement in 2026 \u2013 AppScreenKit<\/a><\/li>\n<li><a href=\"https:\/\/appscreenkit.com\/learn\/what-is-screenshot-optimization-boost-app-store-results\">What is screenshot optimization? Boost app store results fast \u2013 AppScreenKit<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Learn the exact screenshot size and content rules for Apple App Store and Google Play to avoid rejection, pass review, and boost your app&#8217;s conversion rate.<\/p>\n","protected":false},"author":1,"featured_media":94,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-92","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/appscreenkit.com\/learn\/wp-json\/wp\/v2\/posts\/92","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/appscreenkit.com\/learn\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/appscreenkit.com\/learn\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/appscreenkit.com\/learn\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/appscreenkit.com\/learn\/wp-json\/wp\/v2\/comments?post=92"}],"version-history":[{"count":1,"href":"https:\/\/appscreenkit.com\/learn\/wp-json\/wp\/v2\/posts\/92\/revisions"}],"predecessor-version":[{"id":93,"href":"https:\/\/appscreenkit.com\/learn\/wp-json\/wp\/v2\/posts\/92\/revisions\/93"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/appscreenkit.com\/learn\/wp-json\/wp\/v2\/media\/94"}],"wp:attachment":[{"href":"https:\/\/appscreenkit.com\/learn\/wp-json\/wp\/v2\/media?parent=92"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/appscreenkit.com\/learn\/wp-json\/wp\/v2\/categories?post=92"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/appscreenkit.com\/learn\/wp-json\/wp\/v2\/tags?post=92"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}