How to Take Android Emulator Screenshots for Google Play

Quick answer: Click the camera (Take screenshot) button on the emulator toolbar, or run adb exec-out screencap -p > screen.png to save a full-resolution PNG. Change the folder in Extended controls > Settings > General > Screenshot save location. Before uploading to Google Play, check the shape: a 1080 × 2400 capture is longer than the store's 2:1 limit.

Every method below saves the emulated device's real pixels, not the size of the window on your monitor.

The emulator toolbar

When the emulator runs in its own window, the side toolbar has a camera icon. One click saves a PNG of the current screen. It's the fastest option for a handful of captures.

Android Studio's Running Devices window

By default, recent versions of Android Studio show the emulator inside the Running Devices tool window. Its toolbar has a screenshot icon too. Android Studio opens the capture in a preview where you can save it. Some versions also offer to wrap it in device artwork; skip that for store images, because the frame changes the pixel size and the result rarely matches a Google Play layout.

adb from the command line

adb exec-out screencap -p > screen.png streams the PNG straight to your computer. It's scriptable, gives you exact file names and works the same on physical devices with USB debugging turned on.

• Several devices running? List them with adb devices, then target one: adb -s emulator-5554 exec-out screencap -p > screen.png.
• Prefer saving on the device first? adb shell screencap -p /sdcard/screen.png followed by adb pull /sdcard/screen.png does the same in two steps.
• Why exec-out? It passes binary output through untouched. Redirecting adb shell screencap -p instead has corrupted PNGs on some setups.

Open Extended controls with the More button (three dots) on the emulator toolbar, then go to Settings > General. The Screenshot save location field shows the current folder; click the folder icon to pick another one.

Two things trip people up:

• Some extended controls only appear when the emulator runs in a separate window, outside Android Studio. If you can't find the setting, turn off the option that launches the emulator inside the Running Devices tool window (in Android Studio's settings, under Tools > Emulator) and restart the virtual device.
• The "Use detected ADB location" setting must be correct. Android's documentation notes that if it's wrong, screenshot capture doesn't work. Leave it on when you launch the emulator from Android Studio.

With adb, there's no setting at all: the file goes wherever your command says.

Notification icons, a half-empty battery and a random clock make screenshots look unfinished. Android's demo mode fixes that in two commands, plus a few for the icons:

1. adb shell settings put global sysui_demo_allowed 1
2. adb shell am broadcast -a com.android.systemui.demo -e command enter
3. adb shell am broadcast -a com.android.systemui.demo -e command clock -e hhmm 1200
4. adb shell am broadcast -a com.android.systemui.demo -e command battery -e level 100 -e plugged false
5. adb shell am broadcast -a com.android.systemui.demo -e command notifications -e visible false

Exit afterward with adb shell am broadcast -a com.android.systemui.demo -e command exit. Signal bars, Wi-Fi and the iOS equivalents are in our clean status bar guide.

Google Play currently accepts JPEG or 24-bit PNG files without alpha, 320 to 3840 px on each side, up to 8 MB, and the long side can be at most twice the short side. You need 2 to 8 screenshots per device type to publish. To be eligible for featured and recommended placements, Google asks for screenshots at least 1080 px on the short side (at least 4 for apps, 3 for games).

That 2:1 rule is the catch. Most modern phone profiles are taller than 2:1, so a raw full-screen capture can fail before you even think about design:

You have three ways out:

1. Place the capture inside a 9:16 design such as 1080 × 1920, with a headline above it. Google's own guidance recommends 9:16 portrait screenshots of at least 1080 × 1920. This is what most store listings do.
2. Crop the top and bottom of the capture to 2:1 or less. It works for simple screens but often cuts off navigation bars.
3. Create a custom hardware profile in Device Manager with a 1080 × 1920 screen. Captures upload as is, but your layout renders on a shorter screen than most users have.

Our Google Play screenshot sizes guide lists every slot, and the Google Play screenshot requirements article covers the rules in depth. For tablets and Chromebooks, see Google Play tablet screenshots. Not sure if a file fits? The free screenshot size checker shows which store slot an image matches and flags alpha channels.

• Black screenshot. Screens that use FLAG_SECURE (common for banking and password fields) capture as black. Turn the flag off in a debug or screenshot build.
• Rendering glitches. If the capture shows artifacts, change the graphics acceleration option under Settings > Advanced in Extended controls and restart the device.
• Wrong device captured. With an emulator and a phone connected, plain adb commands fail or hit the wrong target. Always pass -s with the serial.
• Landscape needed. Rotate the emulator with the toolbar's rotate buttons before capturing; games and video apps often need landscape sets.
• Alpha channel. Raw PNGs and design-tool exports can carry an alpha channel, which Google Play rejects. Export as JPEG or flattened 24-bit PNG.

For more than a few languages or devices, script it. A simple loop can open deep links with adb shell am start -a android.intent.action.VIEW -d "yourapp://screen" and capture each screen with adb exec-out screencap -p. For instrumented UI tests that switch locales and save named files, fastlane's screengrab action is the established option; our fastlane screengrab guide walks through it. Shipping on iOS too? Our Xcode simulator screenshot guide is the matching workflow.