
If you ever want to switch back to a more stable channel, your updated profile data might not be compatible with the older version. What should I do before I change my channel? Back up your data!īefore you switch, you should make a backup of your profile (bookmarks, most visited pages, history, cookies, etc).
/cdn.vox-cdn.com/assets/1184567/high-res_chrome.png)
Text related to new features may not get translated into all languages until the feature is released in the Stable channel. Note: Early access releases (Canary builds and Dev and Beta channels) will be only partly translated into languages other than English. You can also look for a more specific recent build by going to the Chromium continuous build waterfall, looking at the number near the top under "LKGR", and then going to this Google Storage bucket and downloading the corresponding build.
#Update google chrome for mac os x code
There's no lag between major versions, whatever code we've got, you will get. The Dev channel gets updated once or twice weekly, and it shows what we're working on right now. Dev channel: If you want to see what's happening quickly, then you want the Dev channel.It's updated every week roughly, with major updates coming every six weeks, more than a month before the Stable channel will get them.


It's updated roughly every two-three weeks for minor releases, and every 6 weeks for major releases.
#Update google chrome for mac os x full
Stable channel: This channel has gotten the full testing and blessing of the Chrome test team, and is the best bet to avoid crashes and other issues.This allows you to play with our latest code, while still keeping a tested version of Chrome around. You can run all channels alongside all others, as they do not share profiles with one another. The release channels for chrome range from the most stable and tested (Stable channel) to completely untested and likely least stable (Canary channel).
