The short answer
Every Google Pixel ships with Android: Google’s own build of it. People sometimes call it “Pixel OS”, but that is not a name Google uses; Google’s own pages speak of the phone’s “Android version”. As of September 2026 current Pixels run Android 17, which Google released on 16 June 2026 and rolled out to Pixel first. Google’s build is the open-source Android base plus Google’s own layer: Google Play services and the Play Store as privileged parts of the system, Google’s apps, and features that arrive in Pixel Drops.
GrapheneOS replaces that build with its own, also based on the Android Open Source Project, on the same hardware. It runs Android apps, the phone’s hardware security, and the camera. It removes Google’s privileged services from the system. Google Play is supported, for those who want it, and can be configured to run as an ordinary app (with strictly limited permissions) in a sandbox environment.
What Google puts on a Pixel
Android itself is open source: Google publishes it as the Android Open Source Project (AOSP), “available to anyone”. The Play Store and the Google Mobile Services suite are licensed separately, on top of it. Google describes Google Play services as “a core set of on-device background services that run on all Google-certified Android devices”; the GrapheneOS project describes the same services as “bundled into the OS in a deeply integrated way with special privileged permissions and capabilities unavailable to other service providers” competing with Google.
Updates come from Google every month, and new features arrive in Pixel Drops. Google guarantees seven years of updates for the Pixel 8 and later, and five years for the Pixel 6, Pixel 7 and Pixel Fold.
What GrapheneOS keeps
Android. GrapheneOS “starts from the strong baseline of the Android Open Source Project”. It moved to Android 17 on 18 June 2026, two days after Google.
The apps. Many Android apps install and run as they do on any Android phone. Google Play itself installs as regular apps that receive no special access or privileges. This compatibility includes Play Store and in-app purchases.
Hardware security. Installing GrapheneOS writes the project’s own verified-boot key to the Pixel secure element; the phone checks the system against it on every start, with rollback protection, as it does with Google’s key on the stock system. Hardware attestation, verified through the project’s Auditor app, is fully supported.
Camera. In the project’s words, GrapheneOS “has the same camera capabilities and quality as the stock OS”; Google’s Pixel Camera app also works and “does not require GSF or sandboxed Google Play”.
What GrapheneOS replaces
| Google’s Android on a Pixel | GrapheneOS on the same Pixel | |
|---|---|---|
| Google Play services | A privileged part of the system | An optional app with no special access, installed per profile |
| Google apps | Pre-installed | None bundled; any of them can be installed from the Play Store |
| Browser and WebView | Chrome | Vanadium, a hardened browser and WebView |
| Camera | Pixel Camera | GrapheneOS Camera; Pixel Camera optional |
| App source | Play Store | The GrapheneOS App Store, plus the Play Store if needed |
| Updates | Google’s servers | GrapheneOS servers, automatically checked about every six hours and installed in the background |
| Boot key | Google’s | The GrapheneOS key; a yellow notice on start names the alternate system |
What changes day to day
Tap to pay through Google Wallet does not work on GrapheneOS. Google states that Wallet does not run on phones with “modified factory software”. Which banking apps, Diia and Reserv+ work, as tested, is in our article on banking apps and Diia.
Some banking and government apps check the system. GrapheneOS passes the basic integrity check but is not certified by Google. An app that insists on Google’s certification may refuse.
eSIM needs one switch. Managing an eSIM needs a Google component that GrapheneOS keeps off by default; it is turned on in Settings, Network and internet, eSIM support.
Carrier features work. VoLTE, Wi-Fi calling, SMS, MMS and 5G are supported; a feature that depends on a proprietary Google app can vary by carrier.
Android Auto installs from the GrapheneOS App Store.
Updates come often. The project shipped six releases in September 2026 alone.
Can a Pixel go back to Google’s Android?
Yes. Google publishes factory images “that allow you to restore your Nexus or Pixel device’s original factory firmware”, installed with Google’s web flashing tool. GrapheneOS adds one step: its verified-boot key is erased first, then the bootloader is locked again, and the phone is back in its factory state.
What we supply
We supply the Pixel 9 and Pixel 10 families with GrapheneOS already installed, configured and updated. Current models are on our GrapheneOS page. Which phones GrapheneOS supports with security updates, and until when, is in our article on supported devices.
Buy a Pixel with GrapheneOS: models
Sources
GrapheneOS documentation
- GrapheneOS features overview, read 27 September 2026. — grapheneos.org
- GrapheneOS FAQ, read 27 September 2026. — grapheneos.org
- GrapheneOS usage guide: sandboxed Google Play, camera, eSIM support, carrier functionality, updates, read 27 September 2026. — grapheneos.org
- GrapheneOS web installer: verified boot, and replacing GrapheneOS with the stock OS, read 27 September 2026. — grapheneos.org
- GrapheneOS release notes, the releases of 18 June 2026 (the first based on Android 17) and of September 2026. — grapheneos.org
- GrapheneOS attestation compatibility guide. — grapheneos.org
- Android Open Source Project, “AOSP overview”. — source.android.com
- Google Play services overview. — developers.google.com
- Pixel Update Bulletin, September 2026. — source.android.com
- Pixel Phone Help, “Learn when you’ll get software updates on Google Pixel phones”. — support.google.com
- Android Developers Blog, the Android 17 release, 16 June 2026. — android-developers.googleblog.com
- Google Wallet Help, “Fix problems with tap to pay transactions”. — support.google.com
- Factory images for Nexus and Pixel devices. — developers.google.com
