For developers · Checked 30 September 2026

Google Play’s photo and video permissions policy, explained

Short answer: if your app targets Android 13 (API level 33) or higher, it may request READ_MEDIA_IMAGES or READ_MEDIA_VIDEO only when its core functionality needs broad access to photos and videos, such as a gallery app, and it must explain why in a declaration in Play Console. Every other app has to use the Android photo picker or another system picker. Full compliance has been mandatory since May 28, 2025, and apps that do not comply can be removed from Google Play.

Which path fits your app

From Play Console Help «Details on Google Play’s Photo and Video Permissions policy», read 30 September 2026.

Your appWhat to use
Picks a photo or video now and then (avatar, attachment, post)Android photo picker or another system picker, no media permission
Core function is broad access to photos and videos (gallery, backup, editor working on the whole library)READ_MEDIA_IMAGES / READ_MEDIA_VIDEO, plus a Play Console declaration
Has its own custom picker UIA custom picker alone does not qualify; the declaration must show the photo picker cannot meet the need

What the policy covers

The policy restricts two permissions, READ_MEDIA_IMAGES and READ_MEDIA_VIDEO, for apps that target Android 13 or higher. Google’s position is that most apps only need a user to choose specific items, and the system photo picker does that without giving the app the whole library. Broad access stays available to apps whose core functionality revolves around it.

Who may keep the permissions

Apps whose core functionality is broad access to photos and videos, gallery apps and similar tools where the system photo picker cannot meet the technical need. Having a custom picker is not a reason by itself: you have to show in the Play Console declaration why the Android photo picker is insufficient for what your app does.

How to comply if you only pick media occasionally

Remove READ_MEDIA_IMAGES and READ_MEDIA_VIDEO from the manifest, including those merged in from libraries, and open the Android photo picker or another system picker where the user chooses media. Check the merged manifest after the build, because an SDK can add a permission you never wrote. Then publish the update so the version without the permissions replaces the old one on every active track.

If you get an «invalid use» rejection

Decide which case you are. If the app does not need the whole library, remove the permissions and move to the photo picker; that is the fastest route back. If broad access is your core function, fill in the declaration in Play Console and describe the feature that needs it and why the photo picker cannot do the job. Google has required full compliance since May 28, 2025 for everyone, including developers who had an extension.

Where Censuus fits

Staying on Google Play is the floor; being found is the rest. Censuus ranks apps by the visits they draw, and adding your app is free on the List my app form. Placement comes from traffic and sponsorship: apps climb on the visits they draw, and a sponsor can pay to rise higher.

Frequently asked questions

Which permissions does the Google Play photo and video policy cover?

READ_MEDIA_IMAGES and READ_MEDIA_VIDEO, for apps targeting Android 13 (API level 33) or higher.

What should apps use instead of READ_MEDIA_IMAGES?

The Android photo picker or another system picker, unless broad access to photos and videos is the app’s core functionality.

Is a custom photo picker a valid reason to keep the permission?

No. Google says a custom picker alone does not qualify; you must show why the Android photo picker is insufficient.

What is the deadline for the photo and video permissions policy?

Full compliance has been mandatory since May 28, 2025, including for developers who requested an extension; non-compliant apps can be removed.

Guides for app developers

Put your app in the ranking

Censuus ranks apps by the visits they draw and by sponsorship, no bots. Listing is free; sponsorship raises placement.