iOS 26 Liquid Glass & iPhone 17: Refresh Your App Store Screenshots Before Fall
By Yogesh Devaliya
Published · Last updated
Open your App Store listing on a phone running iOS 26. Then open the app.
If the listing still shows a solid black tab bar, a flat navigation header, and an iPhone 15-era frame, you already have a conversion problem. It is not dramatic. It is quiet. The store says one thing. The first launch says another.
That mismatch is the story of this week. Apple’s Liquid Glass chrome is in the wild. iPhone 17 screenshot specs are in App Store Connect. The fall hardware cycle is days away, not months. Teams that treat screenshots as a once-a-year design task will ship a 2025 listing into a 2026 store.
This is not another generic ASO recap. It is the practical refresh: what changed, which sizes actually matter, and how to ship a new set from Nakxi before the September noise starts.
The trust gap nobody budgets for
Users do not audit your Human Interface Guidelines. They glance.
Frame one and frame two of the gallery are the listing. Everything after that is optional. If those two frames show last year’s chrome, two things happen at once:
- The product looks older than it is. Early iPhone 17 buyers are looking at device-accurate listings. A wrong bezel is a quality signal, the same way an outdated website font is.
- The live app surprises them. Liquid Glass changes how tab bars, navigation bars, toolbars, and sheets render. Screenshots composed against opaque chrome no longer match the installed UI.
Apple does not reject you for that. Review does not care. Users do. Conversion is the ranking signal you actually control this month.
If you want the conversion craft — captions, order, first-frame promise — read how to create App Store screenshots that convert. This post is about the timing and the hardware/OS shift sitting on top of that craft.
What Liquid Glass actually changes (and what it does not)
Liquid Glass is Apple’s translucent, adaptive material on system chrome. If you built with the iOS 26 SDK, a lot of this arrived without a redesign meeting:
| UI you show in screenshots | What changed | Screenshot action |
|---|---|---|
| Tab bar | Floating, translucent, inset from the bottom edge | Retake. Old pinned bars look glued on. |
| Navigation bar | Glass material instead of a solid fill | Retake if the nav is visible in frames 1–3. |
| Sheets and modals | Translucent backdrop | Check contrast. Captions sitting on glass need more weight. |
| Status bar / Dynamic Island | New device geometry on 17-class phones | Use current frames, not last year’s mockup. |
| Custom-drawn UI | Unchanged unless you opted in | No action unless you want visual parity. |
You do not need a brand-new visual language. You need honest captures of the UI people will actually install, placed in current device frames, with captions that still read at search-result size.
A practical test I still use: put the first screenshot on a lock screen, hold the phone at arm’s length, and squint. If the headline and the glass chrome fight each other, the caption loses.
The August window is the point
September will be messy on purpose. iOS 26 stable, iPhone 17 hardware, and a wave of competitor screenshot updates hit conversion analytics at the same time. Devices change. OS versions change. Creatives change. You cannot tell which lever moved.
August is the opposite: calmer search, fewer competing refreshes, and enough days of clean impression data before back-to-school and the hardware launch pile on.
If you only do one listing job this month, do this: new screenshots on 6.9-inch, current frames, Liquid Glass UI, localized captions for your top markets. Metadata tweaks can wait a week. Visuals cannot, because they take longer to produce and they are what people see in search.
Ready to rebuild the set while the window is still open? Start free on Nakxi →
iPhone 17 sizes without turning this into a spec sheet
Apple’s screenshot specifications are the source of truth. For Fall 2026, the iPhone decision collapses to three numbers:
| Display class | Portrait size | Typical devices | Do you upload it? |
|---|---|---|---|
| 6.9“ | 1320 × 2868 (also accepts 1290 × 2796 and 1260 × 2736) | iPhone 17 Pro Max, 16 Pro Max, Plus, Air in this slot | Yes. This is the required iPhone set. |
| 6.3“ | 1206 × 2622 | iPhone 17, 17 Pro, 16 Pro | Optional. Upload if 6.9“ scaled text looks cramped. |
| 6.5“ Air native | 1260 × 2736 | iPhone Air | Optional unless Air is a real slice of your installs. |
Apple scales the 6.9-inch set down through smaller classes. Most teams only need one iPhone upload. The teams that add 6.3-inch are the ones whose captions sit at the edge of the canvas — fintech, health, anything with dense UI.
If you want every accepted pixel size, including iPad, Watch, and legacy phones, use the App Store screenshot size guide. Do not rebuild that table in Figma from memory. Get it wrong and App Store Connect rejects the binary assets, not the design.
File rules that still catch people: PNG or JPEG, RGB, no alpha, no transparency. A “beautiful” PNG with a transparent bezel is a failed upload.
Device frames are part of ASO now
This used to be a taste argument. It is not, in a hardware week.
iPhone 17 buyers scroll listings the way car buyers look at taillights. The frame is the product context. A screenshot still using a thick-chin mockup, or a 6.7-inch proportion on a 6.9-inch canvas, reads as “this app has not been touched.”
Use current frames. Crop tightly enough that the UI is readable in the App Store search strip. Do not hide the Liquid Glass tab bar behind a caption box — that is the whole point of the refresh.
Nakxi’s app mockup generator and the App Store screenshot generator keep device frames on the same canvas as store sizes, so you are not exporting from a mockup tool and pasting into a 1320 × 2868 artboard by hand.
A 5-step refresh that actually ships
I have watched teams spend three weeks on this because they treated it as ten separate design files. It is one project with five passes.
1. Start on 6.9-inch, not “whatever the last project was”
Open a new project in the App Store screenshot generator at 1320 × 2868. If last year’s file is 1290 × 2796, do not stretch it. Stretching captions is how you get blurry type in search.
Templates on nakxi.com/templates/appstore are already sized for store slots. Steal the layout, swap the UI.
2. Drop real iOS 26 UI into current frames
Capture from a device or simulator running iOS 26. Not a marketing render of an older build. Place it in an iPhone 17-class frame. If you show both light and dark, pick the one that matches how your app actually launches for most users — mixed sets look like two products.
3. Rewrite captions for glass, not for last year’s gradient
Liquid Glass eats contrast. Captions that worked on a solid navy background will fail on a frosted bar.
Keep headlines to three to five words. Put the outcome in frame one. Put proof in frame two. Save features for three through six. Write like a human, then check that the words still make sense if Apple’s OCR reads them — which it does. For the copy system, see screenshot copy that increases downloads.
4. Localize while the layout is open
You are already touching every frame. This is the cheapest week of the year to add German, Japanese, Portuguese, and Spanish captions. English overlays in Japan are still one of the most expensive silent leaks in indie ASO.
Nakxi localization can clone the project across 40+ languages without rebuilding the grid. Full walkthrough: App Store localization in 2026.
5. Export iOS, then resize for Play
Do not maintain two unrelated design systems. Finish App Store, then generate Play Store screenshots from the same story with Android frames. Play does not need Liquid Glass. It does need the same promise, in the right aspect ratio.
Build the Fall 2026 set in Nakxi →
What not to do this week
Do not turn this into a full brand redesign. You will miss the window.
Do not upload 6.3-inch and 6.9-inch sets with different caption stories. Apple will scale; users will not forgive inconsistency.
Do not put prices, “#1 app,” or App Store badges in the art. Review still hates that, and it dates the asset the day a competitor outranks you.
Do not skip iPad if you ship iPad. The 13-inch slot is 2064 × 2752. A stretched iPhone screenshot on iPad Pro is its own trust gap.
Do not wait for “final” iPhone 17 photography. You need store-legal pixel sizes and current bezels, not a press render.
A short checklist you can finish this weekend
- First two frames recaptured on iOS 26, not last year’s build
- 6.9-inch export at 1320 × 2868, RGB, no alpha
- iPhone 17-class device frames, not a leftover 15 Pro mockup
- Captions still readable on glass (arm’s-length squint test)
- Locale sets for every market where you already localize metadata
- iPad 13-inch if the binary supports iPad
- Play Store set resized from the same narrative, not ignored
If a box is unchecked on Monday, the listing is the old product. The binary is the new one. Stores punish that slowly. Users punish it immediately.
Frequently Asked Questions
Do I need new App Store screenshots for iOS 26 Liquid Glass?
If your screenshots still show opaque tab bars, solid navigation chrome, or last-generation device frames, yes. iOS 26 reskins system UI with Liquid Glass. A listing that shows the old chrome while the installed app looks translucent creates a trust gap in the first three frames.
What App Store screenshot size should I use for iPhone 17?
Upload the 6.9-inch class as your required iPhone set. Apple currently accepts 1320×2868, 1290×2796, and 1260×2736 for that slot. 1320×2868 is the sharpest match for iPhone 17 Pro Max. Apple scales 6.9-inch screenshots down to smaller classes if you do not upload those sizes separately.
Is 1290×2796 still accepted in 2026?
Yes. It is still an accepted 6.9-inch size in App Store Connect. If you are rebuilding the set anyway for Liquid Glass, export 1320×2868 and you are done with the size question.
When should I refresh screenshots before iPhone 17 launches?
August. You get cleaner conversion data before September’s hardware and OS refresh wave. Waiting until October means you are testing in noise.
Do I also need new Google Play screenshots?
Only if the Android UI actually changed. Refresh iOS first, then resize the same story for Play so the two listings do not drift.
Closing
Fall hardware weeks are when listings quietly rot. Not because developers stopped caring — because screenshots sit in a folder labeled “done.”
Liquid Glass and iPhone 17 are the excuse to open that folder. The work is not artistic. It is operational: right size, current frame, honest UI, captions that still read, locales you already pay to rank in.
Nakxi is the studio I wanted when this used to mean a week in Figma and a pile of rejected uploads. Store canvases, mockups, localization, and export live in one place. Use it, or use whatever you already have — but ship the refresh before the store fills up with people who did.