com.google.android.verifier.overlay Copy

A very small, Google-signed package with no user interface. The "overlay" suffix suggests a runtime resource overlay (RRO), a package that supplies replacement resource values for another package rather than running code of its own. Its manifest declares no permissions, its APK is roughly 8 to 21 KB, and the site's provenance data shows it only on devices running API 36 and 37 (Android 16 and 17), including Pixel phones, Samsung, Motorola, TCL and URAO devices, and the ASUS, Dell and HP Googlebook models. The overlay target and the values it changes could not be sourced, so that reading is an inference from the name and the package profile, not a documented fact. The name sits beside com.google.android.verifier, the Android Developer Verifier, which has its own note on this site. Google describes Android developer verification as a programme that checks apps are registered to a verified developer, with enforcement starting on 30 September 2026 for apps installed from participating stores in Brazil, Indonesia, Singapore and Thailand, and a wider rollout planned from 2027. No Google source found names this overlay or confirms that it configures the verifier, so treat any link between the two as likely but unconfirmed. For Android Enterprise, EMM and kiosk use, Google's developer verification FAQ states that apps distributed through an organisation's store on managed devices do not need to complete the verification requirements. That statement concerns the programme, not this package. Because the package's role is undocumented, no safe-to-disable rating is given; leave it in place unless testing on the target fleet shows otherwise.

• Android developer verification - Android Developers →
• Android developer verification FAQ - Android Developers →
• Package provenance for com.google.android.verifier.overlay - Android System App Database →
• Android Developer Verifier note - Android System App Database →

• Signed by Google's own signing key (the same key Google uses across devices), so it is a Google-provided preinstall that updates independently of the system image, though 13 different Google signing keys appear across the fleet. It also signs the Android framework, so it is a platform-level key on its device(s).
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.