Android 17 QPR1 beta 3 contains a setting that would let users hide Gboard's globe icon, the keyboard switch key that sits in the bottom-right corner. The toggle removes the globe key entirely, even when multiple languages or other keyboard apps are active. That appeals to users who want a cleaner layout, but the same report found a meaningful catch: switching back from at least one third-party keyboard becomes significantly harder once the globe key is gone.
The feature is in testing, not shipping. Android Authority was explicit that finding something in a QPR1 beta build is not a release confirmation, and whether this reaches stable Android 17 remains unclear.
Why the Android 17 keyboard switch key could be harder to replace than it looks
The globe key's job is straightforward: give users a single, always-visible button to move between keyboards. When it's hidden, Gboard offers a fallback through a long-press on the space bar, which still brings up language and keyboard switching options within Gboard. That part works.
The problem is that the space-bar method doesn't work with every third-party keyboard app, Android Authority reported. SwiftKey is the tested example. Once a user switches into SwiftKey with the globe key disabled, there's no in-keyboard path back to Gboard. The only routes out are going into Android's language and input settings to re-enable the globe icon or removing SwiftKey from the active keyboard list entirely.
That's a meaningful friction point. The space-bar gesture is Gboard's solution to its own problem. It doesn't extend to keyboards that haven't implemented the same mechanism, and Android Authority notes the behavior may vary across other third-party apps beyond SwiftKey. For now, the behavior of other keyboards in this scenario isn't documented in the current reporting.
There's a second open question running alongside this one. Android Authority also reported that Google is reworking the keyboard switcher UI in Android 17 more broadly. It's not yet explained how that redesign relates to the globe-key hide option; it's possible a new switcher could eventually provide a cross-keyboard fallback, but that connection remains speculative at this stage.
What the setting does, and what's still unknown
When the toggle is enabled, Gboard stops showing the globe icon in the bottom-right corner. That's true even if the user has multiple languages configured inside Gboard or has other keyboard apps installed and activated. Keyboard and language switching inside Gboard stays available through the space-bar long-press.
What's confirmed: the toggle exists in Android 17 QPR1 beta 3 keyboard settings; the globe key disappears completely when disabled; the space-bar fallback still handles switching within Gboard.
What's not yet clear: the precise menu path, since reporting describes only "a new option in keyboard settings" without specifying the exact location; whether the setting sits at the OS level or inside the Gboard app itself; and whether the feature reaches stable Android 17. Hiding the globe icon is reportedly one of the most-requested changes Gboard users have asked for, which suggests demand exists, but demand hasn't historically guaranteed shipping on any particular timeline.
Who can safely disable the Gboard globe icon, and who should wait
Based on the reported behavior, the case for disabling the globe key is strongest for users who stay entirely within Gboard. If all typing happens in Gboard across one or more languages, the space-bar long-press appears to cover the switching need. Those users may welcome the cleaner bottom row, and hiding the key doesn't appear to create a functional trap for them.
Multilingual Gboard users sit in a similar position, though it's worth confirming the space-bar method works across a specific language configuration before committing to the change. The adjustment is more about muscle memory than a hard loss of access.
Users who rotate between Gboard and any third-party keyboard are in a different situation. The SwiftKey finding illustrates the specific risk: disable the globe key, switch into a third-party app, and the path back requires a trip into system settings. For users who switch keyboards regularly, that's a workflow interruption that makes the globe key worth keeping until Google either clarifies how the new keyboard switcher UI addresses this or ships the feature with a clearer solution in place.
The practical check is simple. Open Android's language and input settings and look at how many keyboard apps are active. One keyboard in regular use, and the globe key is mostly habit. Multiple keyboards in regular use, and removing the globe key introduces real inconvenience based on what's been reported so far.
Part of a longer push to let users trim Gboard's bottom row
The globe-key toggle isn't arriving in isolation. Google has added several bottom-row controls over the past several months, each chipping away at the default layout one key at a time.
Comma and period key toggles arrived in October 2025 and rolled out across both beta and stable channels for Gboard 16.0 and later. Turning both off strips the bottom row down to just the symbol key and the enter key.
An auto-switch-after-apostrophes feature followed, reaching stable users on Gboard 16.7 earlier this year, enabled by default with an opt-out available at Settings > Preferences > Shortcuts. That one handles a specific typing friction point: Gboard automatically returns to the letter keyboard after an apostrophe, rather than leaving the user stranded on the number and symbol view.
The globe-key option fits the same general direction. Google appears to be building out user control over what appears on the bottom row incrementally rather than shipping a wholesale layout overhaul. The comma and period toggles affected visual preference only. The auto-apostrophe setting adjusted a typing behavior.
The globe key is different in kind because it connects Gboard to the rest of the Android keyboard ecosystem. Removing it doesn't just change what users see; it changes how Android manages keyboard switching for that user.
That's what makes this toggle worth watching more carefully than the others. It's not a question of whether the bottom row looks cleaner. It's a question of whether Google provides a cross-keyboard fallback before or alongside shipping the feature. The keyboard switcher UI redesign that Android Authority flagged could be that solution, or it could be entirely separate. Right now, there's no reporting that connects the two.
What to watch before the stable release
Two questions matter most heading into stable Android 17. First, does Google ship the globe-key toggle at all, given that beta and teardown discoveries may not make the final release. Second, if it does ship, does the revamped keyboard switcher UI provide a path between third-party keyboards that doesn't depend on the globe key?
If both land together with a working cross-keyboard solution, the toggle becomes genuinely useful for a wider range of users. If the toggle ships without that fallback resolved, users with any third-party keyboards active have good reason to leave the globe key enabled and wait.
Comments
Be the first, drop a comment!