Google just ruined my favorite Pixel feature and I’m furious

Google Pixel phones, for better or worse, are defined by their software. Exclusive features, quarterly Pixel Drops, and seven years of Android OS updates separate Pixels from the competition. Google’s controversial use of custom Tensor chips is supposed to help some of those exclusive AI features run on the device.

And yet a characteristic in me Pixel 10 Pro It suddenly went from using on-device processing to using the cloud without warning.

Pixel Screenshots is exclusive to the Pixel 9 and Pixel 10 series, excluding the budget A-series models. It’s one of Google’s most polarizing Pixel-only apps, with some considering it redundant when Google Photos already leaks screenshots. As someone who takes a lot of screenshots and never goes back to them, I found the app useful at times. It’s great for filtering screenshot categories, pulling links, and setting reminders to revisit specific screenshots.

I didn’t have any problems with pixel screenshots going haywire with anything I captured. Even when I captured sensitive or confidential information, that wasn’t a problem, because the app data never left my device. The Gemini Nano model on the device that powered Pixel Screenshots was a key advantage, and even Google recognized it.

In a fragment of a Google Store Magazine Entry About Pixel Screenshots, following the launch of the still-live Pixel 9, Google announced the on-device rendering aspect of the new app:

This Pixel-exclusive app uses Gemini Nano with Multimodality, our latest on-device AI model, to easily save, organize and retrieve the information embedded in your screenshots… Oh, and it does all of this super fast since Pixel Screenshots runs on the device, with no internet connection required.

Google was right. While cloud processing is better for intensive and complex tasks, on-device processing is faster and more private for less demanding workflows. The privacy aspect is crucial, as your screenshots may contain personal information that you don’t want leaving your Pixel phone and traveling to a Google server. Imagine my surprise to learn that the Pixel Screenshots app no ​​longer uses on-device rendering exclusively after the v1.26.134.11 update.

I didn’t find out about the change through a push notification or pop-up in the pixel screenshots; I read it in a Android Authority article. This is concerning because there is an expectation that if an app that uses artificial intelligence is marketed on the device, it will remain that way. As far as I can tell, aside from the subtle changes to the Pixel Screenshots app settings page, Google did not adequately communicate this change to users like me. It just flipped a switch in the background.

Even the Official Play Store Release Notes for pixel screenshots skip the change. A simple message explaining the change could have helped me make an informed decision about whether to use Pixel Screenshots now that it’s using “a secure, isolated environment on your device or in the cloud.”

There’s no doubt that offloading Pixel Screenshots processing to the cloud could enable more advanced features and preserve system resources. But as a Pixel 9 and Pixel 10 tester who has used Pixel Screenshots for almost two years, I’m surprised what problem this change solves. Ask Photos on Google Photos already uses cloud-based AI to answer questions about my screenshots.

Pixel Screenshots did a good job of organizing and reviewing my screenshots using the Tensor G4 and Tensor G5 chips and the Gemini Nano models in the device. Now that cloud processing is here, I have to consider privacy and security more than before.

This isn’t the first time Google has switched a Pixel feature from on-device processing to cloud processing. It made a similar change to Magic Cue on the Pixel 10 last December, and the feature now uses Google Private AI Compute in an attempt to balance performance and privacy. While not explicitly confirmed, Private AI Compute is likely to be the “secure and isolated environment” that Pixel Screenshots now uses. The idea is that encryption protects your data in transit and not even Google can see it.

I’m not a security researcher, so I can’t say whether you should trust Private AI Compute or not. Instead, I will phrase it much more simply. When the Pixel Screenshot app processed all your data on your phone, you can be sure that it will not leave your device. After the latest update, you are blindly trusting the security of a cloud processing system that you may not fully understand.

This change did not have to be controversial. If Google had added a separate switch to Pixel Screenshots, giving users the option between on-device and cloud rendering, this update wouldn’t have been an issue. We know it’s possible because Pixel Screenshots can still manually process inputs on the device when the phone is offline. The same would be true if you added a popup to Pixel Screenshots that conveyed the change and provided an opt-out button.

Instead, Pixel Screenshots users should navigate to the app’s settings page and turn on the switch next to “Search your screenshots with AI” to avoid sending screenshot data to the cloud. A new button appears that can “Delete all AI summaries and metadata.” So, that’s exactly what I did.

It’s fair to say that Google has a Pixel memory and performance problem. Pixel 9a and Pixel 10a didn’t get Pixel screenshots in the first place, presumably due to its mere 8GB of RAM. Pixel Screenshots join Magic Cue as a feature that once relied exclusively on the Gemini Nano’s local intelligence, but now relies on the cloud for some tasks. In a perfect world, Pixel users would at least have the option to keep these features local.

There is pressure for Google to expand Pixel Screenshots to more devices. It’s hard to argue with the hardware limitations that accounted for Pixel Screenshots’ exclusivity when it used on-device processing. But if you’re using the cloud now, the flagship Pixel 9 and Pixel 10 shouldn’t be the only phones to get Pixel screenshots.

Bring the Pixel Screenshots app to older, weaker Pixel phones and I’ll understand the reason behind the change. Don’t hold your breath, because Magic Cue started using Private AI Compute six months ago and remains exclusive to the Pixel 10 series.

Ideally, I want as many AI functions running locally on my phone as possible. It’s a shame Pixel phones don’t get more features that take advantage of on-device processing – they’re becoming more reliant on the cloud.