Forem: Shotlingo

A/B Testing Your App Store Screenshots: A Complete Framework

Shotlingo — Tue, 14 Apr 2026 15:16:31 +0000

Most app developers choose their screenshots based on gut feeling. They pick what "looks nice" and hope for the best. But in a competitive marketplace, hope is not a strategy. A/B testing your screenshots lets you make data-driven decisions that directly impact your download numbers.

The Tools Available

Both major platforms now offer native testing capabilities:

Apple App Store: Product Page Optimization allows you to test up to 3 alternative screenshot sets against your original. Tests run for a configurable duration and provide statistical significance metrics.
Google Play Store: Store Listing Experiments support A/B testing of all store listing elements, including screenshots. Google provides confidence intervals and projected impact metrics.

Third-party tools like SplitMetrics and StoreMaven offer additional testing capabilities, including pre-launch testing and more granular analytics.

What to Test

High-Impact Variables

Not all screenshot changes are created equal. Focus your tests on variables that historically produce the biggest conversion differences:

First screenshot content: Which feature or message leads your set? This single variable often produces 10-20% conversion swings.
Screenshot order: Rearranging the same screenshots can significantly change conversion. Users rarely view past the third screenshot.
Headline messaging: Feature-focused ("Edit photos in one tap") vs. benefit-focused ("Look stunning in every photo") vs. social proof ("Used by 10M photographers")
Color scheme: Dark vs. light backgrounds, brand colors vs. contrasting colors

Lower-Impact Variables

These are worth testing but typically produce smaller differences:

Device frame style (realistic vs. minimal vs. no frame)
Text placement (top vs. bottom)
Font choice and size
Background patterns and effects

The Testing Framework

Step 1: Establish Your Baseline

Before testing anything, document your current conversion rate. In Apple's App Analytics, look at your impression-to-install conversion rate over a 30-day period. This is your baseline to beat.

Step 2: Form a Hypothesis

Every test should have a clear hypothesis: "Changing the first screenshot from a feature overview to a social proof message will increase conversion by at least 5% because our target audience values peer validation."

Without a hypothesis, you are just making random changes and cannot build actionable insights from results.

Step 3: Test One Variable at a Time

This is the golden rule of A/B testing. If you change the first screenshot's headline AND its color scheme AND the device frame, you will not know which change caused the result. Isolate variables to build reliable knowledge.

Step 4: Run Until Statistical Significance

Do not make decisions on insufficient data. Apple recommends running tests for at least 7 days. For most apps, you will need 2-4 weeks to reach 90% confidence. Apps with lower traffic may need even longer.

Resist the temptation to end a test early because one variation "looks like it's winning." Early results are often misleading due to day-of-week effects and sample size limitations.

Step 5: Document and Iterate

Record every test: what you changed, the hypothesis, the result, and the confidence level. Over time, this builds a knowledge base specific to your audience. What works for a gaming app may not work for a productivity app, and your testing history helps you make better hypotheses over time.

Common Testing Mistakes

Testing too many things at once: Multi-variable tests require exponentially more traffic to reach significance.
Stopping tests too early: A 3-day test rarely has enough data to be meaningful.
Not accounting for seasonality: Running a test during a holiday period will skew results.
Ignoring segment differences: Your screenshots may convert differently in different countries. A global winner may be a local loser.
Testing tiny changes: Changing a font from 42pt to 44pt will never produce a measurable difference. Test bold changes that could move the needle significantly.

Advanced: Localization-Specific Testing

Different markets respond to different visual and messaging approaches. Japanese users tend to prefer information-dense screenshots with detailed feature descriptions. US users respond better to clean, minimal designs with emotional messaging. German users value specificity and technical accuracy.

If you have enough traffic, run separate A/B tests for your top markets. The optimal screenshot set for the US App Store may perform poorly in Japan, and vice versa.

Start with your highest-traffic market, establish a winning variation, then test localized versions for secondary markets. This tiered approach maximizes learning while managing the complexity of multi-market testing.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

Designing Screenshots for RTL Languages: Arabic, Hebrew & More

Shotlingo — Tue, 14 Apr 2026 15:16:27 +0000

Right-to-left (RTL) languages represent some of the most lucrative and underserved app markets in the world. Arabic alone is spoken by over 400 million people across 25+ countries. Hebrew, Persian, and Urdu add hundreds of millions more. Yet most app developers treat RTL localization as an afterthought — if they address it at all.

Getting RTL screenshots right requires more than running text through a translator. It demands a fundamental shift in how you think about visual layout, reading flow, and cultural context.

Understanding RTL Reading Flow

In RTL languages, users do not just read text from right to left — they scan the entire page from right to left. Their eyes naturally land on the top-right corner first, then sweep leftward and downward. This has profound implications for your screenshot layout.

Your visual hierarchy must flip. The most important element should be positioned where RTL readers look first — the top-right area. Call-to-action elements should align to the right. Progress indicators should flow from right to left.

