October reports said Chrome on Googlebook lacked profiles

Reports published October 6, 2026, said Chrome on Googlebook OS lacked multiple browser profiles. Google community manager Mishaal Rahman said the browser did not support them, and reviewers reported the same limitation on an ASUS Googlebook 14.

A Chrome profile is a separate browser space. It is distinct from adding another Google Account in an app or switching to another user on the device. That difference matters when you want separate browser setups for different tasks.

NeoTeo previously covered Googlebook’s launch features in an earlier article; this article focuses on Chrome profiles.

Chrome on Googlebook OS and browser profiles

Rahman said Chrome on Googlebook OS did not support multiple profiles. That means the standard browser did not offer a way to switch between separate Chrome profiles in the reports published October 6.

What reviewers observed on an ASUS Googlebook 14

Reviewers reported that tapping Chrome’s profile image on an ASUS Googlebook 14 opened account settings rather than a profile selector. Chrome’s three-dot menu also had no profile-switching option. Those interface observations were specific to that device; Rahman’s statement addressed Chrome on Googlebook OS.

Browser profiles, app accounts and device users

Rahman distinguished the browser limitation from using multiple Google Accounts within apps: Googlebook OS users could switch accounts in apps. He also said the operating system supported separate device users, each with their own apps, files and Google Accounts, selectable from the login screen.

Those options serve different purposes. Switching an account inside an app does not create a second Chrome profile, and a separate device user is an operating-system account rather than a profile inside Chrome.

The reported Chrome Beta or Canary workaround

Reviewers reported testing Chrome Beta or Chrome Canary as separate browser releases alongside standard Chrome, signing into a different account in the alternate release. That was a reported workaround, not multiple-profile support in standard Chrome.