We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Provides developers and users with instant plain English names and functional descriptions for standard Android permission strings.
This is a locally maintained static reference table, not a live official directory, current policy or complete collection. Records without a named source and update date remain unverified.
Selected permission names, added API levels and protection levels checked against Android documentation on 2026-09-29. Grant behavior depends on OS, targetSdk and purpose; coarse/fine location never guarantees a fixed meter accuracy. Reference
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This table is a compact way to look up a curated set of 21 Android permission identifiers. Each row shows the permission constant, the API level where it was added, and its protection level. For example, android.permission.POST_NOTIFICATIONS is listed as added in API level 33, while android.permission.CAMERA is listed as added in API level 1. These are reference fields, not a report about any particular app or device.
A protection level describes how Android controls a permission. The table's normal and dangerous labels help orient a first review, but they do not tell you whether an app has received access or what it does with that access.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Enter all or part of a constant, such as READ_CONTACTS or android.permission.READ_CONTACTS. The table filters rows as the text matches their displayed values, so a partial name can be useful when you only remember one segment.
Compare the full identifier with the added API level and protection level. Use the column headings to sort, the column menu to hide fields, and the page controls to move through the filtered results.
For a code review, record the app's target SDK and the Android version in scope, then open the official Manifest.permission reference and check the specific constant. If you are implementing a runtime request, also follow Android's runtime permission guidance.
Use cases
See how the tool fits into real work and everyday tasks.
When reading a permission declaration in a project, search the identifier to get a quick orientation to its listed API level and protection label before checking the exact Android reference.
Use the table to make a short list of permission constants that need discussion. Review the app's purpose and implementation separately; the table does not inspect source code or explain why an app requests a permission.
Compare familiar entries such as camera, contacts, or notifications, then read Android's overview to understand how protection labels relate to install-time and runtime permission flows.
Q&A
Find concise answers to common questions and confusing cases.
No. This is a reference table; it does not inspect an app's manifest, device settings, or current permission grants. Check the device or app state and the relevant Android behavior separately.
The table is a selected set, not a complete registry. Try searching a shorter distinctive fragment. If there is still no match, search the official Android API reference for the exact constant.
No. A protection label alone does not determine the full user flow. Runtime behavior can depend on Android version, target SDK, permission purpose, and other rules; consult the current Android documentation for the case you are implementing.
It identifies the API level at which the permission was introduced according to the reference entry. It does not by itself say whether a particular app can use it or what behavior applies on every device version.
Notes
Review scope, result limitations, and important precautions before use.
The entries are a curated subset of Android permissions, not an exhaustive list, APK analyzer, security audit, or permission-grant checker. A permission declaration indicates a requested capability; it does not prove that the app obtained access, used it, or handled user data in a particular way. Android's rules change across OS releases and can depend on target SDK, permission purpose, and device implementation. Use the official Android documentation and the behavior of the specific app and device for security, compatibility, or release decisions.
Related
Discover related tools, collections, and available API capabilities.