How to Screenshot Android Apps That Block Screenshots

If an Android app blocks screenshots, there is no supported button or Android setting that overrides the app’s protection. A common cause is FLAG_SECURE, which tells Android to prevent screenshots and keep the window off non-secure displays such as casting. For information you are allowed to keep, use the app’s share, export, download, print, or save option, or ask the provider for an approved copy. Android documents FLAG_SECURE as a protection for sensitive screens such as banking and password-manager views.

1. First, identify what is being blocked

There are two different situations that can look alike:

• The normal screenshot shortcut is not working. The phone may use a different button sequence, or a work profile or device administrator may restrict captures.
• The app is protecting a particular screen. Android may show a message such as “Can’t take screenshot due to security policy,” or the saved capture may be blank. The app may have marked its window secure.

A screenshot failure does not prove that FLAG_SECURE is the cause. App-specific behavior, device-maker changes, Android version, and organization management can also affect capture. Try the normal system shortcut on a different, non-sensitive screen. If that works but the target app remains blocked, treat the restriction as intentional unless the app’s provider says otherwise.

2. Try Android’s normal screenshot controls

1. Open the screen you are allowed to capture.
2. Press Power + Volume Down at the same time. On some phones, press and hold Power, then tap Screenshot.
3. Use the preview to check that the image contains the expected content, then save or share it through the phone’s normal controls.
4. If the shortcut is unavailable, consult the phone maker’s instructions. Button combinations and menus vary by device.

These are the standard Android capture steps, not a way to override a protected screen. Google’s Android screenshot instructions describe the button shortcut and Power-menu alternative.

When you need a longer image

On Android 12 and later, many scrollable screens offer Capture more after a normal screenshot. It is available only on most screens that support scrolling, and it does not unlock a screen that refuses capture. If the option is missing, the screen or device may not support scrolling capture.

3. What FLAG_SECURE does

FLAG_SECURE is a window setting controlled by the app. When enabled, Android prevents the window from appearing in screenshots and on non-secure displays. An app may use it to protect credentials, financial information, private conversations, or other sensitive content from capture or screen sharing. Android describes the screenshot result in documented circumstances as blank.

For Android developers, the relevant distinction is prevention versus detection. An app can protect its own activity by setting the flag. A separate Android 14 API can notify an app that a supported user screenshot event occurred, but its callback does not provide the screenshot image. Detection is not a mechanism for retrieving or overriding a capture. See the Android screenshot detection documentation.

The flag also has platform caveats. Android notes that on Android 11 (API 30) and earlier it works reliably on around 70% of devices; that qualification applies to those older releases, not to all current devices. Android also says the flag does not always correctly predict whether screen recording is active. Device and app behavior can vary.

4. Can screen recording or casting capture it?

Do not count on either. A protected window can be withheld from non-secure displays, and a screen recording may show a blank or restricted area. Android’s documentation cautions that FLAG_SECURE does not always predict recording status correctly, so behavior is not identical across every recorder and device. A result that works on one phone is not a supported or dependable method to obtain protected content.

For an ordinary screen that permits recording, Android’s built-in controls are in Quick Settings:

1. Swipe down twice from the top of the screen.
2. Tap Screen record. If it is not visible, swipe across the tiles or use Edit to add it.
3. Choose audio or touch-display options if the device offers them, then start recording.
4. Stop from the screen-recorder notification. Recordings are typically available in the phone’s photo or gallery app.

These steps describe the normal recorder. They do not guarantee that protected app content will appear in the recording. Android’s recording guide covers the Quick Settings flow.

5. Get the information through an approved route

Choose the route that matches what you need: a copy of the underlying information, a shareable file, or a visual record. These options preserve the app’s choice about protected content.

1. Look for an in-app action. Check the relevant screen and its menus for Share, Export, Download, Print, Save, or a statement/document history. Some services let you export the data rather than capture the screen.
2. Ask the account owner or service for a copy. Request a provider-approved document, statement, receipt, or export. If the data belongs to someone else, obtain their permission.
3. Contact app support. Explain what information you need, why you need it, and what format would work. Ask whether they offer a permitted way to save or share it.
4. Check device management. If captures fail across otherwise ordinary apps on a work or school device, ask the organization’s administrator whether a policy applies.

