Chrome updates happen in the background automatically — keeping you running smoothly and securely with the latest features.
How to check your version of Chrome
- On your computer, open Chrome
- At the top right, look at More
- Click Help > About Chrome
Here’s how you can update Chrome
Chrome checks for new updates regularly, and when an update is available, Chrome applies it automatically when you close and reopen the browser.
Applying a pending update
If you haven’t closed your browser in a while, you might see a pending update.
If an update is pending, the icon will be colored:
The pending update was released less than 2 days ago.
The pending update was released about 4 days ago.
The pending update was released at least a week ago.
To apply the update, simply close and reopen Chrome.
Why keep Chrome updated
Keeping Chrome up to date allows you to take advantage of the latest Chrome features and security updates to keep you productive, secure, and mobile.
Keeps you secure
Chrome makes staying safe easy by updating automatically. This ensures you have the latest security features and fixes as soon as they’re available.
The latest Google features
Chrome is constantly updating to bring new Google tools into the browser like one-click translation, tab groups, and password checkup.
Improved speed and performance
Chrome is designed for speed and efficiency — making your browsing experience fast and reliable, so you can get stuff done.
Help when you need it
Need more assistance with Chrome? Explore our help center to learn more about updates and other ways to use Chrome.
- Help Help
- Change language or region
For Windows 10/8.1/8/7 32-bit.
For Windows 10/8.1/8/7 64-bit.
This computer will no longer receive Google Chrome updates because Windows XP and Windows Vista are no longer supported.
Please select your download package:
Not Debian/Ubuntu or Fedora/openSUSE? There may be a community-supported version for your distribution here.
Select the version of Chrome that’s right for your Mac
- At the top left, open the Apple menu.
- Select About This Mac.
- In the “Overview” tab, look for “Processor” or “Chip”.
- Check if it says “Intel” or “Apple”.
Note: Installing Google Chrome will add the Google repository so your system will automatically keep Google Chrome up to date. If you don’t want Google’s repository, do “sudo touch /etc/default/google-chrome” before installing the package.
Download for phone or tablet
Download for another desktop OS
The device you have runs on Chrome OS, which already has Chrome browser built-in. No need to manually install or update it — with automatic updates, you’ll always get the latest version. Learn more about automatic updates.
Easily give your Chromebook a fresh, clean start in under a minute.
Resetting a Chromebook is a snap.
One of my favorite Chromebook features is how fast and easy it is to perform a factory reset. That might seem odd, but it’s a simple way to keep it running smoothly. Google calls the feature Powerwash and it can be done in under a minute. It’s also one of the features that make Chromebooks so good for sharing. Just Powerwash your Chromebook and someone else can use it and you won’t need to worry about them accessing your info.
Also, although Chromebooks are inherently secure, that doesn’t mean you can’t install a malfunctioning extension or a web app that misbehaves. Uninstalling the offending extension or app can typically fix the problem, but if that doesn’t work, a reset should do the trick. The same goes for other wonky behavior you may experience.
A Powerwash is a breeze to do, too. I’ve detailed the steps below. Also, while I included how to locate most settings by navigating menus, it is generally easier to use the built-in Launcher search feature to find exactly what you’re looking for fast. The Launcher can be opened by clicking the radial button at the far left on the shelf at the bottom of your screen; a two-finger swipe up from the shelf; or hitting the Search key.
Back up your files first
Since you’ll be wiping your Chromebook’s internal storage, you’ll want to back up any files you want to keep to the cloud or an external drive. This isn’t as painful as you might think because a lot of what you do on a Chromebook is already synced to your Google account — from apps and extensions to passwords and Wi-Fi networks. (To see what’s set up to sync, go to the Accounts section of the Settings menu. Click on Sync and Google services and select Manage what you sync.)
Back up files from your Files folder before you Powerwash your Chromebook.
What doesn’t automatically get synced are files saved locally to the Downloads folder. Linux and Play files are also stored locally. To see and back up those and any other files, open the Files app (or search for Files with the Launcher). The left-side navigation panel in Files shows you all your folders.
You’ll also see your Google Drive folder (that’s what I use for backups) as well as external storage. If your Chromebook has a microSD card slot, for example, you can save files to a card or attach an external drive. You can copy and paste files to Google Drive or external storage or just drag and drop them. The Powerwash only deletes what’s on your Chromebook’s built-in storage.
Give it a good scrub
A couple of clicks from a clean Chromebook.
Once your files are all backed up, you can start the Powerwash. Go to the Settings menu by clicking on the time on the far right side of the shelf at the bottom of your screen. That will pop up the quick settings panel. Click on the cog icon at the top of the panel.
Under the Advanced section at the bottom of the menu (you may need to click on Advanced to expand the options) you’ll find Reset settings and Powerwash. Click the Reset button and you’re on your way. You can also search for Powerwash with the Launcher or Search key to access it. And, if you aren’t or can’t sign in and want to Powerwash a Chromebook, press and hold Ctrl plus Alt plus Shift plus r to begin the reset.
There are a couple of warnings you’ll need to click through to confirm that you know what you’re about to do. After that, the Powerwash begins. And it is fast, too, generally taking less than a minute to complete. Also, if Chrome OS isn’t up to date or there’s a firmware update available for your Chromebook, it will ask if you want to install the updates.
Sign in and start working
When the Powerwash cycle completes, the Chromebook will restart and you’ll be greeted with the Welcome screen. Just follow the prompts to sign in to your Google account and you’re done. Anything you have set to sync will do so. That includes installing web and Android apps and browser extensions and any updates. Otherwise, the internal drive should be clean and your Chromebook running like new.
Today’s Best Tech Deals
Picked by PCWorld’s Editors
Top Deals On Great Products
Picked by Techconnect’s Editors
Network issues are bad, but they’re worse with a Chromebook. Chromebooks thrive on an active Internet connection, even though apps are being developed for offline use. When that connection is severed, the Chromebook can be like a fish out of water.
While there are ways to get work done while offline on a Chromebook, chances are you’ll need your connection back as fast as possible. With a few simple steps, you can get your Chromebook back online where it belongs.
Where the wireless settings are
There are two places where you can make changes to your wireless settings on a Chromebook. The most convenient route is through the status area in the bottom right-hand corner of your Chromebook’s shelf.
The Chromebook’s wireless options can be reached via the status bar at the bottom right of the shelf on the home screen.
Click anywhere in the status area to expand it: Among other basic settings, it’ll show your current connection in the Network bar near the top. If you’re connected to a network, it should say, “Connected to [Network Name].”
When you scan for networks, a list of Wi-Fi networks will appear in the status area popup.
If it says “No Network,” click the box to open up a list of available Wi-Fi Networks. You can click Join other. or Settings at the bottom to enter a network manually.
Click the Settings bar at the bottom of the expanded status area to launch into the full Settings page within the Chrome browser, which delves deeper into your Chromebook’s settings. In the Internet Connection section at the top, you can allow proxies for shared networks and edit your saved wireless connections.
The wireless settings in Chrome are a bit more advanced than the simple controls in the status bar.
Make sure your Chromebook is connected to Wi-Fi
If the password for the network you’re trying to connect to has changed, you’ll need to re-configure the connection to update the password. From the list of available networks in the Settings tab in Chrome, click the network name you want to connect to.
Check that your WPA password is indeed correct by clicking on Configure.
Click the Configure button at the bottom of the pop-up window to enter the new password and click Connect.
In the dialog that pops up, enter the WPA password for your WI-Fi network.
Run Google’s diagnostic tool
If you’re actually connected to a network but are having issues with your connection, you’ll want to run Google’s Chrome Connectivity Diagnostics App built specifically for Chromebooks.
Google’s Diagnostic Tool will help you identify connection problems and reccommend action if there is anything you can do.
The app runs a detailed diagnostic that gives you in-depth information on what could be causing you trouble. It makes sure Chrome is up-to-date, checks for a DNS server, and it also checks whether internet traffic is being blocked by a captive portal.
The Diagnostic Tool will test each part of your connection to find what’s slowing you down or keeping you from working.
Reboot all the things!
If you’ve tried everything listed above, your laptop likely isn’t the problem. When in doubt, follow the age-old advice of turning everything off and on again.
Turn your Chromebook off, turn the modem off, and turn off the router if you have a separate one. Wait a good minute or two, then begin rebooting your devices. Start with the modem, followed by the router and then, finally, your Chromebook. If that doesn’t fix your problem, move on to the next step.
Check other computers
The next step is to figure out whether it’s your Chromebook or the wireless network itself causing problems. Try to connect another device to the wireless network. If that device can use the web when connected to Wi-Fi, the problem is with your Chromebook. If not, the router may be at fault.
Test the wired network
If none of your other devices can connect to the Internet through Wi-Fi, there may be some other problem with your router. To test this, you’ll have to try connecting your Chromebook—or another computer—to the router the old-fashioned way: with an ethernet cable.
Unfortunately, most Chromebooks don’t have an ethernet port. If you’ve made the commitment to use a Chromebook as your regular machine, you should probably invest in a $13 USB-to-ethernet adapter.
If you can connect to the Web through the ethernet cable, you’ve discovered that it’s definitely the wireless network causing you grief. If not, the router, modem, or your ISP are the likely culprits.
A recent update to a network policy on managed Chrome devices has resulted in some unforeseen connectivity issues for thousands of users in schools and businesses alike. Devices that are configured to connect automatically to organizational, password-protected wifi were affected.
Devices affected would have been online December 5th between 9:50 a.m. and 11:50 a.m. PST and are managed by an organization. Only devices whose wifi is managed via the Admin Console would have experienced the outage.
The fix for the bug has been pushed from Google but refreshing the network policy is required to alleviate the problem. Since the broken policy prevents that connecting to a network, a workaround must be implemented.
Google support has published an article to help organizations in getting up and running again as quickly as possible. Long story short, devices will need to connect to a different network in order to update the guilty policy.
Here’s a rundown of how to fix the problem.
Create a new, open network.
- Create a new temporary WiFi SSID to something easy to read (for example, “Fix WiFi”) and security type to be open (no password). If this is not possible, consider temporarily changing your organization’s WiFi network SSID in this way.
- Instruct users to join WiFi before signing in.
- After the devices have connected, change your organization’s WiFI network SSID and security type back to the previous configuration.
*note – creating an open network will temporarily open your organization to unauthorized device connections. If you choose this method, make sure you have all the devices prepped and ready to connect at the same time to minimize the amount of time the network is unsecured.
Manually connect to an existing open network.
- If an open network is already available, instruct users to connect from the lock screen or guest mode to update policies.
- Once updated, reconnect devices to secured network
Manually re-enter WPA-PSK passphrase.
- If an open network is not an option, users can manually re-enter the network passphrase.
- Once entered, the policies should update automatically.
*This method will be the most time-consuming but will also be the most secure for organizations not wishing to have an open network available.
Use a mobile hotspot.
- You can update devices on a group by group basis by creating a hotspot with a mobile device and allowing a number of machines to connect and update policies.
- For security purposes, your mobile hotspot should allow you to limit the number of devices that can connect to it.
*Keep in mind, this will use your mobile data. If you do not have an unlimited plan, charges could be incurred.
Use an Ethernet connection with USB adapter.
- Connect an ethernet cable to your network using a USB ethernet adapter.
- Connect USB ethernet adapter to each Chrome device to connect.
This method will also be very time-consuming and will be best for organizations with a limited number of devices. If your organization is experiencing this issue, you can find more information on diagnosing the problem at Google’s support page here.
- Click to share on Twitter (Opens in new window)
- Click to share on Facebook (Opens in new window)
- Click to share on Reddit (Opens in new window)
- Click to share on WhatsApp (Opens in new window)
About Gabriel Brangers
Lover of all things coffee. Foodie for life. Passionate drummer, hobby guitar player, Web designer and proud Army Veteran. I have come to drink coffee and tell the world of all things Chrome. “Whatever you do, Carpe the heck out of that Diem” – Roman poet, Horace. Slightly paraphrased.
Google pushed out a small Chrome OS update at the tail end of June, and now Chromebook users are seeing performance issues as a result. One of the chief issues is absurdly high CPU usage that can slow your Chromebook to a crawl.
Chrome OS version 91.0.4472.147 dropped last week, bringing with it the usual cadre of bug fixes and security updates for the bigger Chrome OS update pushed through at the beginning of June.
As the update hit, users started to file bug reports and post publicly about experiencing slowed down Chromebooks and severe lag. In the official bug report, users submitted screenshots of the Diagnostics app, showing the CPU locked up at high usage rates and topping out at the maximum rate. If the operating system is throttling the processor all that much, it makes it virtually useless when trying to navigate anywhere else in Chrome OS.
But the bug doesn’t seem to affect all Chromebooks. The reports come primarily from Grunt and Hatch devices, both internal code names used to refer to specific boards within certain models of Chromebooks. This makes it easy to isolate which of the available models might be affected by the bug. AboutChromebooks has a handy list of all the possible models in no particular order:
HP Chromebook 14
Acer Chromebook 315
HP Chromebook 11a G6 EE
Lenovo 14e Chromebook
Acer Chromebook 311
Acer Chromebook Spin 311
Lenovo 100e 2nd-gen AMD
Lenovo 300e 2nd-gen AMD
Acer Chromebook 712
Lenovo Ideapad Flex 5
Samsung Galaxy Chromebook and Chromebook 2
Asus Chromebook Flip C435
If you’re curious, you can check which board your Chromebook uses by cross-referencing this list of devices or by typing chrome://version into your Chromebook’s address bar. Look three lines down, next to Platform. The name of your board is at the end.
Not all the devices listed above suffer from the issue that’s apparently plaguing the version 91.0.4472.147 update. But unless you can afford to spend your free time filing bug reports, you might want to ignore the notifications to update your software, at least for a few more days. Also avoid shutting down your Chromebook so as not to trigger automatic updates. If you want to know when the coast is clear, you can bookmark the official bug report, which is effectively a large thread on the goings-on of this particular version.
- Latest news
- Android 11
- Android 10
- Android OS
- Chrome OS
- Android TV
- Android Auto
- App Reviews
- Game Reviews
- All reviews
- Phone Reviews
- Tablet Reviews
- Wearable Reviews
- Other Reviews
Google really wants you to use virtual desktops on your Chromebook
Most of us probably feel overwhelmed by the endless slew of browser tabs and and all the software windows cluttering up our PCs. Thanks to virtual desktops for Chromebooks, managing your tasks is way easier: you can create a workspace for each of your classes, or have a dedicated desk for gaming. Your organization possibilities are virtually endless — yet very few users take full advantage of this feature. It seems Google really wants you to realize how useful it is, as it’s experimenting with putting virtual desks front-and-center to the Chrome OS experience.
We’ve spotted ongoing work over at the Chromium Gerrit that displays your virtual desks persistently, internally called “bento bar.” The bar will show up at the top of your Chromebook’s screen when there are multiple desks. While its flag isn’t in the latest Chrome OS Canary build yet, we got it working on our Chromebook with some degree of effort.
A work-in-progress feature puts your virtual desks front and center.
Upon signing into your user account, you’ll see a thin bar that occupies a small portion at the top of your Chromebook’s screen. The strip fills up depending on how many desks you have — clicking on a label will zip your screen to that virtual desk. There are two buttons on the right side of the bar: an overflow menu that offers to hide or show the strip, and a shortcut that launches an expo of your active windows.
The new bento bar experiment is a big deal for multitaskers and students like myself who often use virtual desktops regularly. Instead of swiping over and over on my Chromebook’s trackpad or hitting the overview key first, the bento bar keeps all of my desks a click away. I care about getting tasks done efficiently, and this feature is a step towards that.
Bento bar is far from perfect — a reminder that the experiment is still in its infancy. There are bugs that prevent me from fully taking advantage of it, like covering a maximized application’s title bar and its awkward placement when the taskbar is aligned to the left or right side of the screen. I’d also prefer an option to auto-reveal the bar when moving the mouse against the top of the screen.
The bugs I’ve described will probably get ironed out when Google officially launches bento bar to Chromebooks some time from now. With features like custom desk names, handfuls of useful keyboard shortcuts, and smoother transitions, it’s clear that Google is getting serious about taking your productivity on Chromebooks at a whole new level. Fingers crossed we’ll eventually be able to set different wallpapers for virtual desks, too.
Dec 1, 2018 · 5 min read
This article is about simply previewing your static or dynamic web pages, running on your computer, on an actual mobile phone as opposed to using your browser’s debugging tool to see how it will look on a phone.
The obvious reason is to test for responsiveness, but this is already possible, and quite convenient in modern browsers, the most popular amongst developers being Chrome. While this is completely fine in most cases, there are several cases where it just doesn’t suffice. I’ll outline those scenarios below
- Using the Chrome developer tools mean that whatever you see is how the Chrome browser engine (Blink) renders the page, which is most likely going to be a bit different from other browser engines like Webkit. I’ve deployed web pages only to later discover that the layout is completely broken on iOS devices.
- This is similar to the first reason. A lot of your users will not always use Chrome or Safari. There’s a whole lot of mobile browsers like Opera mini, Brave, and the very popular UC Browser. Believe it or not, they sometimes behave differently.
- Some browsers have mobile data saving turned on by default on mobile, which can affect the layout of your website a great deal. Some of my users once complained they couldn’t find the submit button on a form, despite using Semantic-UI (a Bootstrap alternative) which is supposed to have a uniform layout across all browsers and devices. Turns out Opera Mini has a max data savings mode that resulted in the weird behavior.
Chrome’s remot e debugging doesn’t solve the problems highlighted above, it was designed to “ inspect and debug live content on your Android device from your development machine”, which is not what this post is about.
In summary, both devices (PC and mobile phone) need to be connected to the same network, in which case you can then access your PC’s localhost address by entering the IP address assigned to the PC on the mobile phone browser’s address bar. This can be achieved by connecting both devices to a WiFi router or by connecting the PC to the mobile phone hotspot. I’ll outline the steps for the two methods. Make sure your development server is running on your PC and take note of the port number
Using a Router
As we know, when devices are connected to the same network, they are all assigned a unique IP that identifies them on that network. On most networks, this happens dynamically, which means that the IP is assigned when the device connects. You don’t need to know how this happens, just know that the IP might not be the same when you reconnect subsequently.
Most Routers (I’ve never seen one without this feature) have a web portal where you can do things like set the SSID, Password and other network settings. The portal is usually accessible via an IP address, which is constant for that router (you can check the label of google the router model to get the IP address for the web portal). In my case, the IP is 192.168.8.1 . Visiting that address opens up the home page which shows an overview of the current session. Yours will most likely be very different from this
You can see that three devices are connected, but this doesn’t show any details about those devices, so you may have to dig deeper to get them. In my case, I only have to click on the statistics tab. The page will most likely prompt for user credentials. If you’ve never changed this, you can find it on the device label (sometimes under the battery).
Here, I have 4 connected devices with their names and assigned IP addresses. The only one of concern is your development machine. Mine has an IP of 192.168.8.103. Now all you have to do is go to that IP address on your mobile device like this 192.168.8.103:8080 (mind the port number). That’s it!
Connecting Via Mobile Hotspot (Android)
This method is a bit more straightforward but I’ve never had to use it because I’m always connected to a Router. It is important to note that you don’t need to have an active data subscription for this to work (including the router method), you don’t even need to turn on your mobile data connection.
Just like the previous method, the process might not be exactly the same for you. I am going to use a Samsung Galaxy S8+ running Android 8.0 Oreo for this example.
- Turn on mobile hotspot in your phone settings menu
- Search for the network on your PC and connect to it
- Check the list of connected devices on your phone and click on your PC name. This will reveal the assigned IP address
- Open a browser on your phone and visit that IP address with the port number your development server is listening on. And we’re done!
Chrome OS is getting a super-Googley new superpower — and if we’re lucky, Android might soon follow suit.
- 6 noteworthy new Chrome OS features to.
- A clever way to bring widgets into.
- 2 colossal Chrome OS changes to keep an.
- The hidden significance of a simple.
- 5 new Chrome OS features you should.
- Google just quietly set the stage for a.
- Hands on: What it’s actually like to.
- 6 useful Chrome OS features you.
- 22 worthwhile ways to use Google.
- The Chromebook’s new secret weapon
Google’s Chrome OS platform is a lot of different things. It’s a simple place for web-centric computing. It’s a natural extension of Android and the future of the “Android tablet.” It’s a place to run Linux apps — and soon, if you’re in the right enterprise environment, a place to run Windows apps, too (!).
Chrome OS has truly become the “everything OS” — a colossal shift from its initial position as the “nothing OS” when it first showed up on our doorsteps many moons ago. But aside from appealing to people with all of those aforementioned qualities, the humble Chromebook is slowly but surely gaining a new purpose and unique advantage over its competitors.
It’s something that’s been shaping up subtly for a while but that Google is now openly promoting and pushing forward, and it’s an asset so obvious-seeming, it’s almost shocking that it hasn’t been tapped into ’til now. It’s the Chromebook’s role as the ultimate Google machine — a single device where Google’s services and search prowess come together in a singularly streamlined way. And if you think it’s no big deal, well, you’re missing the bigger picture.
It was more of a passing side note than any bold declaration, but Google actually laid out its vision for this new Chrome OS superpower in a blog post this week. The post was about new features coming into the Chrome OS environment as part of September’s hefty operating system update. A smarter cross-device Wi-Fi password syncing system, a simplified system settings interface, and a more accessible mic-level slider were the headlining items. But casually dropped in the middle of the post was a quietly important paragraph:
Soon, you’ll also be able to search through settings from the Launcher. This is a big step in helping the Launcher work like an “everything button” — our vision is to create one place for you to access Google Search, your Drive, settings, apps, local files, and more. So you can hit one button, type what you’re looking for, and then your Chromebook will intelligently figure out what to find for you.
And there you have it: the “everything button” — the logical next step for what’s evolved into the “everything OS.”
It’s easy to brush that away as a modest expansion, but having that all-in-one, “everything button” function really can impact your day-to-day work and ability to get stuff done. To some degree, that Chrome OS Launcher button has acted as a bit of an “everything button” for a while now, but the “everything” part of it has had a handful of missing elements — and Google hasn’t done an especially great job of publicizing its multipurpose nature and making sure we mortal Chromebook owners appreciate its potential.
But with its new powers coming into play, that button — represented by a magnifying glass icon on most Chromebooks and (somewhat confusingly, with random-seeming inconsistency) a circle on Google’s own Pixelbook line of devices — could almost be described as a “Google button.” Tap it, and in the one box that comes up, you can:
- Search the web.
- Search your local computer storage.
- Search your Drive file storage.
- Search for documents, spreadsheets, and presentations in your web-based Docs, Sheets, and Slides collections.
- Search for a system-level setting that you want to modify.
- Search for an app to run on your own device — no matter what type of app it is — or search for a new app to install from the Google Play Store.
- Perform any imaginable action via the Google Assistant.
That last part is huge, especially for anyone who also uses Assistant on Android or on a Smart Display. And Assistant on Chrome OS can do some impressively helpful stuff — everything from creating new documents to controlling your calendar and interacting with your cross-device reminders.
There’s just one catch: On most current Chromebooks, the Assistant remains frustratingly detached from the main Launcher experience. It’s connected but also separate from the rest of the Launcher setup: If you want to interact with Assistant, you have to either click or tap an Assistant icon within the initial Launcher search box or press the Launcher key and “A” key together to pull it up.
On Google’s own Pixelbook line of devices, though, Assistant is integrated into the Launcher seamlessly — and my goodness, what a difference that makes. You just start typing into the single Launcher search box, and whatever’s most appropriate comes up automatically as the top suggestion — whether that’s an app:
. a system setting:
. or an Assistant-handled action:
It’s a seemingly subtle distinction but a significant one when it comes to real-world impact. Having Assistant right there, integrated in with everything else, makes it feel like a natural extension of the operating system. And it makes the idea of this “everything button” — the “Google button” — feel powerful and complete. Quite honestly, it’s something you resent not having when you work on Chrome OS and then go back to a more traditional operating system environment.
(And here’s a little secret: You can actually get that native Assistant Launcher integration on any current Chromebook, even if it doesn’t have the Pixel branding. I shared the specific steps in this issue of my newsletter.)
Factor in Google’s ongoing plan to turn the Play Store into a unified, all-in-one Chromebook app market, and you can see how the long-scattered pieces of the Chrome OS ecosystem are finally starting to coalesce into something sensible.
Chrome OS is on the brink of becoming the place where Google’s best capabilities come together to form a whole new kind of connected experience. It’s an exciting new start for intelligent desktop computing — and beyond that, it shows us the type of thoroughly connected Google experience Android could, should, and hopefully one day will also provide.
Want even more Googley knowledge? Sign up for my weekly newsletter to get next-level tips and insight delivered directly to your inbox.
Contributing Editor JR Raphael serves up tasty morsels about the human side of technology. Hungry for more? Join him on Twitter or sign up for his weekly newsletter to get fresh tips and insight in your inbox every Friday.
- Latest news
- Android 11
- Android 10
- Android OS
- Chrome OS
- Android TV
- Android Auto
- App Reviews
- Game Reviews
- All reviews
- Phone Reviews
- Tablet Reviews
- Wearable Reviews
- Other Reviews
The easiest way to mount your Synology NAS on your Chromebook
It’s been over three years since I started using my Synology DiskStation NAS to store every photo, video, and other file type I want to keep. In the time since, I’ve struggled a lot with Synology’s web interface, especially its poor file manager experience that refreshes each time you make a simple change. To avoid that, I’ve been looking for solutions to mount the DiskStation’s storage on my Pixelbook, but no tutorial or forum thread suggestion worked. Most were incomplete, others were outdated, some used unnecessary extensions, etc. After multiple trials and errors, and after mixing several recommendations from different users, I managed to get my NAS’s shared folders on my Pixelbook, which has made file management a breeze. I’ll share that method below.
To mount Synology, we’ll use SMB file shares, which have been supported on Chrome OS since 2018. So we need to enable SMB file sharing on the NAS, set up shared folders, and then mount the SMB folders onto Chrome OS.
Step 1: Enable SMB3 on Synology
In your DiskStation’s web interface, go to Control Panel then File Services. Click to Enable SMB service in the first tab.
Now click on Advanced Settings below the SMB section and change the Maximum SMB protcol to SMB3 then click Apply. You need that to ensure your Chromebook can mount shared folders.
Note: In the screenshot above, I set the minimum SMB protocol to SMB1. It works that way, but SMB1 is insecure. As far as I understand, that won’t matter if you’re only going to mount your Synology folders on Chrome OS, because the latter needs and uses SMB3. But if you want to make sure your shares are more secure (should you inadvertently connect an older SMB1 client in the future), you should set the minimum to SMB2. Everything else in this tutorial stays the same and works as expected. Thanks, Oliver!
Step 2: Check shared Synology folders
Next, you need to verify that you have access to the NAS shared folder(s) you’re trying to mount.
On your Synology, open the Control Panel, and go to Shared Folder. This is where the default shared folders (photo, music, video) and the user-created ones can be seen. In my case, I’m looking at my video folder.
Right click on that then click Edit and go to the Permissions tab. You can now see what privileges each user has for that folder. In my case, my rita user has Read/Write access to the video folder that I want to mount. If your user doesn’t, make sure the Synology admin grants it that permission.
Another way to check which folders your user has access to is to go to the User section in Synology’s Control Panel, choose your username, go to the Permissions tab, and see the list of folders you can access and with which permissions. That way, you know what you can mount.
Step 3: Find your Synology’s local IP
Before we start adding these folders to Chrome OS, we have to get our Synology’s local IP address. To do that, you can check your router’s device admin page, copy the URL from the browser when you open the DiskStation’s web interface, or simply go to find.synology.com. This page will look for any Synology on your network and give you its local IP address. It should be formatted as 10.0.0.xyz or 192.168.1.xyz.
Step 4: Time to mount on Chrome OS
Grab your Chromebook and open the Files application. Click the overflow (three-dot) button on the top right, then Add new service > SMB file share.
In the window that shows up, fill up this info:
- File share URL: your IP address from step 3 and your shared folder from step 2, formatted as \\IPaddress\sharedfolder — in my case, it’s \\10.0.0.64\video
- Display name: pick the name you want to see in Chrome OS for this folder — I went for “video”
- Username: your Synology user name (unless the shared folder you picked is open to guests, but I don’t recommend doing that)
- Password: your Synology user’s password.
Now click Add and the folder will be mounted in the sidebar of the Files app on your Chromebook.
Repeat this for every folder you want to mount. Below, you can see I’ve added my photo, home, music, book, and video folders in Chrome OS. These mounts survive multiple reboots and can only be removed by right clicking then choosing Close.
In a mounted folder, you can browse files and sub-folders, open and rename files, download them to your computer, move them around, and more, as if you’re browsing a local storage on your Chromebook. Chrome OS’s regular keyboard shortcuts for renaming, cutting, pasting, creating folders, etc. work as intended. You also don’t need to wait for the Synology web client to refresh each time you move or rename a file or folder. That is painful if you manage a lot of files on your NAS.
Things only slow down when you want to move things from one mounted folder to another — Chrome OS doesn’t seem to understand you’re going through the same NAS, and handles it very slowly as if you’re moving things between two different ones. You’re better off making those moves through Synology’s web interface.
Besides this small inconvenience, I’m currently managing all my mounted folders from Chrome OS instead of Synology’s web client. It’s much faster and more efficient.