The Short Answer
Dark screenshots work when your app is genuinely dark-first and the store page has enough contrast around them. They fail when the store's own background is light, because a dark tile with dark captions turns into a grey smudge at carousel size.
The honest answer is that it depends on your category and it's worth testing rather than deciding on taste. Media, music, photo editing and developer tools tend to do well dark. Utilities, finance, health and anything aimed at a broad audience tend to do better light.
What matters more than the choice is contrast inside the frame. A dark screenshot with bright, high-contrast caption text outperforms a light one with grey-on-white captions every time.
So the question isn't really light or dark. It's whether the thing you want people to read survives being shrunk to thumbnail size.
The honest answer is that it depends on your category and it's worth testing rather than deciding on taste. Media, music, photo editing and developer tools tend to do well dark. Utilities, finance, health and anything aimed at a broad audience tend to do better light.
What matters more than the choice is contrast inside the frame. A dark screenshot with bright, high-contrast caption text outperforms a light one with grey-on-white captions every time.
So the question isn't really light or dark. It's whether the thing you want people to read survives being shrunk to thumbnail size.
What Dark Backgrounds Do to Contrast
The store carousel displays your screenshots small and surrounded by the store's own chrome. On both stores, that chrome is predominantly light in default appearance.
A dark screenshot creates a strong edge against that light background, which is genuinely good for stopping the scroll — the tile reads as a distinct object rather than blending into the page.
The problem is inside the tile. Dark backgrounds compress the range you have for text. White text on near-black is high contrast, and mid-grey text on dark grey, which is what most "elegant" designs use, disappears entirely at small sizes.
So the design rule flips. On light screenshots you can use mid-tone text and get away with it. On dark ones, captions need to be near-white or a saturated accent colour, or they're lost.
Check by shrinking your screenshot to about 25% and looking at it from arm's length. That's roughly what a browsing user sees, and it's the test most dark designs fail.
If you want the underlying theory, Material's colour role documentation explains why dark surfaces need larger contrast steps between layers than light ones do — the same reason dark screenshots need brighter captions than you'd expect.
A dark screenshot creates a strong edge against that light background, which is genuinely good for stopping the scroll — the tile reads as a distinct object rather than blending into the page.
The problem is inside the tile. Dark backgrounds compress the range you have for text. White text on near-black is high contrast, and mid-grey text on dark grey, which is what most "elegant" designs use, disappears entirely at small sizes.
So the design rule flips. On light screenshots you can use mid-tone text and get away with it. On dark ones, captions need to be near-white or a saturated accent colour, or they're lost.
Check by shrinking your screenshot to about 25% and looking at it from arm's length. That's roughly what a browsing user sees, and it's the test most dark designs fail.
If you want the underlying theory, Material's colour role documentation explains why dark surfaces need larger contrast steps between layers than light ones do — the same reason dark screenshots need brighter captions than you'd expect.
Where Dark Screenshots Win
Media apps are the clearest case. Video, music and photo apps look better dark because the content is the bright thing on screen and a dark chrome makes it pop, which is exactly what the real app does.
Developer and productivity tools benefit too. Code editors, terminals and data tools are dark in practice, and showing them light would misrepresent the product.
Games are almost always better dark, because game art carries the frame and any UI around it should recede.
The common thread is that the app is genuinely dark. Screenshots are supposed to show the app, and dressing a light app in a dark theme for the store creates a mismatch users notice on first launch — which shows up as uninstalls rather than as a conversion problem you can see.
There's a secondary win worth mentioning: dark tiles differentiate you when every competitor in your category uses white backgrounds. Standing out in the search results grid is worth real installs, and it costs nothing to try.
Developer and productivity tools benefit too. Code editors, terminals and data tools are dark in practice, and showing them light would misrepresent the product.
Games are almost always better dark, because game art carries the frame and any UI around it should recede.
The common thread is that the app is genuinely dark. Screenshots are supposed to show the app, and dressing a light app in a dark theme for the store creates a mismatch users notice on first launch — which shows up as uninstalls rather than as a conversion problem you can see.
There's a secondary win worth mentioning: dark tiles differentiate you when every competitor in your category uses white backgrounds. Standing out in the search results grid is worth real installs, and it costs nothing to try.
Where Dark Screenshots Lose
Broad-audience utilities are the main loser. An older or less technical audience reads dark interfaces as harder to use, and there's no upside to fighting that impression on the store page.
Finance and health apps also tend to do better light, where light reads as clean and trustworthy. That's a cultural association rather than a rule, and it's consistent enough to plan around.
Any app where the screenshots are text-heavy struggles dark. Long captions, feature lists and comparison tables all read worse on dark backgrounds at small sizes.
And the technical problem: dark screenshots with subtle gradients band badly under JPEG compression. What looks like a smooth deep-blue gradient in your design tool becomes visible stripes on the store page. If you're going dark with gradients, export as PNG rather than JPEG.
Watch the device frame too. A dark screenshot inside a black device frame merges into one shape, and the phone disappears. Use a lighter frame, or add a subtle inner border — our device frames guide covers picking frames that separate from the content.
Finance and health apps also tend to do better light, where light reads as clean and trustworthy. That's a cultural association rather than a rule, and it's consistent enough to plan around.
Any app where the screenshots are text-heavy struggles dark. Long captions, feature lists and comparison tables all read worse on dark backgrounds at small sizes.
And the technical problem: dark screenshots with subtle gradients band badly under JPEG compression. What looks like a smooth deep-blue gradient in your design tool becomes visible stripes on the store page. If you're going dark with gradients, export as PNG rather than JPEG.
Watch the device frame too. A dark screenshot inside a black device frame merges into one shape, and the phone disappears. Use a lighter frame, or add a subtle inner border — our device frames guide covers picking frames that separate from the content.
The Hybrid That Usually Wins
The setup I'd recommend for most apps isn't fully light or fully dark. It's a coloured background — your brand colour, reasonably saturated — with the actual app screenshot in whatever theme the app really uses.
That gives you the differentiation of a non-white tile, plenty of contrast for caption text, and no misrepresentation of the app itself.
It also solves the frame problem. A brand-coloured background separates cleanly from both black and white device frames, so the phone reads as a phone.
If your brand colour is very light or very dark, use a tint or shade of it rather than the raw value. Store tiles want mid-range saturation, since extremes at either end cause the contrast problems described above.
The first screenshot is where this matters most. It's the one that appears in search results, it carries most of the conversion weight, and our guide to screenshots that get downloads goes into what else belongs in that frame.
That gives you the differentiation of a non-white tile, plenty of contrast for caption text, and no misrepresentation of the app itself.
It also solves the frame problem. A brand-coloured background separates cleanly from both black and white device frames, so the phone reads as a phone.
If your brand colour is very light or very dark, use a tint or shade of it rather than the raw value. Store tiles want mid-range saturation, since extremes at either end cause the contrast problems described above.
The first screenshot is where this matters most. It's the one that appears in search results, it carries most of the conversion weight, and our guide to screenshots that get downloads goes into what else belongs in that frame.
Testing It Properly
Don't decide this from a design review. Both stores let you test, and the answer varies by category enough that intuition is unreliable.
On Google Play, store listing experiments will run a light set against a dark set and report the difference with statistical confidence. That's the cleanest possible answer to this question and it's free.
On the App Store, custom product pages and product page optimisation let you do something similar, though the setup is more involved.
Run the test on the first two screenshots only, not the whole set. Changing everything at once tells you that something worked without telling you what.
Give it enough traffic to be meaningful. A low-volume app may never reach significance on a screenshot test, in which case pick the option with better small-size legibility and move on. Our walkthrough of A/B testing app store screenshots covers how long to run and when to call it.
And if you want to produce both variants quickly to test, generating the same captures on two backgrounds takes minutes in PlayMockup rather than an afternoon of re-exporting.
On Google Play, store listing experiments will run a light set against a dark set and report the difference with statistical confidence. That's the cleanest possible answer to this question and it's free.
On the App Store, custom product pages and product page optimisation let you do something similar, though the setup is more involved.
Run the test on the first two screenshots only, not the whole set. Changing everything at once tells you that something worked without telling you what.
Give it enough traffic to be meaningful. A low-volume app may never reach significance on a screenshot test, in which case pick the option with better small-size legibility and move on. Our walkthrough of A/B testing app store screenshots covers how long to run and when to call it.
And if you want to produce both variants quickly to test, generating the same captures on two backgrounds takes minutes in PlayMockup rather than an afternoon of re-exporting.
The Store Chrome Problem
One factor people forget entirely: the store page itself has a theme, and the user controls it.
A dark screenshot designed against the App Store's light background looks completely different when the user browses in dark mode. Your carefully judged contrast edge disappears, because now a dark tile sits on a dark page and the boundary vanishes.
The reverse is true for light screenshots, which glare against a dark store page. Neither is fatal, and both mean your design can't assume a background.
The practical defence is a defined edge inside the tile. A subtle border, a background that isn't pure black or pure white, or a device frame that contrasts with the canvas all keep the screenshot legible in either store theme.
Check it by viewing your own store listing in both appearance settings on a real device. It takes a minute, most people never do it, and it's the fastest way to find a set that looks great in one theme and unreadable in the other. Do it once per major store redesign and forget about it in between.
A dark screenshot designed against the App Store's light background looks completely different when the user browses in dark mode. Your carefully judged contrast edge disappears, because now a dark tile sits on a dark page and the boundary vanishes.
The reverse is true for light screenshots, which glare against a dark store page. Neither is fatal, and both mean your design can't assume a background.
The practical defence is a defined edge inside the tile. A subtle border, a background that isn't pure black or pure white, or a device frame that contrasts with the canvas all keep the screenshot legible in either store theme.
Check it by viewing your own store listing in both appearance settings on a real device. It takes a minute, most people never do it, and it's the fastest way to find a set that looks great in one theme and unreadable in the other. Do it once per major store redesign and forget about it in between.
Frequently asked questions
Are dark mode app screenshots better for conversion?
It depends on category. Media, games and developer tools generally do well dark; broad utilities, finance and health apps usually do better light. What matters more is caption contrast — dark backgrounds need near-white or saturated accent text to stay readable at thumbnail size.
Should my screenshots match my app's actual theme?
Yes. Showing a light app in a dark theme creates a mismatch users notice on first launch, which produces uninstalls rather than a conversion problem you can measure. Show the app as it really looks.
Why do my dark screenshots look banded on the store?
JPEG compression handles subtle dark gradients badly, producing visible stripes. Export dark screenshots with gradients as PNG rather than JPEG, and keep gradient transitions shorter to reduce the effect.
What background colour works best for app screenshots?
A mid-saturation version of your brand colour usually beats both pure white and pure black. It differentiates in the search grid, gives caption text room to contrast, and separates cleanly from black or white [device frames](/blog/device-frames-for-app-mockups).
How do I test light versus dark screenshots?
Use Google Play's store listing experiments, or custom product pages on the App Store. Change only the first two screenshots so you know what caused any difference, and give the test enough traffic to reach significance before acting on it.
Build the mockup in your browser.
Drop a screenshot into a real device frame and export at the exact store size — free, no signup.