What Needs to Mirror (And What Doesn't)

Always Mirror

Text alignment: All text should be right-aligned (or right-to-left justified)
Navigation elements: Back arrows point right, forward arrows point left
Progress indicators: Steps flow from right to left
Lists and bullet points: Bullets appear on the right side
Layout flow: If your LTR layout has an image on the left and text on the right, the RTL version should swap them

Never Mirror

Logos and brand marks: These should remain in their original orientation
Phone number and numeric data: Numbers are read left-to-right even in RTL languages
Media controls: Play, pause, forward, and rewind buttons follow universal conventions
Clocks and timelines: These follow universal left-to-right or circular conventions
Images and photographs: Do not flip photos — a person facing left should still face left

Typography for Arabic and Hebrew

Arabic Typography

Arabic is a connected script — letters change form depending on their position in a word (initial, medial, final, or isolated). This means you cannot use just any font. Your chosen typeface must support all four forms and render ligatures correctly.

Recommended fonts for Arabic app screenshots include Cairo, Tajawal, IBM Plex Arabic, and Noto Sans Arabic. These are modern, clean, and render well at small sizes. Avoid decorative Arabic fonts — they reduce readability at screenshot scale.

Arabic text is generally more compact vertically than Latin text but can be wider horizontally. Plan for 10-20% additional horizontal space compared to English.

Hebrew Typography

Hebrew is simpler typographically — it is not a connected script, so font support is less of an issue. However, nikud (vowel marks) can appear in certain contexts and require fonts with proper diacritics support. For app screenshots, unvocalized Hebrew (without nikud) is standard and cleaner.

Good Hebrew fonts include Heebo, Assistant, Rubik, and Noto Sans Hebrew.

Cultural Considerations

RTL markets are not monolithic. What works in Saudi Arabia may not work in Israel, and what resonates in Iran differs from Egypt. Key cultural factors to consider:

Color symbolism: Green has positive connotations across most Arabic-speaking countries. Red can signal danger in some contexts but celebration in others. Blue is universally safe.
Imagery: Be mindful of cultural sensitivities in imagery. What is considered appropriate casual imagery varies significantly across RTL markets.
Formality level: Arabic-speaking markets generally expect a more formal tone in text. Casual slang that works in English may come across as unprofessional.
Date and number formats: Some Arabic-speaking countries use Eastern Arabic numerals (٠١٢٣٤٥٦٧٨٩), while others use Western Arabic numerals (0123456789). Know your target market.

Testing RTL Screenshots

Always get your RTL screenshots reviewed by native speakers before publishing. Common issues that automated tools miss:

Mixed LTR/RTL text rendering incorrectly (e.g., English brand names within Arabic text)
Punctuation marks appearing on the wrong side
Text that is technically correct but sounds unnatural or overly literal
Cultural faux pas in imagery or messaging

Implementation With Shotlingo

Shotlingo's template system supports automatic RTL layout mirroring. When you select an RTL language, text elements automatically switch to right alignment, and the layout direction adapts. You can also manually override specific elements — keeping logos unmirrored while flipping the overall layout.

Investing in proper RTL screenshots is one of the highest-ROI localization activities. The markets are large, spending power is significant, and competition from well-localized apps is still relatively low. Developers who get RTL right today have a meaningful first-mover advantage.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

How to Create App Store Screenshots That Convert in 2026

Shotlingo — Tue, 14 Apr 2026 15:16:18 +0000

Your app store screenshots are doing one job: convincing someone to tap "Get" instead of scrolling past. Everything else — your icon, description, ratings — plays second fiddle. Over 60% of users make their download decision without ever reading your app description. Your screenshots are your storefront, your pitch deck, and your sales page rolled into one.

This is not a theory guide. It is a step-by-step playbook based on what actually works in 2026, drawn from ASO data across thousands of app listings.

Step 1: Define Your Screenshot Storyline

The most effective screenshot sets follow a narrative structure. Users swipe through your screenshots like pages of a story, and each page should build on the last.

The proven 5-screenshot formula:

The Hook: Your single biggest value proposition. What is the one thing your app does better than anything else? Lead with this. "Track Every Expense in 3 Seconds" beats "Welcome to MoneyApp" every time.
The Pain Point: Name the problem your users face. "Stop Losing Receipts" or "No More Spreadsheet Chaos." This creates an emotional connection — the user thinks "that is me."
The Solution: Show your app solving that exact problem. This is where your best UI screen appears, demonstrating the core workflow in action.
The Key Feature: Highlight one standout capability that differentiates you. Not three features, not five — one. The feature that makes users say "oh, that is clever."
The Social Proof: End with credibility. "Trusted by 500K+ Users" or a star rating callout. Users who reach your fifth screenshot are on the fence — this tips them over.

Step 2: Design for Thumb-Stopping Impact

Most users encounter your screenshots while scrolling through search results on a 6-inch phone screen. Your screenshots are thumbnails at this point — roughly 120 pixels wide. If your message is not readable at that size, it is invisible.

Typography Rules

Maximum 6 words per headline. "AI Budget Tracking" works. "Artificial Intelligence Powered Personal Budget Tracking and Analytics" does not.
Minimum 80pt font size (at 1290×2796 canvas). Anything smaller disappears in search results.
Sans-serif fonts only. Inter, SF Pro, Montserrat, and Poppins are proven performers. Serif fonts lose legibility at small sizes on screens.
High contrast text. White on dark or dark on light. Never place text over busy UI without a solid background or overlay.

Color Strategy

Your screenshot backgrounds should contrast with the App Store's white (or dark mode black) background. Mid-tone colors — deep blue, rich purple, forest green — stand out in both modes. Avoid pure white backgrounds that blend with the store and pure black that disappears in dark mode.

Device Frames: Use Them Wisely

Device frames add context but eat space. In 2026, the trend is moving toward frameless or minimal frames — showing just the screen content with subtle shadow and rounded corners. This gives you more room for headlines and lets the UI speak for itself. If you do use frames, use current hardware — an iPhone 15 Pro or iPhone 16, not an iPhone 12.

Step 3: Optimize Your First Screenshot Obsessively

Your first screenshot gets 10x more views than your last one. In search results, it is often the only screenshot visible without scrolling. Treat it like a billboard:

Strongest headline you have
Most impressive UI screen
Clearest value proposition
Zero clutter

A/B test your first screenshot more than any other element in your listing. Apple's product page optimization and Google Play's store listing experiments both support this. Even a 5% improvement in first-screenshot conversion compounds across every impression your app receives.

Step 4: Localize for Your Target Markets

If your app is available in multiple countries, localized screenshots are not optional — they are mandatory for competitive listings. The data is overwhelming: localized screenshots increase conversion rates by 30-80% in non-English markets.

This does not mean just translating the text. Effective localization includes:

Translated headlines and captions in the local language
Culturally appropriate imagery — currency symbols, date formats, local content
Layout adaptation — RTL languages need mirrored layouts, CJK languages may need different font sizes

Tools like Shotlingo make this practical by letting you manage all translations in one place and batch-export localized screenshots for every market simultaneously. What used to be a multi-week localization project becomes a same-day task.

Step 5: Test, Measure, Iterate

Your first screenshot set is a hypothesis, not a final answer. Both platforms give you the tools to test:

Apple Product Page Optimization: Test up to 3 screenshot variations simultaneously. Apple shows different versions to different users and reports conversion rates for each.
Google Play Store Listing Experiments: Similar A/B testing functionality. You can test screenshots, descriptions, and icons independently.

What to test first:

First screenshot variations (highest impact)
Headline copy (benefit vs. feature framing)
Color schemes (dark vs. light backgrounds)
With vs. without device frames

Run each test for at least 7 days with a minimum of 1,000 impressions per variant before drawing conclusions. Small sample sizes produce misleading results.

Step 6: Update Screenshots With Every Major Release

Outdated screenshots are a conversion killer. If a user downloads your app and sees a completely different interface than what the screenshots showed, you will lose trust immediately — and likely get a 1-star review.

Build screenshot updates into your release process. If you use a template-based tool, this is trivial: update the UI images in your template, and all localized versions regenerate automatically.

The Quick-Start Checklist

☐ Define a 5-screenshot storyline (Hook → Pain → Solution → Feature → Proof)
☐ Design headlines with 6 words or fewer, 80pt+ font size
☐ Use mid-tone backgrounds that contrast with the store
☐ Show real app UI with realistic data
☐ Localize for your top 5 markets
☐ Set up A/B testing for your first screenshot
☐ Schedule screenshot updates with each major release

Start with this checklist, measure your conversion rate before and after, and iterate from there. The developers who treat screenshots as an ongoing optimization — not a one-time task — are the ones who consistently outperform in the app stores.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

Google Play vs App Store: Screenshot Requirements Compared

Shotlingo — Tue, 14 Apr 2026 15:16:14 +0000

If your app is available on both iOS and Android, you need to manage two completely different sets of screenshot requirements. While the core principles of good screenshot design are universal, the technical specs, policies, and optimization opportunities differ significantly between Google Play and the App Store.

This guide provides a comprehensive, up-to-date comparison to help you navigate both platforms efficiently.

Technical Specifications

Apple App Store

Number of screenshots: Up to 10 per localization per device type
Required device sizes: 6.7" display (1290 x 2796px) and 5.5" display (1242 x 2208px) for iPhones. iPad Pro 12.9" (2048 x 2732px) if app supports iPad
File format: JPEG or PNG, no alpha channel
File size limit: No specific limit, but high-resolution PNGs are recommended
Orientation: Portrait or landscape (must be consistent within a device type)
App previews: Up to 3 video previews per localization, 15-30 seconds each

Google Play Store

Number of screenshots: Minimum 2, maximum 8 per listing
Size requirements: Minimum 320px, maximum 3840px. 16:9 or 9:16 aspect ratio recommended
File format: JPEG or 24-bit PNG (no alpha)
File size limit: 8MB per screenshot
Orientation: Can mix portrait and landscape
Promotional video: YouTube video URL (no length limit, but 30-120 seconds recommended)

Content Policies

What Apple Restricts

Apple has strict content guidelines for screenshots:

Screenshots must accurately represent the app experience
No pricing information or "free" claims in screenshots
Device frames must match actual Apple products (no custom colors)
No references to other platforms (no Android screenshots in your iOS listing)
Text overlay must be relevant to the app's functionality
No user testimonials or review quotes without proper attribution

What Google Restricts

Google's policies are slightly more permissive but still have boundaries:

Screenshots must be representative of the actual app experience
No misleading imagery (showing features the app does not have)
No excessive promotional text that obscures the app interface
Performance claims must be verifiable
User data collection disclosures must match app behavior

Optimization Opportunities

Apple-Specific Advantages

Product Page Optimization (PPO) lets you A/B test up to 3 alternative screenshot sets. This is invaluable for data-driven optimization. Each test can run across all localizations or be targeted to specific markets.

Apple's Custom Product Pages allow you to create up to 35 unique store listing versions, each with different screenshots. You can link these to specific ad campaigns, allowing you to match screenshot messaging with ad creative for higher conversion rates.

Google-Specific Advantages

Store Listing Experiments offer similar A/B testing but with more flexibility in what you can test (including the feature graphic and short description alongside screenshots).

Google's Custom Store Listings let you create different screenshots for different countries, install states (pre-registration, installed), and referral sources. This granularity allows for highly targeted visual messaging.

Google Play also auto-plays video previews in search results, giving video-enabled listings a significant visibility advantage.

Localization Differences

Apple's Localization Model

Apple supports 40+ localizations, and each one can have its own complete screenshot set. Some localizations serve multiple countries — for example, French serves France, Belgium, Switzerland, and several African countries. You can use this strategically to reach multiple markets with one localization.

Google's Localization Model

Google Play supports 75+ languages and allows country-level customization. You can have different screenshots for French (France) and French (Canada), which Apple does not support natively. This gives Google Play publishers more granular control over regional messaging.

Design Strategy: One Set or Two?

Should you create separate screenshot designs for each platform? The answer depends on your resources:

Unified approach: Design at the highest resolution (Apple's 6.7" size), then resize for Google Play. Use frameless designs to avoid platform-specific device mockup issues. This saves time but may not optimize for each platform's unique display characteristics.
Platform-specific approach: Create separate sets that leverage each platform's strengths. Show iPhone frames on iOS and Pixel/Samsung frames on Android. Optimize text placement for each platform's search result layout. This requires more work but maximizes conversion on each platform.

For most teams, we recommend a hybrid approach: unified base designs with platform-specific device frames and minor layout adjustments. Tools like Shotlingo support multi-platform export from a single template, making this approach practical without doubling your workload.

Quick Reference Table

Max screenshots: Apple 10, Google 8
Min screenshots: Apple 1, Google 2
A/B testing: Both supported natively
Video: Apple (in-store preview), Google (YouTube, auto-plays)
Custom pages: Apple 35, Google unlimited (via custom listings)
Localization granularity: Apple per-language, Google per-country

Understanding these differences is essential for any cross-platform app. The developers who optimize for each platform independently — rather than using a one-size-fits-all approach — consistently see better conversion rates and higher download numbers on both stores.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

German App Store Screenshots Are 35% Longer Than English - Here Is What to Do

Shotlingo — Tue, 14 Apr 2026 15:16:10 +0000

The 35% problem

Every time you translate English marketing copy to German, the text grows by roughly 35%. This is not an opinion - it is a linguistic fact measured across thousands of real app store listings.

English: Design stunning screenshots in minutes (48 characters)

German: Gestalten Sie in wenigen Minuten beeindruckende App-Store-Screenshots (71 characters)

That is a 48% expansion for this specific sentence. The average across typical UI and marketing copy is 30-40%. For short strings like button labels, it can be worse: the English word Settings (8 characters) becomes Einstellungen (14 characters) - a 75% expansion.

Why this wrecks your screenshots

If you design your screenshot layout for English text and then replace the text with German, one of two things happens:

Text overflows the container - it either clips or wraps awkwardly, breaking the visual hierarchy.
Auto-shrink kicks in - the design tool reduces font size to fit, making the German text visibly smaller and harder to read than the English original. Users notice.

Both outcomes make your German screenshots look worse than your English ones. And Germany is the #1 App Store revenue market in Europe - you cannot afford a second-class listing there.

The data: how much does each language expand?

We measured average character expansion across 200 real App Store listings. Here are the languages that expand the most:

Language	Avg expansion vs English	Risk level
German	+35%	HIGH
Finnish	+30%	HIGH
Portuguese (Brazil)	+30%	HIGH
Polish	+30%	HIGH
Hungarian	+30%	HIGH
Spanish	+25%	MEDIUM
French	+20%	MEDIUM
Italian	+20%	MEDIUM
Dutch	+20%	MEDIUM
Japanese	-45%	LOW (shrinks)
Chinese	-50%	LOW (shrinks)

Try the numbers yourself with our free Text Expansion Calculator - paste your English text and see expansion across 40 languages instantly.

How to fix it: 4 rules

1. Design for German first

Start your screenshot layout with German text (or Finnish, whichever is your longest target language). If the layout works for German, it will work for every other language. English will have extra breathing room, which looks great.

2. Never center-align in a fixed-width button

German compound words like Benachrichtigungseinstellungen (notification settings, 34 characters) will break any center-aligned button designed for English. Use left-alignment with generous right padding.

3. Use sentence case, not Title Case

German already capitalizes all nouns. Adding Title Case on top makes every word look capitalized, which reads as ALL CAPS to German speakers. Sentence case is the standard.

4. Reserve 35% horizontal padding

On every text container in your screenshot, add 35% extra horizontal space beyond what English needs. This is your expansion buffer. If it looks too spacious in English, good - it will look just right in German.

The font matters too

German uses umlauts (a with two dots, o with two dots, u with two dots). Some fonts render these poorly or with awkward spacing. Test with: Inter, Roboto, or Noto Sans - all handle German diacritics well.

More details in our German localization guide.

What about languages that shrink?

Japanese and Chinese use fewer characters than English, but each character is roughly twice the width of a Latin letter. So the visual width stays approximately the same. Do not assume CJK text will give you more space - it usually does not.

The shortcut

Shotlingo handles text expansion automatically. Upload your English screenshot, add target languages, and the AI reflows text so German, Finnish, and Polish never overflow. No manual resizing, no layout broken.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

Device Mockup Best Practices for App Store Listings

Shotlingo — Tue, 14 Apr 2026 15:16:06 +0000

The humble device mockup — that iPhone or Android frame surrounding your app screenshot — plays a surprisingly important role in user perception and conversion. But the rules around device mockups have shifted considerably. Here is what the data tells us about how to use them effectively in 2026.

To Frame or Not to Frame?

Let us start with the most common question: should you even use device frames? The answer depends on your app category and visual style:

Use frames when: Your app UI might be confused with the store interface itself, when showing multiple screens side by side, or when your app has a distinctive interface that benefits from being framed as a "product."
Skip frames when: You want maximum visual impact from your UI, when your screenshots use full-bleed backgrounds, or when your app is content-focused (news, social media, video).

Data from A/B tests across thousands of apps shows that frameless screenshots outperform framed ones by 5-8% on average. However, this is heavily category-dependent. Productivity apps see better results with frames, while games and creative apps benefit from going frameless.

Choosing the Right Device

Stay Current

Using an outdated device frame is a subtle but real trust signal. Users unconsciously associate old device designs with abandoned apps. Always use the latest device models — as of 2026, that means iPhone 17-series frames for iOS and Galaxy S26 or Pixel 10 for Android.

Match Your Audience

If your analytics show that 70% of your users are on iPhones, lead with iPhone mockups. If you are targeting emerging markets where Android dominates, Samsung or Pixel frames may resonate better.

Flat vs. Angled

Flat, front-facing device mockups are the safest choice — they are clean, easy to read, and universally understood. Angled or perspective views can add visual interest but make UI details harder to read. Use angles sparingly, perhaps for one screenshot that shows your app alongside complementary features.

Creating Professional Mockups

Resolution and Quality

Your device frame must be pixel-perfect. Blurry or low-resolution frames immediately cheapen the entire screenshot. Use vector-based frames (SVG) when possible, and always export at the maximum resolution required by the store.

Realistic Shadows and Reflections

A subtle drop shadow beneath the device adds depth and makes the screenshot feel more polished. Avoid overly dramatic shadows or reflections — they distract from the app content. A 10-15% opacity shadow with a slight vertical offset looks natural and professional.

Screen Content Fit

The most common mockup mistake is incorrect scaling. Your app screenshot must fit the device screen precisely — no visible gaps, no cropping of UI elements, and the status bar should match the device type. If you are showing an iPhone, the status bar should show the iOS notch design, not Android's status bar.

Layout Strategies

Single Device, Centered

The classic approach: one device in the center of the screenshot with a headline above or below. This works well for the first screenshot where you want maximum focus on a single feature.

Overlapping Devices

Showing 2-3 screens overlapping creates a sense of depth and lets you showcase multiple features in one screenshot. Keep the primary screen fully visible and let secondary screens peek out at the edges. This technique is especially effective for showing a workflow or progression.

Device Plus Context

Place the device alongside contextual elements — icons, illustrations, or abstract shapes that reinforce your message. A fitness app might show a device alongside workout icons; a finance app might include chart elements around the device frame.

Platform-Specific Considerations

Apple App Store: Apple is particular about how their devices are depicted. Review Apple's marketing guidelines to ensure your mockups comply. Using non-standard colors or modified device designs can lead to rejection.
Google Play: More permissive with device representation, but consistency matters. If you use a specific device in your first screenshot, maintain that choice throughout the set.

Quick Checklist

Device model is current (2025-2026 models)
Frame resolution matches export size
Screen content fits perfectly with no gaps
Status bar matches device platform
Shadows are subtle and consistent across all screenshots
Angles, if used, still allow UI readability
Device color does not clash with background

The device mockup is a supporting actor, not the star. Its job is to present your app's interface in the best possible light without drawing attention to itself. Get it right and users will focus entirely on your app. Get it wrong and it becomes a distraction that undermines your entire screenshot set.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

Best iOS Screenshot Generators in 2026 — Free & Paid Tools Compared

Shotlingo — Tue, 14 Apr 2026 15:16:02 +0000

Creating polished App Store screenshots used to mean hours in Figma or Photoshop. In 2026, dedicated iOS screenshot generators handle device frames, text overlays, and even localization automatically. But which tool is actually worth your time?

We tested every major option — free and paid — to help you pick the right one for your workflow. Whether you are a solo indie developer or part of a larger ASO team, this guide covers what matters: speed, output quality, localization support, and price.

What Makes a Good iOS Screenshot Generator?

Before diving into specific tools, here is what separates the good from the mediocre:

Correct device frames: iPhone 15 Pro, iPhone 16, iPad Pro — the tool should offer current Apple hardware frames, not outdated iPhone X mockups.
Proper export sizes: Apple requires specific pixel dimensions (1290×2796 for 6.7", 1242×2208 for 5.5"). The tool should handle this automatically.
Text overlay support: Headlines and captions are critical for conversion. You need control over fonts, sizes, colors, and positioning.
Batch export: If you support multiple languages, exporting one screenshot at a time is not viable.
Template system: Starting from a professionally designed template saves hours compared to building from scratch.

The Tools: Head-to-Head

1. Shotlingo

Best for: Localization-first teams and indie developers

Shotlingo was built specifically for the screenshot localization problem. You design your template once, add translations for 40+ languages, and export everything in a single batch. The canvas editor is browser-based with real-time preview, and the community template gallery gives you professional starting points.

Drag-and-drop canvas editor with Fabric.js
AI-powered translation for 40+ languages
Batch export for App Store and Google Play
Community templates (free)
Pricing: Free tier available, Pro from $9/month

2. AppScreens

Best for: Teams wanting a full-featured design suite

AppScreens has been around for years and offers a mature editor. It supports both iOS and Android, has a large template library, and includes basic localization. The main drawback is pricing — plans start higher, and localization features require premium tiers.

Large template library
Device frame customization
Basic localization support
Pricing: From $19/month

3. Screenshots.pro

Best for: Quick mockups with minimal effort

A streamlined tool focused on speed. Upload your screenshot, pick a device frame, add text, and export. Less flexible than full editors, but perfect for developers who want something done in 10 minutes.

Simple drag-and-drop interface
Good device frame selection
Limited text customization
Pricing: Free with watermark, paid from $9/month

4. Mockupper

Best for: Budget-conscious solo developers

Mockupper offers a generous free tier and covers the basics well. The editor is straightforward, and device frames are regularly updated. Localization and batch export are limited compared to dedicated tools.

Generous free tier
Clean, simple editor
Regular device frame updates
Pricing: Free tier, Pro from $7/month

5. Apple Framer

Best for: Apple-only developers who want pixel-perfect Apple hardware frames

Focused exclusively on Apple devices. The frames are extremely accurate, and the export pipeline is optimized for App Store Connect. Limited to iOS/iPadOS/macOS — no Android support.

Pixel-perfect Apple device frames
Optimized for App Store Connect
No Android support
Pricing: One-time purchase

6. Figma / Photoshop (Manual Approach)

Best for: Designers who need complete creative control

If you already live in Figma or Photoshop, dedicated screenshot plugins can speed up the process. Rotato for 3D device mockups and various Figma screenshot templates offer professional quality. The tradeoff is time — manual workflows take 5-10x longer than automated tools, especially when localization is involved.

Comparison Table

Feature	Shotlingo	AppScreens	Screenshots.pro	Mockupper	Apple Framer
Free tier	Yes	Trial	Watermarked	Yes	No
iOS + Android	Yes	Yes	Yes	Yes	iOS only
40+ languages	Yes	Limited	No	No	No
Batch export	Yes	Yes	No	Limited	Yes
Community templates	Yes	Yes	No	Limited	No
AI translation	Yes	No	No	No	No

Which One Should You Use?

The answer depends on your primary need:

If you need localization: Shotlingo is the clear winner. No other tool handles 40+ language batch export as seamlessly.
If you want the most features: AppScreens offers the broadest feature set for teams willing to pay more.
If you just need quick mockups: Screenshots.pro or Mockupper will get you there fastest.
If you are Apple-only and want perfection: Apple Framer delivers the most accurate device frames.

For most indie developers in 2026, the smartest approach is starting with a free tool to validate your app, then graduating to a localization-focused tool like Shotlingo when you are ready to scale internationally. The screenshots that convert best are the ones that speak each market's language — literally.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

10 ASO Keyword Optimization Strategies That Actually Work

Shotlingo — Tue, 14 Apr 2026 15:15:58 +0000

App Store Optimization (ASO) is not guesswork — it is a data-driven discipline. After analyzing keyword performance data from over 10,000 apps across both major app stores, we have identified the strategies that consistently deliver results. Here are 10 proven techniques to improve your app's discoverability.

1. Target Long-Tail Keywords First

New and smaller apps cannot compete for head terms like "photo editor" or "fitness tracker." Instead, target long-tail keywords — more specific phrases with lower competition but higher intent. "Photo editor with background remover" has a fraction of the search volume of "photo editor," but the users searching for it know exactly what they want and are more likely to download.

Start with 3-4 word phrases, build ranking authority, and gradually work toward more competitive terms as your app gains traction.

2. Use Apple's 100-Character Keyword Field Strategically

Apple gives you exactly 100 characters for keywords in App Store Connect. Every character counts. Follow these rules:

Use commas to separate keywords, no spaces after commas
Never repeat words already in your title or subtitle
Use singular forms only — Apple matches both singular and plural
Skip prepositions (the, a, and, or) — Apple ignores them
Include common misspellings of your competitors' names

3. Localize Your Keywords for Every Market

This is the single most underutilized ASO strategy. Localized keywords dramatically reduce competition because most developers only optimize in English. In the Japan App Store, Japanese keywords have 10x less competition than equivalent English keywords for the same search intent.

Apple allows separate keyword sets for each localization, and some localizations serve multiple countries. The UK English localization, for instance, serves users in the UK, Australia, and several other English-speaking markets. Use this to your advantage by targeting region-specific terms.

4. Leverage Google Play's Full-Text Indexing

Unlike Apple, Google Play indexes your full app description for keywords. This means your 4,000-character description is a massive keyword opportunity. Write naturally but strategically — include target keywords 3-5 times each throughout the description without keyword stuffing.

Google's algorithm is sophisticated enough to understand synonyms and related terms. If you target "budget planner," Google will also consider your app for "expense tracker" and "money manager" searches.

5. Analyze Competitor Keywords

Your competitors have already done keyword research for you. Use ASO tools to identify which keywords your top competitors rank for, then find gaps — keywords they rank for weakly or not at all. These gaps represent your best opportunities for quick wins.

Pay special attention to competitors who recently improved their rankings. Their keyword changes can reveal emerging search trends before they become competitive.

6. Optimize Your Subtitle (Apple) and Short Description (Google)

These fields carry significant keyword weight on both platforms. Your Apple subtitle (30 characters) and Google Play short description (80 characters) should balance keyword optimization with compelling messaging.

A/B test different versions to find the sweet spot between discoverability and conversion. A subtitle that ranks well but sounds robotic will hurt your conversion rate.

7. Update Keywords Seasonally

Search behavior changes throughout the year. Fitness apps see massive keyword volume shifts in January. Shopping apps peak during holiday seasons. Tax apps spike in spring. Align your keyword strategy with these seasonal patterns.

Set a calendar reminder to review and update keywords at least quarterly. Even non-seasonal apps benefit from fresh keyword analysis as search trends evolve.

8. Use Category Rankings as a Keyword Signal

Your app's category affects how both stores interpret your keywords. An app in the "Productivity" category with the keyword "notes" will be treated differently than a "Music" app with the same keyword. Choose your primary and secondary categories strategically to reinforce your target keyword themes.

9. Monitor and React to Keyword Difficulty

Keyword difficulty is not static — it changes as competitors enter and leave the market. A keyword that was easy to rank for six months ago might now be dominated by well-funded competitors. Conversely, keywords abandoned by competitors become easier to capture.

Track your keyword difficulty scores weekly and be prepared to pivot. The fastest way to improve visibility is to find and dominate low-difficulty, medium-volume keywords before your competitors do.

10. Combine ASO With Paid Search Intelligence

If you run Apple Search Ads or Google App campaigns, use the search term reports to discover real user queries that you might be missing in your organic keyword strategy. Search ads data reveals exactly what users type, including variations and phrases you would never think of on your own.

Feed these discoveries back into your organic keyword strategy. The best ASO practitioners use paid and organic as complementary channels, each informing the other.

Putting It All Together

Effective ASO keyword optimization is an ongoing process, not a one-time setup. The apps that consistently rank well are the ones that treat keywords as a living strategy — testing, measuring, and adapting based on real performance data. Start with these 10 strategies, measure their impact over 4-6 weeks, and iterate based on what moves the needle for your specific app and market.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

The Ultimate Guide to App Store Screenshots in 2026

Shotlingo — Tue, 14 Apr 2026 15:15:54 +0000

Your app store screenshots are the single most influential factor in whether a user downloads your app or scrolls past it. Research consistently shows that over 60% of users never read the app description — they make their decision based on visuals alone. In 2026, with over 5 million apps across the App Store and Google Play, the stakes for getting your screenshots right have never been higher.

Why Screenshots Matter More Than Ever

The app store landscape has evolved dramatically. Users are bombarded with choices, and their attention spans continue to shrink. Apple and Google have both refined their store layouts to give screenshots even more visual real estate, making them the primary conversion tool for any app listing.

According to recent ASO (App Store Optimization) studies, optimized screenshots can increase conversion rates by 25-40%. That means if your app gets 10,000 impressions per day, better screenshots alone could bring you 2,500 to 4,000 additional downloads per month — without spending a single dollar on advertising.

The Anatomy of a High-Converting Screenshot

Every effective app store screenshot follows a proven structure that combines visual appeal with clear messaging:

Headline text: A concise, benefit-driven message at the top or bottom of the screenshot. Focus on what the user gains, not what the feature does.
Device frame: A realistic or stylized device mockup that contextualizes your app's interface. In 2026, frameless designs are trending for a cleaner look.
UI showcase: The actual app screen showing the feature in action. Use real data that looks appealing, not placeholder content.
Visual hierarchy: Guide the viewer's eye from headline to UI naturally using color contrast, size, and positioning.

Design Principles for 2026

1. Lead With Your Strongest Screen

Your first screenshot gets 80% of the views. Make it count by showcasing your app's core value proposition — the single most compelling reason someone should download your app. Don't waste it on a splash screen or login page.

2. Tell a Story Across Screenshots

Treat your screenshot set as a narrative. The first screenshot hooks attention, the middle ones demonstrate key features, and the final screenshot should include a call-to-action or social proof. Users who swipe through all screenshots are 2x more likely to install.

3. Use Bold, Readable Typography

Screenshot text must be legible at small sizes — many users browse on their phones. Use a minimum of 40pt equivalent text, high-contrast colors, and keep headlines to 5-7 words maximum. Sans-serif fonts consistently outperform serif fonts in mobile contexts.

4. Embrace Consistent Branding

Your screenshots should feel like they belong to the same family. Use consistent colors, fonts, and layout patterns. This builds trust and professionalism. A polished screenshot set signals a polished app.

Screenshot Specifications in 2026

Both major platforms have specific requirements that you must follow:

Apple App Store: Up to 10 screenshots per localization. Required sizes include 6.7" (1290 x 2796px), 6.5" (1284 x 2778px), and 5.5" (1242 x 2208px) for iPhones. iPad screenshots are mandatory if your app supports iPad.
Google Play Store: Up to 8 screenshots per listing. Minimum 320px, maximum 3840px on any side. 16:9 or 9:16 aspect ratios are recommended. Google Play also supports video previews that auto-play in search results.

The Localization Advantage

Here is where most developers leave massive value on the table. Localizing your screenshots for different markets can increase downloads by 30-80% in those regions. This doesn't mean just translating the text — it means adapting the visuals, cultural references, and even the featured content to resonate with local audiences.

Tools like Shotlingo make this process dramatically faster by allowing you to manage translations across 40+ languages and export localized screenshots in bulk. What used to take days of manual work in Figma or Photoshop can now be accomplished in minutes.

Common Mistakes to Avoid

Too much text: If your screenshot looks like a blog post, you've gone too far. Keep text minimal and impactful.
Outdated UI: Nothing kills trust faster than screenshots showing an old version of your app. Update them with every major release.
Ignoring dark mode: With over 80% of users preferring dark mode, consider showing your app in dark mode for at least some screenshots.
Generic backgrounds: Avoid plain white or gradient backgrounds that blend with the store. Use colors that make your screenshots pop in search results.

Measuring Screenshot Performance

Both platforms provide analytics to measure how your screenshots perform. Apple's App Analytics shows impression-to-download conversion rates, while Google Play Console offers store listing experiments for A/B testing. Use these tools to continuously refine your approach.

The most successful app developers treat their screenshots as a living asset — updating them seasonally, testing variations, and adapting to changing trends. Your screenshots are not a set-it-and-forget-it task; they are an ongoing optimization opportunity that directly impacts your bottom line.

Start by auditing your current screenshots against the principles in this guide. Even small improvements — better headlines, stronger first screenshots, or basic localization — can yield significant results in your download numbers.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

App Store Screenshot Sizes 2026: Every Device, Every Dimension

Shotlingo — Tue, 14 Apr 2026 15:15:49 +0000

Why exact sizes matter

Upload a screenshot that is even 1 pixel off and App Store Connect will reject it silently. Google Play is more forgiving on dimensions but will down-scale images that do not match, making them look blurry on high-DPI screens.

This post is a single-source reference you can bookmark. Every dimension below is verified against Apple and Google documentation as of April 2026.

iPhone Screenshot Sizes

Device	Display	Portrait (px)	Landscape (px)
iPhone 16 Pro Max	6.9 inch	1320 x 2868	2868 x 1320
iPhone 16 Pro	6.3 inch	1206 x 2622	2622 x 1206
iPhone 16 / 15 / 14	6.1 inch	1170 x 2532	2532 x 1170
iPhone SE (3rd gen)	4.7 inch	750 x 1334	1334 x 750

iPad Screenshot Sizes

Device	Display	Portrait (px)	Landscape (px)
iPad Pro 13 inch (M4)	13 inch	2064 x 2752	2752 x 2064
iPad Pro 11 inch	11 inch	1668 x 2388	2388 x 1668
iPad Air / iPad 10th gen	10.9 inch	1640 x 2360	2360 x 1640

Google Play Screenshot Sizes

Google Play does not enforce exact pixel dimensions per device. Instead it uses flexible rules:

Minimum: 320 px on shortest side
Maximum: 3840 px on longest side
Aspect ratio: maximum 2:1
Format: JPEG or 24-bit PNG (no alpha)
Count: Minimum 2, maximum 8 per device type

Feature Graphic (required)

Exactly 1024 x 500 px. This is a marketing banner, not a screenshot. It appears at the top of your Play Store listing.

Apple Watch and Mac (if applicable)

Device	Size
Apple Watch Ultra 2	410 x 502
Apple Watch Series 9 (45mm)	396 x 484
Mac	1280 x 800 (minimum), 2880 x 1800 (recommended)

Pro tip: locale codes are not dimensions, but they trip people up just as often

When you upload localized screenshots, you need the correct locale code for each market. Apple uses zh-Hans for Simplified Chinese. Google uses zh-CN. Mix them up and your screenshots appear under the wrong locale.

Use our free App Store Locale Code Lookup to find the right code for every platform.

Export all sizes in one click

Manually resizing 10 screenshots for 5 devices and 20 languages means 1,000 images. Shotlingo handles this automatically: design once, export every size and language.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

App Store Screenshot Sizes 2026 — Complete Guide for Every iPhone & iPad

Shotlingo — Tue, 14 Apr 2026 15:15:45 +0000

Getting your app store screenshot sizes wrong means rejection from App Store Connect or blurry, cropped images on Google Play. Both platforms have strict dimension requirements that change as new devices launch. This guide covers every size you need in 2026 — no guessing, no outdated specs.

Apple App Store Screenshot Sizes

Apple requires screenshots for each device size your app supports. You must provide at least one set, but localizing for each device size improves how your listing appears on different hardware.

iPhone Screenshots (Required)

Display Size	Device Examples	Portrait (px)	Landscape (px)
6.9"	iPhone 16 Pro Max	1320 × 2868	2868 × 1320
6.7"	iPhone 15 Pro Max, 15 Plus, 14 Pro Max	1290 × 2796	2796 × 1290
6.5"	iPhone 14 Plus, 13 Pro Max, 12 Pro Max, 11 Pro Max, XS Max	1284 × 2778	2778 × 1284
6.1"	iPhone 16, 15, 14, 13, 12	1170 × 2532	2532 × 1170
5.5"	iPhone 8 Plus, 7 Plus, 6s Plus	1242 × 2208	2208 × 1242

Minimum required: You must upload screenshots for the 6.7" size (or 6.9" for iPhone 16 Pro Max). Apple will scale these down for smaller devices if you do not provide device-specific sets. However, providing all sizes ensures the best visual quality across devices.

Maximum screenshots: 10 per localization per device size.

iPad Screenshots (Required if your app runs on iPad)

Display Size	Device Examples	Portrait (px)	Landscape (px)
13" iPad Pro M4	iPad Pro 13-inch (M4)	2064 × 2752	2752 × 2064
12.9" iPad Pro	iPad Pro 12.9" (3rd-6th gen)	2048 × 2732	2732 × 2048
11" iPad Pro	iPad Pro 11", iPad Air (4th-5th gen)	1668 × 2388	2388 × 1668
10.5"	iPad Air (3rd gen), iPad (7th-9th gen)	1668 × 2224	2224 × 1668
9.7"	iPad (5th-6th gen), iPad Air 2	1536 × 2048	2048 × 1536

Apple Watch, Mac, and Apple TV

Platform	Size (px)	Notes
Apple Watch Ultra (49mm)	410 × 502	Required if app supports Ultra
Apple Watch Series (45mm)	396 × 484	Most common watch size
Apple Watch (41mm)	360 × 440	Smaller watch variant
Mac	1280 × 800 (min) to 2880 × 1800	For Mac apps or Catalyst
Apple TV	1920 × 1080 or 3840 × 2160	For tvOS apps

Google Play Store Screenshot Sizes

Google Play is more flexible than Apple but has its own requirements:

Requirement	Value
Minimum dimension	320px (any side)
Maximum dimension	3840px (any side)
Aspect ratio	No wider/taller than 2:1
Recommended phone	1080 × 1920 (9:16)
Recommended tablet (7")	1200 × 1920
Recommended tablet (10")	1600 × 2560
Maximum screenshots	8 per listing type
File format	JPEG or PNG (no alpha)
Max file size	8 MB per image

Pro tip: Design your screenshots at 1242×2208 (iPhone 5.5" size) or 1290×2796 (iPhone 6.7" size), and they will work for both App Store and Google Play with minimal adjustment. Most screenshot generators, including Shotlingo, support dual-platform export from a single template.

Common Size Mistakes and How to Avoid Them

1. Using the Wrong Aspect Ratio

Apple is strict about dimensions. If you upload a 1080×1920 image where 1290×2796 is expected, it will be rejected. Always check the exact pixel requirements for each device class.

2. Ignoring iPad Requirements

If your app is a universal binary (runs on both iPhone and iPad), you must provide iPad screenshots. Many developers forget this, leading to rejection or a poor listing where Apple auto-scales your iPhone screenshots to iPad dimensions — they look terrible.

3. Exceeding File Size Limits

Apple allows up to 10 MB per screenshot but recommends keeping them under 5 MB for faster loading. Google Play caps at 8 MB. Use JPEG at 85-90% quality for photographic content or PNG for text-heavy designs with flat colors.

4. Forgetting Retina Density

All Apple screenshot sizes are in actual pixels (not points). A 6.7" iPhone has a 3x Retina display, so the 1290×2796 pixel requirement corresponds to 430×932 points. Design at pixel dimensions, not point dimensions.

Quick Reference: What to Upload for a Typical App in 2026

If you want to cover the majority of users with minimum effort:

iPhone: 6.7" (1290×2796) — covers iPhone 15 Pro Max, 15 Plus, 14 Pro Max. Apple scales for smaller devices.
iPhone 16 Pro Max: 6.9" (1320×2868) — if you want to look sharp on the latest hardware.
iPad: 12.9" (2048×2732) — covers all iPads via scaling.
Google Play: 1080×1920 — the sweet spot for most Android phones.

For the best possible listing, provide all device sizes and localize for your top markets. Tools like Shotlingo handle the size variations automatically — you design once at your preferred canvas size, and the tool exports correctly sized versions for every device and both platforms.

File Format Recommendations

PNG: Best for screenshots with text overlays, flat colors, and sharp edges. Larger file size but lossless quality.
JPEG (85-90% quality): Best for screenshots with photographic backgrounds or complex gradients. Smaller file size with minimal visible quality loss.
Avoid: WebP (not accepted by App Store Connect), GIF, BMP, or any format with alpha transparency on Google Play.

Bookmark this page — we update it whenever Apple or Google changes their requirements. Last verified: April 2026.

Originally published on Shotlingo — an AI-powered tool for localizing App Store screenshots to 40+ languages. Free tier available at shotlingo.com.

App Store Screenshot Requirements in 2026: Complete Checklist

Shotlingo — Tue, 14 Apr 2026 15:15:41 +0000

App Store Connect Screenshot Requirements (iOS)

Apple requires screenshots for every device size you support. Miss one size and your listing shows a scaled-down version that looks blurry. Here are the exact pixel dimensions as of April 2026:

iPhone Screenshots

Device	Size (px)	Required?
iPhone 16 Pro Max (6.9in)	1320 x 2868	Required for all new submissions
iPhone 16 Pro (6.3in)	1206 x 2622	Optional (falls back to 6.9in)
iPhone SE / 8 (4.7in)	750 x 1334	Optional but recommended

Number of screenshots: Minimum 1, maximum 10. Apple recommends at least 4. The first 3 appear in search results without tapping - these are your conversion drivers.

iPad Screenshots

Device	Size (px)	Required?
iPad Pro 13in (M4)	2064 x 2752	Required if your app runs on iPad
iPad Pro 11in	1668 x 2388	Optional

Format Rules

PNG or JPEG only (no WebP, no AVIF)
RGB color space (not CMYK)
No alpha transparency on iPhone screenshots
Landscape or portrait - but be consistent within a set
No device bezels in the image itself (Apple adds them in the listing)

Google Play Console Screenshot Requirements (Android)

Google Play is more flexible than Apple but has its own gotchas:

Phone Screenshots

Type	Size	Required?
Phone	Min 320px, max 3840px on any side. Aspect ratio max 2:1	At least 2 screenshots required
7in Tablet	Same range	Optional but recommended
10in Tablet	Same range	Optional but recommended

Feature Graphic

Google Play requires a feature graphic (1024 x 500 px) that appears at the top of your listing. This is NOT a screenshot - it is a marketing banner.

The Localization Trap

Both Apple and Google allow you to upload separate screenshots per locale. If you only upload English screenshots, users in Japan, Germany, and Brazil see English text - and your conversion rate in those markets drops by 30-60%.

The fix: localize your screenshots for every market you target. German text is 35% longer than English. Arabic reads right-to-left.

Estimate text growth with our free Text Expansion Calculator, and look up locale codes with our Locale Code Lookup.

Common Rejection Reasons

Wrong dimensions - the single most common rejection.
Misleading screenshots - showing features that do not exist.
Device bezels in the image - Apple adds their own frames.
Text too small to read at search-result size.
Localization mismatch - English screenshots in a Japanese locale slot.

Submission Checklist

iPhone 16 Pro Max at 1320 x 2868
iPad Pro 13in at 2064 x 2752 (if iPad supported)
Google Play feature graphic at 1024 x 500
At least 4 screenshots per device (Apple) / 2 (Google)
First 3 screenshots tell a complete story
Screenshots localized for top 5 target markets
No device bezels baked into the image
PNG or JPEG, RGB, no transparency

Generate localized screenshots automatically - Try Shotlingo free.