Chrome for Android Dedicated Back Button: Menu Redesign Explained

Google is adding a dedicated back button to the Chrome for Android three-dot menu with the rollout of Chrome version 150, bringing the Android browser in line with what Chrome on iPhone has offered for some time. The Chrome for Android dedicated back button sits alongside the existing forward arrow in the menu's top row, but it arrives as part of a broader reorganization that touches more controls than the headline feature suggests. The complication: testing by PiunikaWeb this week found the redesigned menu on a device running Chrome 149 while a separate phone on the newer Chrome 150 still showed the old layout, which suggests the changes are being pushed from Google's servers rather than delivered through a standard app update.

Chrome 150 became widely available via the Play Store this week, 9to5Google reported. But version number and menu state appear to be independent of each other, at least for now.

What changed in Chrome's Android three-dot menu

The back button is the most visible addition, but the overflow menu has been restructured in several ways at once.

Previously, the top row of the three-dot menu showed only the forward arrow, a control that stays grayed out until the user has already navigated back by some other means. The redesign adds a back button beside it, so both navigation controls now sit together in that row. 9to5Google and Android Authority both confirmed the update matches the layout Chrome on iOS has carried for some time.

Clearing space for that second button required removing something. The page info icon is gone from the top row. In its place, a new "Site controls" entry has been added further down the scrollable menu, according to Android Authority and PiunikaWeb. Neither outlet, nor Google, has explained what changed underneath the label. Whether the per-site settings previously accessible through the page info icon, such as permissions, security status, and cookie controls, have been reorganized or simply relabeled is not established in available reporting. That distinction matters for how consequential this particular change actually is.

Lower in the menu, the "Add to Home screen" option has been renamed "Install and create shortcut" and moved to a different position, per PiunikaWeb and 9to5Google. The bookmark and download buttons have each shifted one spot to the right, per PiunikaWeb.

One detail that gives the restructuring some context: 9to5Google noted that "Show Reading mode" was the most recent addition to the overflow list before this update, added in February. The three-dot menu has been accumulating options steadily. Moving site management tools deeper and clearing the top row addresses real accumulation, not just aesthetic preference.

Which changes will cause friction

The back button is a convenience addition, not a replacement for something that was missing. Android users already navigate backward through the system back gesture or the navigation button, and neither of those is going away. PiunikaWeb noted the in-menu button is most relevant for users who rely on it as an alternative to the system gesture. For everyone else, it's an option that exists but won't change anything about how Chrome gets used day to day.

The bookmark and download icon shifts are a different matter. Controls tapped from muscle memory are precisely the ones that generate irritation when they move, even slightly. A one-position shift to the right is small in isolation; repeated across dozens of daily interactions, it produces the low-grade friction that generates complaints. PiunikaWeb flagged this specifically, noting that anyone used to tapping those buttons without looking will need time to adjust. The adjustment period is short, but it's the most likely near-term source of user pushback on a redesign that is otherwise minor.

"Site controls" sits in a different category. If Google has simply relabeled the old page info panel, the practical consequence is that the same settings now require an extra scroll and a different label to find. That's a mild inconvenience. If the underlying permission management has been reorganized or expanded, it has real implications for anyone who regularly audits site behavior, checks certificate details, or adjusts per-site permissions. Available reporting does not resolve this, and Google has not characterized the change publicly. For now, it reads as a rename, but that assumption has not been confirmed.

Why the Chrome for Android dedicated back button may not appear after updating

PiunikaWeb's device testing produced a result that runs against normal update logic. A phone running Chrome 149.0.7827.200 displayed the redesigned menu. A separate phone running Chrome 150.0.7871.63, a newer build, still showed the old layout. The newer version was less likely to have the update, not more. PiunikaWeb noted this pattern is consistent with Google pushing features from its servers rather than tying them to a specific app release.

The individual changes also appear to be toggling independently of each other. The Chrome 149 device had the back button but still used the old "Add to Home screen" label. The Chrome 150 device had the renamed "Install and create shortcut" label but no back button. Two phones running different versions of the same browser, each carrying a different partial state of the same redesign, per PiunikaWeb. That pattern suggests Google is enabling each change separately at the server level rather than shipping them as a coherent bundle tied to a single release.

Android Authority reported it could not find the back button or "Site controls" on most of its test devices running the current Play Store version of Chrome, though the renamed install option appeared on at least one device. The result is consistent with a staged deployment that is reaching different accounts and device configurations at different rates.

App version, in this case, is a floor rather than a trigger. Chrome 150 rolling out via the Play Store this week establishes which builds can receive the changes, but whether a given device actually sees them depends on Google's server-side configuration. Two phones running the same Chrome build may display entirely different menus, and there is no user-facing step that forces the change through. Updating is worth doing; seeing the new menu afterward is not guaranteed.

What remains unresolved

The back button is the named feature, but "Site controls" is the change that deserves a second look once the rollout reaches enough devices for direct comparison. If it's a straight relabeling of the old page info panel, the story is that a familiar control got renamed and moved deeper in the menu. If Google restructured what's accessible there, it becomes the more consequential part of this update, and one that received no public explanation beyond a quiet label change in an overflow menu.

That question won't have a clean answer until the redesign is broadly available. For most users, the more immediate reality is a bookmark button that has moved one slot to the right and a new navigation option that will rarely come up. The menu looks different. How differently it actually functions depends on a detail Google has not yet explained.