Screenshots

Progressive Web App screenshots enable richer installation UI. As shown below, by default only the application name and short name are visible.

However, by including screenshots in the web app manifest, the installation experience can be significantly improved. These screenshots give users a visual preview of the app, enhancing their understanding and increasing the likelihood of installation.

Screenshots should showcase the most important functionalities of your application and be of high quality to attract users.

In the example below, a selection of screenshots are visible and the user can navigate to show them all. On mobile devices, the interface is different, but shows the same information.

Overview

Screenshots are an essential part of your PWA's installation experience. They help users understand what your app does before installing it.

Key benefits:

Enhanced installation UI with visual previews
Increased installation conversion rates
Showcase app's key features and functionality
Platform-specific presentation (Android, Windows, etc.)
Support for different device form factors (mobile, desktop)
Automatic format conversion and optimization

Browser/Platform Support:

Platform

Support

Display Location

Chrome (Desktop)

✅ Full

Installation dialog

Chrome (Android)

✅ Full

WebAPK install screen

Edge (Desktop)

✅ Full

Installation dialog

Windows Store

✅ Full

Store listing

Samsung Internet

✅ Full

Install prompt

Safari (iOS)

⚠️ Limited

Not displayed in install flow

Firefox

⚠️ Limited

Partial support

Basic Configuration

Simple Configuration

/config/packages/pwa.yaml

pwa:
    manifest:
        enabled: true
        screenshots:
            # Simple string format (path only)
            - "images/screenshot-feature1.png"
            - "images/screenshot-feature2.png"
            - "images/screenshot-feature3.png"

Complete Configuration

/config/packages/pwa.yaml

pwa:
    manifest:
        enabled: true
        screenshots:
            # Desktop screenshot with all parameters
            - src: "images/desktop-dashboard.png"
              width: 1920
              height: 1080
              format: "webp"
              label: "Main dashboard with analytics"
              form_factor: "wide"
              platform: "windows"

            # Mobile screenshot
            - src: "images/mobile-home.png"
              width: 1080
              height: 1920
              format: "webp"
              label: "Home screen on mobile"
              form_factor: "narrow"
              platform: "android"

            # Tablet screenshot
            - src: "images/tablet-catalog.png"
              width: 1280
              height: 800
              label: "Product catalog on tablet"
              form_factor: "wide"
              platform: "android"

Configuration Parameters

`src` Parameter

The src parameter specifies the path to your screenshot image.

Asset Mapper Integration:

screenshots:
    - src: "images/screenshot.png"  # Served via Asset Mapper

Absolute URLs:

screenshots:
    - src: "https://cdn.example.com/screenshots/app.png"

Best Practices:

Use high-quality images (Full HD or higher recommended)
Keep file sizes reasonable (< 500 KB per screenshot)
Use consistent dimensions per form factor
Prefer WebP format for smaller file sizes

`width` and `height` Parameters

Specify screenshot dimensions in pixels. If omitted, dimensions are detected automatically.

/config/packages/pwa.yaml

screenshots:
    - src: "images/desktop.png"
      width: 1920    # Width in pixels
      height: 1080   # Height in pixels

Why specify dimensions?

Improves manifest parsing performance
Ensures correct aspect ratio detection
Helps browsers choose appropriate screenshot for device
Required for some platform app stores

`format` Parameter

The format parameter specifies the image format. The bundle can automatically convert images to the specified format.

Supported formats:

"png" - Lossless, good for UI screenshots
"jpg" or "jpeg" - Lossy, smaller file sizes
"webp" - Modern format, best compression

/config/packages/pwa.yaml

screenshots:
    # Source is PNG, bundle converts to WebP
    - src: "images/screenshot.png"
      format: "webp"  # Automatic conversion!

    # Source is PNG, stays as PNG
    - src: "images/screenshot.png"
      format: "png"

    # Source is PNG, converted to JPEG
    - src: "images/screenshot.png"
      format: "jpg"

Automatic Conversion: The bundle automatically converts images when the format parameter differs from the source file format. This makes it easy to optimize all screenshots as WebP without manually converting files.

