Using Chrome on roaming user profiles

As an administrator, you can let users in your organization use roaming user profiles. When users sign into Windows® on a computer on your organization’s network, information from their roaming user profile is copied from the network to their local computer. When they start Chrome, their roaming user profile is used to update the local Chrome profile. This means that users don’t need to separately maintain a local profile on each computer they use on your organization’s network.

The roaming user profile contains information such as bookmarks, autofill data, passwords, per-computer browsing history, browser preferences, and installed extensions. It doesn’t contain information about cookies, browsing sessions, cached or downloaded files, and other local browser instance and transient data.

Turn on roaming user profiles

To turn on the roaming profile option in Chrome, you can:

Check roaming user profile status

To view the roaming profile status on a specific Windows computer, enter chrome://sync-internals in the browser window. On the About page, under Local state, you can see if local sync is enabled. If so, the local file path is listed.

Change roaming profile file location

By default, information for each roaming user profile is maintained in a file called profile.pb. This file is located in %APPDATA%/Google/Chrome. If you delete or corrupt the file, no local Chrome profile data is lost. However, data that has not yet synced with it isn’t available on other computers in the network.

To set a different location for profile.pb:

Known issues

  • If one of your users starts Chrome simultaneously on multiple Windows computers on your organization’s network, they won’t sync to each other. Instead, the profile file is overwritten each time the user’s local profile changes on one of the computers.
  • If your users have big profiles with tens of thousands of bookmarks, autofill data, or extensions, Chrome might consume more memory and run slower.
  • Each Chrome profile is mapped to a roaming profile in the same order they’re created on each computer. So, if two different profiles, such as work and private, are created in a different order on different computers, roaming user profiles might not work properly. We recommend that your users use a single profile. We’re planning to support multiple profiles in the future.
Was this article helpful?
How can we improve it?