Your Screenshots Still Show Pre-Glass UI
Since April 28, 2026, App Store uploads must use the iOS 26 SDK. Standard bars and sheets pick up Liquid Glass on their own. If the listing still shows last year’s opaque chrome, the product page is advertising an app you no longer ship.
Quick answer
Do App Store screenshots need to be recaptured after Liquid Glass?
Yes, if the live app now uses Liquid Glass and the listing still shows pre-iOS 26 chrome. Apps uploaded to App Store Connect since April 28, 2026 must be built with the iOS 26 SDK or later. Standard SwiftUI, UIKit, and AppKit bars, sheets, and controls pick up Liquid Glass when you build with that SDK. Guideline 2.3 also requires screenshots to stay up to date with new versions. Recapture from the shipping binary, then rebuild the store set.
- iOS and iPadOS uploads have required the iOS 26 SDK since April 28, 2026
- Standard system components adopt Liquid Glass without a redesign
- Opaque nav bars and pinned tab bars in screenshots no longer match the installed app
- Guideline 2.3 says metadata, including screenshots, must stay current
- Recapture filled, realistic screens from the binary you actually ship
On this page
A lot of indie iOS teams treated Liquid Glass as an engineering ticket: bump Xcode, fix the one custom tab bar that broke, ship. The listing never got a ticket. Search still shows last year’s solid navigation bar. The installed app is translucent, concentric, and obviously newer. That gap is now the default, not an edge case.
Apple’s submitting page is unambiguous. As of April 28, 2026, iOS and iPadOS apps uploaded to App Store Connect must be built with the iOS 26 and iPadOS 26 SDK or later . The visual consequence sits in a different document: if you use standard components, the interface picks up Liquid Glass when you build with the latest SDKs.
What actually changed in the pixels
Apple’s Adopting Liquid Glass note is the part most ASO checklists skipped. Liquid Glass is a functional layer for controls and navigation. Bars, sheets, popovers, and standard controls adopt it automatically in SwiftUI, UIKit, and AppKit. Custom backgrounds on those elements can overlay or fight the material. Icons are layered. Light, dark, clear, and tinted Home Screen appearances exist. None of that is optional cosmetics for a screenshot captured in 2025.
| Old screenshot | What the shipping app often shows | Why it matters on the store |
|---|---|---|
| Opaque navigation bar, hard edge | Translucent bar over scrolling content | Frame one no longer matches first launch |
| Tab bar glued to a solid fill | Floating, concentric tab bar | Search thumbnails read as a different product |
| Flat toolbar buttons | Glass controls that refract the UI behind them | The “in use” proof looks dated next to iOS 26 peers |
| Single light-mode icon crop | Layered icon with dark / tinted variants | Home Screen mockups in the listing lie about personalization |
You do not need a full redesign for this mismatch to appear. Rebuilding with the iOS 26 SDK is enough for standard chrome to change, and enough for old screenshots to stop being proof.
This is a Guideline 2.3 problem, not a taste problem
App Review Guideline 2.3 Accurate Metadata tells you to keep screenshots up to date with new versions so customers know what they are getting. Stale chrome is not automatically a rejection, and it should not be sold as one. It is still a metadata miss: the listing promises an interface the binary no longer presents. Conversion leaks from that kind of surprise even when review is silent.
- Recapture from the build you submit, not from an old Figma file or a simulator theme you no longer ship.
- Fill the screens with realistic data. Empty Glass chrome looks even more like a template.
- Check Reduce Transparency and the user’s Liquid Glass intensity settings so captions still sit on a readable crop.
- If screenshot one includes Home Screen or icon art, update the layered icon set too.
- Fall iOS 27 Creative Assets sit above these frames. A glass app under a 2025 header is a second mismatch. See App Store Creative Assets.
Do not generate Glass. Recapture it.
Image models will invent a plausible translucent tab bar. That invented bar is not your app, and it is the fastest way to walk into a 2.3 accuracy issue. The correct input is a device or simulator capture from the shipping binary. Layout, captions, and backgrounds are the part you can generate. The UI inside the frame is not.
Recapture a Liquid Glass screenshot set in one sitting
Confirm the shipping look
Run the App Store binary on an iOS 26 or 27 device or simulator. Note bars, sheets, and the icon’s light and dark variants. If you set UIDesignRequiresCompatibility, document that — the listing must match the opt-out.
Capture three to five filled screens
Skip splash, login, and empty states. Use realistic names and data. Capture at the resolution you will crop from, in the orientation you ship.
Rebuild the store frames
Drop the captures into AppGrowthKit. Keep the in-app UI untouched. Rewrite captions so they still read on a glassy crop, then export the required App Store sizes.
Replace the live set
Upload the new frames in App Store Connect with the next version, or through Asset Library when that workflow is available for screenshots. Do not leave one old 6.1" leftover next to a new 6.9" set.
Spot-check search
Look at the first three frames at search-result size. If the glass chrome ate the caption, shorten the type or change the crop — do not flatten the UI to make the type easier.
Recap: Glass in the binary, Glass on the store
- The iOS 26 SDK deadline already happened. New uploads are Glass-era binaries.
- Standard chrome changes without a redesign. Screenshots do not update themselves.
- Guideline 2.3 wants metadata that matches the current experience.
- Recapture real UI. Generate layout around it. Do not invent a tab bar.
- iOS 27 Creative Assets will sit on top of these frames this fall — do not refresh only the header.
Liquid Glass screenshot questions
Will App Review reject screenshots that still show iOS 18 chrome?
Apple has not published a “must show Liquid Glass” screenshot rule. Guideline 2.3 does require screenshots to accurately reflect the current app and stay up to date. A listing that shows UI the binary no longer presents is the risk, not the material name.
We used UIDesignRequiresCompatibility. Do we still recapture?
Capture whatever the customer actually launches. If compatibility mode keeps the old look, old-looking screenshots can be accurate. If most users on iOS 26 still see Glass, the listing should show Glass.
Do Google Play screenshots need the same pass?
Only if the Android UI also changed. Play does not adopt Liquid Glass. Recapture Android frames when the product UI changed, and keep Play-sized exports in the same session so the two stores do not drift.
Should we wait for iOS 27 stable before reshooting?
Do not wait if the live listing already disagrees with the iOS 26 app. Recapture now from the shipping SDK. Plan a second pass this fall if you add Creative Assets or if iOS 27 changes icon treatment you show in the frames.
Sources, verified 2026-08-21:
Free tools that help here
App Icon Generator
Drop in one 1024px icon and download every iOS and Android size, ready for Xcode and Android Studio. Runs entirely in your browser - nothing gets uploaded.
ASO Character Counter
Count characters for every App Store and Google Play metadata field against exact store limits. Live counts and over-limit warnings - nothing gets truncated at submission.
Screenshot Beautifier
Add polished backgrounds, padding, shadows, and rounded corners to any screenshot in seconds. Perfect for social posts, docs, and portfolios.
The live UI changed. The listing has to catch up.
AppGrowthKit wraps the screens you recapture from the current binary — glass chrome and all — into editable, store-sized frames so the first three slots match what people install.
Try AppGrowthKit for Free