Format Recommendations:

Use Case

Recommended Format

Why

UI Screenshots

WebP or PNG

Sharp text, no artifacts

Photo-heavy screens

WebP or JPEG

Better compression for photos

Maximum compatibility

PNG

Universally supported

Smallest file size

WebP

Best compression ratio

`label` Parameter

The label parameter provides a brief description or caption for the screenshot. This helps users understand what the feature or screen is about.

/config/packages/pwa.yaml

screenshots:
    - src: "images/dashboard.png"
      label: "Main dashboard view with real-time analytics"

    - src: "images/settings.png"
      label: "Customizable settings and preferences"

Label Best Practices:

Keep labels concise (5-10 words)
Describe the feature or functionality shown
Use consistent tone across all labels
Avoid redundant information (don't repeat app name)

Translation Support:

The label parameter supports Symfony translations:

/config/packages/pwa.yaml

screenshots:
    - src: "images/dashboard.png"
      label: "app.screenshots.dashboard"  # Translation key

/translations/messages.en.yaml

app:
    screenshots:
        dashboard: "Main dashboard with analytics"
        settings: "User settings and preferences"

/translations/messages.fr.yaml

app:
    screenshots:
        dashboard: "Tableau de bord principal avec analytique"
        settings: "Paramètres et préférences utilisateur"

`platform` Parameter

The platform parameter specifies which operating system or distribution platform the screenshot is intended for. This helps display appropriate screenshots for users on different devices.

/config/packages/pwa.yaml

screenshots:
    # Android-specific screenshot
    - src: "images/android-home.png"
      platform: "android"
      label: "Home screen on Android"

    # iOS-specific screenshot
    - src: "images/ios-home.png"
      platform: "ios"
      label: "Home screen on iOS"

    # Windows-specific screenshot
    - src: "images/windows-dashboard.png"
      platform: "windows"
      label: "Dashboard on Windows"

Device Platform Identifiers:

"android" - Android devices
"chromeos" - ChromeOS devices
"ipados" - iPad devices
"ios" - iPhone devices
"kaios" - KaiOS devices
"macos" - macOS devices
"windows" - Windows devices
"xbox" - Xbox devices

Distribution Platform Identifiers:

"chrome_web_store" - Chrome Web Store
"itunes" - Apple App Store
"microsoft-inbox" - Microsoft built-in apps
"microsoft-store" - Microsoft Store
"play" - Google Play Store

If platform is not specified, the screenshot is considered universal and may be shown on any platform.

`form_factor` Parameter

The form_factor parameter defines the intended device form factor for your screenshots. This helps browsers display appropriate screenshots based on the user's device.

Possible values:

"narrow" - Best suited for narrow screen devices (phones, portrait tablets)
"wide" - Intended for wider screen devices (desktops, landscape tablets)

/config/packages/pwa.yaml

screenshots:
    # Mobile/phone screenshots
    - src: "images/mobile-1.png"
      form_factor: "narrow"
      label: "Mobile home screen"

    # Desktop/tablet screenshots
    - src: "images/desktop-1.png"
      form_factor: "wide"
      label: "Desktop dashboard"

Automatic Detection: If form_factor is not specified, it's automatically determined using the screenshot dimensions:

Aspect ratio > 1 (landscape) → "wide"
Aspect ratio ≤ 1 (portrait) → "narrow"

Form Factor Guidelines:

Form Factor

Typical Dimensions

Aspect Ratio

Use Cases

"narrow"

1080x1920 (portrait)

9:16

Phones, portrait tablets

"narrow"

750x1334 (iPhone 8)

9:16

Mobile devices

"wide"

1920x1080 (landscape)

16:9

Desktops, laptops

"wide"

1280x720 (HD)

16:9

Tablets (landscape)

`reference` Parameter

The reference parameter allows you to specify a URL reference for the screenshot. This is for documentation purposes only and is not used by the bundle in the generated manifest.

/config/packages/pwa.yaml

screenshots:
    - src: "images/dashboard.png"
      reference: "https://design.example.com/specs/dashboard-v2"
      label: "Dashboard v2 design"

Use cases:

Link to design specifications
Reference Figma or design tool URLs
Internal documentation links
Version tracking

Screenshot Creation

Recommended Dimensions

Mobile (Narrow):

Device

Resolution

Aspect Ratio

iPhone 14 Pro

1179×2556

9:19.5

iPhone 14

1170×2532

9:19.5

iPhone 8

750×1334

9:16

Android (1080p)

1080×1920

9:16

Android (720p)

720×1280

9:16

Desktop/Tablet (Wide):

Device

Resolution

Aspect Ratio

Full HD

1920×1080

16:9

1280×720

16:9

iPad Pro

2048×1536

4:3

Surface Pro

2736×1824

3:2

Screenshot Creation Methods

1. Browser DevTools (Recommended)

# Chrome/Edge DevTools
1. Open your PWA in browser (F12)
2. Click device toolbar (Ctrl+Shift+M)
3. Select target device/resolution
4. Navigate to the screen you want to capture
5. Click three-dot menu → "Capture screenshot"
# Or: Cmd/Ctrl+Shift+P → "Capture screenshot"

2. Automated Tools (Puppeteer)

scripts/generate-screenshots.js

const puppeteer = require('puppeteer');

async function captureScreenshots() {
    const browser = await puppeteer.launch();
    const page = await browser.newPage();

    // Desktop screenshot (1920x1080)
    await page.setViewport({ width: 1920, height: 1080 });
    await page.goto('https://your-app.com/dashboard');
    await page.screenshot({
        path: 'assets/images/desktop-dashboard.png',
        fullPage: false
    });

    // Mobile screenshot (1080x1920)
    await page.setViewport({ width: 1080, height: 1920 });
    await page.goto('https://your-app.com/');
    await page.screenshot({
        path: 'assets/images/mobile-home.png',
        fullPage: false
    });

    await browser.close();
}

captureScreenshots();

3. Playwright

scripts/generate-screenshots.js

const { chromium } = require('playwright');

async function captureScreenshots() {
    const browser = await chromium.launch();
    const context = await browser.newContext();
    const page = await context.newPage();

    // Desktop
    await page.setViewportSize({ width: 1920, height: 1080 });
    await page.goto('https://your-app.com/dashboard');
    await page.screenshot({
        path: 'assets/images/desktop-dashboard.png'
    });

    // Mobile
    await page.setViewportSize({ width: 1080, height: 1920 });
    await page.goto('https://your-app.com/');
    await page.screenshot({
        path: 'assets/images/mobile-home.png'
    });

    await browser.close();
}

captureScreenshots();

4. OS Screenshot Tools

Windows: Win + Shift + S
macOS: Cmd + Shift + 4 (select area) or Cmd + Shift + 5 (advanced)
Linux: PrtScn or Shift + PrtScn

Complete Use Cases

Use Case 1: E-Commerce App

/config/packages/pwa.yaml

pwa:
    manifest:
        name: "ShopPro"
        short_name: "ShopPro"
        screenshots:
            # Desktop screenshots
            - src: "screenshots/desktop-home.png"
              width: 1920
              height: 1080
              format: "webp"
              label: "Browse thousands of products"
              form_factor: "wide"
              platform: "windows"

            - src: "screenshots/desktop-cart.png"
              width: 1920
              height: 1080
              format: "webp"
              label: "Simple checkout process"
              form_factor: "wide"
              platform: "windows"

            - src: "screenshots/desktop-product.png"
              width: 1920
              height: 1080
              format: "webp"
              label: "Detailed product views"
              form_factor: "wide"
              platform: "windows"

            # Mobile screenshots
            - src: "screenshots/mobile-home.png"
              width: 1080
              height: 1920
              format: "webp"
              label: "Shop on the go"
              form_factor: "narrow"
              platform: "android"

            - src: "screenshots/mobile-search.png"
              width: 1080
              height: 1920
              format: "webp"
              label: "Fast product search"
              form_factor: "narrow"
              platform: "android"

            - src: "screenshots/mobile-orders.png"
              width: 1080
              height: 1920
              format: "webp"
              label: "Track your orders"
              form_factor: "narrow"
              platform: "android"

Use Case 2: Productivity App with Platform-Specific Screens

/config/packages/pwa.yaml

pwa:
    manifest:
        name: "TaskMaster Pro"
        screenshots:
            # Android screenshots
            - src: "screenshots/android-tasks.png"
              width: 1080
              height: 1920
              label: "app.screenshots.tasks"
              platform: "android"
              form_factor: "narrow"

            - src: "screenshots/android-calendar.png"
              width: 1080
              height: 1920
              label: "app.screenshots.calendar"
              platform: "android"
              form_factor: "narrow"

            # iOS screenshots (different UI)
            - src: "screenshots/ios-tasks.png"
              width: 1170
              height: 2532
              label: "app.screenshots.tasks"
              platform: "ios"
              form_factor: "narrow"

            - src: "screenshots/ios-calendar.png"
              width: 1170
              height: 2532
              label: "app.screenshots.calendar"
              platform: "ios"
              form_factor: "narrow"

            # Desktop screenshots
            - src: "screenshots/windows-dashboard.png"
              width: 1920
              height: 1080
              label: "app.screenshots.dashboard"
              platform: "windows"
              form_factor: "wide"

            - src: "screenshots/macos-dashboard.png"
              width: 1920
              height: 1080
              label: "app.screenshots.dashboard"
              platform: "macos"
              form_factor: "wide"

Use Case 3: Multi-Language App

/config/packages/pwa.yaml

pwa:
    manifest:
        name: "GlobalNews"
        screenshots:
            - src: "screenshots/home-en.png"
              width: 1920
              height: 1080
              label: "news.screenshots.home"
              form_factor: "wide"

            - src: "screenshots/articles-en.png"
              width: 1920
              height: 1080
              label: "news.screenshots.articles"
              form_factor: "wide"

            - src: "screenshots/mobile-en.png"
              width: 1080
              height: 1920
              label: "news.screenshots.mobile"
              form_factor: "narrow"

/translations/messages.en.yaml

news:
    screenshots:
        home: "Breaking news from around the world"
        articles: "In-depth articles and analysis"
        mobile: "Stay informed on the go"

/translations/messages.fr.yaml

news:
    screenshots:
        home: "Actualités du monde entier"
        articles: "Articles et analyses approfondis"
        mobile: "Restez informé en déplacement"

Screenshot Optimization

File Size Optimization

1. Use WebP Format

WebP typically provides 25-35% better compression than PNG or JPEG:

/config/packages/pwa.yaml

screenshots:
    # Bundle automatically converts PNG to WebP
    - src: "screenshots/dashboard.png"
      format: "webp"  # Auto-conversion!

2. Optimize Before Upload

Using command-line tools:

# Using ImageMagick
convert input.png -quality 85 -define webp:lossless=false output.webp

# Using cwebp (WebP encoder)
cwebp -q 80 input.png -o output.webp

# Using pngquant (for PNG)
pngquant --quality=65-80 input.png -o output.png

3. Compress Existing Images

Using Node.js with Sharp:

scripts/optimize-screenshots.js

const sharp = require('sharp');
const fs = require('fs');
const path = require('path');

const screenshotsDir = 'assets/images/screenshots';
const outputDir = 'assets/images/screenshots-optimized';

fs.readdirSync(screenshotsDir).forEach(file => {
    const inputPath = path.join(screenshotsDir, file);
    const outputPath = path.join(outputDir, file.replace(/\.(png|jpg)$/, '.webp'));

    sharp(inputPath)
        .webp({ quality: 80 })
        .toFile(outputPath)
        .then(info => console.log(`Optimized ${file}: ${info.size} bytes`))
        .catch(err => console.error(`Error processing ${file}:`, err));
});

File Size Guidelines

Screenshot Type

Target Size

Maximum Size

Mobile (narrow)

< 200 KB

< 500 KB

Desktop (wide)

< 300 KB

< 800 KB

Total (all screenshots)

< 2 MB

< 5 MB

Image Quality Best Practices

Use high-resolution source
- Capture at actual device resolution (not scaled up)
- Use 2x or 3x scale for retina displays
Remove sensitive information
- No real user data
- No API keys or tokens visible
- Use placeholder/demo content
Consistent visual design
- Same theme (light/dark) across all screenshots
- Consistent UI state (logged in, data loaded)
- Professional appearance (no dev tools, no errors)
Optimize content
- Show actual features, not loading states
- Include realistic but anonymized data
- Highlight key functionality

Platform-Specific Requirements

Android / Google Play

Requirements:

Minimum: 2 screenshots
Maximum: 8 screenshots
Format: PNG or JPEG
Dimensions: 320px - 3840px (width or height)
Aspect ratio: 16:9 or 9:16 recommended

/config/packages/pwa.yaml

screenshots:
    - src: "screenshots/android-1.png"
      width: 1080
      height: 1920
      platform: "android"
      form_factor: "narrow"
      label: "Home screen"

    - src: "screenshots/android-2.png"
      width: 1080
      height: 1920
      platform: "android"
      form_factor: "narrow"
      label: "Features view"

iOS / App Store

Requirements:

Screenshots for each supported device size
Format: PNG or JPEG
No transparency
Actual device screenshots preferred
Different sizes for iPhone and iPad

/config/packages/pwa.yaml

screenshots:
    # iPhone 14 Pro
    - src: "screenshots/iphone-14-pro-1.png"
      width: 1179
      height: 2556
      platform: "ios"
      form_factor: "narrow"

    # iPad Pro
    - src: "screenshots/ipad-pro-1.png"
      width: 2048
      height: 2732
      platform: "ipados"
      form_factor: "narrow"

Windows / Microsoft Store

Requirements:

Minimum: 1 screenshot
Format: PNG, JPEG, or GIF
Dimensions: Minimum 1366×768 or larger
Aspect ratio: 16:9 recommended

/config/packages/pwa.yaml

screenshots:
    - src: "screenshots/windows-1.png"
      width: 1920
      height: 1080
      platform: "windows"
      form_factor: "wide"
      label: "Dashboard on Windows"

Testing Screenshots

1. Validate in Manifest

Check that screenshots are correctly included in the generated manifest:

# Open your manifest.json
curl https://your-app.com/manifest.json | jq '.screenshots'

Expected output:

[
  {
    "src": "/assets/images/screenshot-abc123.webp",
    "sizes": "1920x1080",
    "type": "image/webp",
    "label": "Dashboard view",
    "form_factor": "wide"
  }
]

2. Browser DevTools

1. Open DevTools (F12)
2. Go to Application tab
3. Click "Manifest" in sidebar
4. Scroll to "Screenshots" section
5. Verify:
   - All screenshots are listed
   - Images load correctly
   - Dimensions are correct
   - Labels appear properly

3. Test Installation Flow

Desktop:

1. Open your PWA in Chrome/Edge
2. Click install button (or three-dot menu → "Install")
3. Verify screenshots appear in install dialog
4. Check that they're sharp and properly sized

Android:

1. Open your PWA in Chrome for Android
2. Trigger "Add to Home Screen" prompt
3. Verify screenshots appear in WebAPK install screen
4. Swipe through screenshots
5. Verify labels are visible

4. Lighthouse PWA Audit

# Run Lighthouse audit
npx lighthouse https://your-app.com --view --preset=desktop

# Check PWA category
# Look for "Provides screenshots" check

Best Practices

1. Quantity and Sequence

Recommended number:

Minimum: 3 screenshots
Ideal: 4-6 screenshots
Maximum: 8 screenshots (platform limit)

Logical sequence:

/config/packages/pwa.yaml

screenshots:
    # 1. Welcome/landing screen
    - src: "screenshots/01-welcome.png"
      label: "Welcome to TaskMaster"

    # 2. Main interface
    - src: "screenshots/02-dashboard.png"
      label: "Your task dashboard"

    # 3. Key feature #1
    - src: "screenshots/03-create-task.png"
      label: "Create tasks quickly"

    # 4. Key feature #2
    - src: "screenshots/04-calendar.png"
      label: "Calendar integration"

    # 5. Additional value
    - src: "screenshots/05-reports.png"
      label: "Track your productivity"

2. Content Quality

# ✅ Good - Shows real feature with clear UI
screenshots:
    - src: "screenshots/dashboard-with-data.png"
      label: "Real-time analytics dashboard"

# ❌ Avoid - Empty state, no value shown
screenshots:
    - src: "screenshots/empty-dashboard.png"
      label: "Dashboard"

Quality checklist:

Show actual features, not loading screens
Use realistic but anonymized data
Remove developer tools, debug info
Ensure text is readable
Check for spelling errors in UI
Verify consistent theme (all light or all dark)

3. Form Factor Strategy

Provide screenshots for both narrow and wide form factors:

/config/packages/pwa.yaml

screenshots:
    # Mobile-first (narrow)
    - src: "screenshots/mobile-home.png"
      form_factor: "narrow"
    - src: "screenshots/mobile-features.png"
      form_factor: "narrow"
    - src: "screenshots/mobile-settings.png"
      form_factor: "narrow"

    # Desktop (wide)
    - src: "screenshots/desktop-dashboard.png"
      form_factor: "wide"
    - src: "screenshots/desktop-features.png"
      form_factor: "wide"
    - src: "screenshots/desktop-settings.png"
      form_factor: "wide"

4. Performance Optimization

Minimize file sizes:

screenshots:
    # Use WebP format
    - src: "screenshots/home.png"
      format: "webp"

    # Specify dimensions to avoid browser detection
    - src: "screenshots/dashboard.png"
      width: 1920
      height: 1080
      format: "webp"

5. Accessibility

Descriptive labels:

# ✅ Good - Describes what's shown
screenshots:
    - src: "screenshots/dashboard.png"
      label: "Dashboard showing sales analytics and charts"

# ❌ Avoid - Too generic
screenshots:
    - src: "screenshots/dashboard.png"
      label: "Dashboard"

6. Localization

Use translation keys for international apps:

/config/packages/pwa.yaml

screenshots:
    - src: "screenshots/home.png"
      label: "app.screenshots.home"
    - src: "screenshots/features.png"
      label: "app.screenshots.features"

Common Issues

1. Screenshots Not Appearing in Install Dialog

Problem: Screenshots configured but not showing during installation

Solutions:

# ✅ Check 1: Verify screenshots are in manifest
# Visit https://your-app.com/manifest.json

# ✅ Check 2: Ensure images are accessible
# Open screenshot URLs directly in browser

# ✅ Check 3: Clear cache and reinstall

# Clear cache in Chrome
1. Open chrome://serviceworker-internals/
2. Unregister service worker
3. Clear browser cache (Ctrl+Shift+Del)
4. Reload app and reinstall

2. Screenshots Appear Blurry or Pixelated

Problem: Low quality or incorrect dimensions

Solutions:

# ✅ Use high-resolution source images
screenshots:
    - src: "screenshots/dashboard-fullhd.png"  # 1920x1080
      width: 1920
      height: 1080

# ❌ Avoid upscaling small images
screenshots:
    - src: "screenshots/dashboard-small.png"  # 640x480 scaled up
      width: 1920
      height: 1080

3. Wrong Screenshots Shown for Device

Problem: Desktop screenshots shown on mobile or vice versa

Solutions:

# ✅ Explicitly set form_factor
screenshots:
    - src: "screenshots/mobile.png"
      form_factor: "narrow"  # For phones

    - src: "screenshots/desktop.png"
      form_factor: "wide"    # For desktops

4. Screenshots Not Converting to WebP

Problem: format: "webp" specified but images not converting

Solutions:

# ✅ Check 1: Ensure GD or Imagick extension installed
php -m | grep -i gd
php -m | grep -i imagick

# ✅ Check 2: Verify file permissions
ls -la assets/images/screenshots/

# ✅ Check 3: Check logs for conversion errors
php bin/console debug:container pwa

5. File Size Too Large

Problem: Screenshots causing slow manifest loading

Solutions:

# ✅ Use WebP with compression
screenshots:
    - src: "screenshots/large.png"
      format: "webp"  # Smaller file size

# ✅ Reduce screenshot dimensions if excessive
# Instead of 4K (3840x2160), use Full HD (1920x1080)

Troubleshooting Checklist

Before submitting your PWA:

Icons - Icon configuration for your PWA
Application Information - App metadata configuration
Translations - Localizing your manifest

Resources

MDN Web Docs: https://developer.mozilla.org/en-US/docs/Web/Manifest/screenshots
Web.dev: https://web.dev/add-manifest/#screenshots
PWA Builder: https://www.pwabuilder.com/ - Test and validate screenshots
Chrome DevTools: https://developer.chrome.com/docs/devtools/
Puppeteer: https://pptr.dev/ - Automated screenshot generation
Playwright: https://playwright.dev/ - Browser automation
Sharp: https://sharp.pixelplumbing.com/ - Image optimization library

PreviousIcons NextShortcuts

Last updated 2 months ago

Was this helpful?

Good evening

hashtagOverview

hashtagBasic Configuration

hashtagSimple Configuration

hashtagComplete Configuration

hashtagConfiguration Parameters

hashtagsrc Parameter

hashtagwidth and height Parameters

hashtagformat Parameter

hashtaglabel Parameter

hashtagplatform Parameter

hashtagform_factor Parameter

hashtagreference Parameter

hashtagScreenshot Creation

hashtagRecommended Dimensions

hashtagScreenshot Creation Methods

hashtagComplete Use Cases

hashtagUse Case 1: E-Commerce App

hashtagUse Case 2: Productivity App with Platform-Specific Screens

hashtagUse Case 3: Multi-Language App

hashtagScreenshot Optimization

hashtagFile Size Optimization

hashtagFile Size Guidelines

hashtagImage Quality Best Practices

hashtagPlatform-Specific Requirements

hashtagAndroid / Google Play

hashtagiOS / App Store

hashtagWindows / Microsoft Store

hashtagTesting Screenshots

hashtag1. Validate in Manifest

hashtag2. Browser DevTools

hashtag3. Test Installation Flow

hashtag4. Lighthouse PWA Audit

hashtagBest Practices

hashtag1. Quantity and Sequence

hashtag2. Content Quality

hashtag3. Form Factor Strategy

hashtag4. Performance Optimization

hashtag5. Accessibility

hashtag6. Localization

hashtagCommon Issues

hashtag1. Screenshots Not Appearing in Install Dialog

hashtag2. Screenshots Appear Blurry or Pixelated

hashtag3. Wrong Screenshots Shown for Device

hashtag4. Screenshots Not Converting to WebP

hashtag5. File Size Too Large

hashtagTroubleshooting Checklist

hashtagRelated Documentation

hashtagResources

Overview

Basic Configuration

Simple Configuration

Complete Configuration

Configuration Parameters

`src` Parameter

`width` and `height` Parameters

`format` Parameter

`label` Parameter

`platform` Parameter

`form_factor` Parameter

`reference` Parameter

Screenshot Creation

Recommended Dimensions

Screenshot Creation Methods

Complete Use Cases

Use Case 1: E-Commerce App

Use Case 2: Productivity App with Platform-Specific Screens

Use Case 3: Multi-Language App

Screenshot Optimization

File Size Optimization

File Size Guidelines

Image Quality Best Practices

Platform-Specific Requirements

Android / Google Play

iOS / App Store

Windows / Microsoft Store

Testing Screenshots

1. Validate in Manifest

2. Browser DevTools

3. Test Installation Flow

4. Lighthouse PWA Audit

Best Practices

1. Quantity and Sequence

2. Content Quality

3. Form Factor Strategy

4. Performance Optimization

5. Accessibility

6. Localization

Common Issues

1. Screenshots Not Appearing in Install Dialog

2. Screenshots Appear Blurry or Pixelated

3. Wrong Screenshots Shown for Device

4. Screenshots Not Converting to WebP

5. File Size Too Large

Troubleshooting Checklist

Related Documentation

Resources