Google Play’s Device and Network Abuse policy requires apps to respect other apps’ FLAG_SECURE declarations and prohibits bypass workarounds. It has a narrow accessibility-tool exception with limits; that is not general permission to save, transmit, or cache protected content. For this reason, rooting, modified apps, capture utilities, or accessibility tools should not be presented as routine ways around another app’s restriction.

6. If you develop the app: protect and support users deliberately

If you own the app and need to protect an activity, Android’s documented Kotlin pattern sets the flag on that window:

window?.setFlags(
    WindowManager.LayoutParams.FLAG_SECURE,
    WindowManager.LayoutParams.FLAG_SECURE
)

Use it only for views that warrant capture protection, and ensure the user has another way to retain legitimate records where appropriate. Android suggests considering a setting that lets users toggle the flag. A secure screen can prevent a user from documenting a transaction or sharing a support issue, so pair the restriction with a clear export or help path where the product allows it.

If your goal is to know when a user takes a screenshot, Android 14 provides a separate per-activity detection callback. It reports a supported hardware-button screenshot event; it does not return the image. The supported detection behavior is specific, and the API does not detect screenshot test commands such as ADB. Do not use detection as a substitute for securing sensitive content.

7. Troubleshooting common messages and outcomes

What you see	Likely explanation	What to do
“Can’t take screenshot due to security policy” in one app	The app or its screen may prohibit capture, often through a secure window flag.	Use an in-app export/share route or ask the provider for a permitted copy.
Screenshot saved, but part of it is blank	The protected window may have been withheld from the capture.	Do not assume the file is corrupted. Request the information from the service in an approved format.
Power + Volume Down does nothing	The timing, button mapping, or device instructions may differ.	Try the Power-button menu and check the manufacturer’s help page.
Capture is blocked in multiple unrelated apps	A managed-device policy or device-level behavior may be involved.	Ask the organization administrator if managed, or consult device support.
Capture more is missing	The device may be below Android 12, or that screen may not support scrolling capture.	Use the app’s own export function or capture permitted sections separately.
Screen recording shows a black area	The app may protect its window on non-secure displays.	Recording is not a reliable workaround. Ask for an approved export.

8. Reliability, privacy, and cost considerations

For an allowed screen, the built-in screenshot is usually the simplest route: it is already on the device and creates a local image. Scrolling capture depends on Android version and the screen’s support. Recording creates a video rather than a still image, can include more surrounding activity than intended, and may still omit protected content. Review the result before sharing it, especially if it contains account details or notifications.

For blocked content, repeated attempts with other capture paths are unlikely to give you a reliable, provider-approved record. An app export is often more useful than an image: it may preserve the underlying document or transaction details in a format intended to be shared. Availability depends on the app and account. There is no need to buy a separate capture app or accessory to solve a protected-screen restriction.

9. Need a screenshot of a website instead?

This Android restriction concerns a native app’s protected screen. It is different from capturing a public website in a browser or from a URL. If your actual task is documenting web pages for QA, reports, or an AI workflow, ScreenshotNeo is a website screenshot API and MCP server; it does not bypass Android app protections or capture a protected native screen.

Or skip the browser setup

For a website you are authorized to capture, ScreenshotNeo takes a screenshot from one URL request. The API supports PNG, JPEG, WebP, and PDF. Its page-cleaning steps can accept cookie or consent banners and remove supported consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Responses identify page outcomes and billing in headers: bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents and MCP clients. This is for web pages, not protected Android app screens.

Here is the supplied cURL request, saving a WebP screenshot of a public website:

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://stripe.com \
  -o shot.webp

Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

Node.js:

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://stripe.com'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));

See the ScreenshotNeo API documentation for request options and setup. The Free plan includes 1,000 shots a month with no card; paid plans start at $5 for 3,000 shots. Every feature is on every plan. Sign up for 1,000 free screenshots a month, with no card.

10. FAQ

Does a screenshot block mean my phone is broken?

Not necessarily. If the normal shortcut works elsewhere and only one app blocks capture, the app may be protecting that screen. Device or management policies can also affect capture.

Can Android 14’s screenshot detection API retrieve the image?

No. It notifies the app about a qualifying screenshot event; its callback does not provide the captured image.

Is the blank image a file-saving error?

Often the app has deliberately withheld protected content from the capture. If the app offers an export, use that to get a usable record.

Will scrolling screenshots work on a blocked screen?

No. Scrolling capture extends supported screenshots on many scrollable screens; it does not remove an app’s capture restriction.