If every other device on your network is fine and only the Chromebook keeps dropping off, the router isn’t your problem — something on the Chromebook itself is killing the connection. Usually it’s one of three things: aggressive Wi-Fi power saving, the device jumping between saved networks, or a DNS/IP renewal that’s timing out. Here’s how to track down which one it is and kill it.
First, confirm it’s actually the Chromebook
Before changing any settings, connect a second device — phone, laptop, whatever — to the exact same network and watch it for ten minutes. If that device drops too, this isn’t a Chromebook issue, it’s your router or ISP, and no amount of tweaking ChromeOS will fix it. If everything else stays rock solid and only the Chromebook falls off, keep going below.
Kill Wi-Fi power save mode
This is the single biggest cause of random disconnects on Chromebooks, and most people never find it because it’s buried in a terminal command, not a settings menu. ChromeOS powers down the Wi-Fi radio slightly during idle moments to save battery. On most routers this is invisible. On some — especially older or budget routers — that micro-sleep is enough to drop the session entirely.
To turn it off, open the built-in terminal with Ctrl + Alt + T, which opens crosh (not a regular Linux terminal, just the Chromebook’s diagnostic shell). Then run:
wifi_power_save disable
You’ll see a confirmation that power save is off. Battery life takes a small hit, but the connection stops dropping. The catch: this setting is not persistent — it resets every time you reboot, so you’ll need to run it again after a restart. There’s currently no official way to make it stick permanently across reboots.
Stop it from switching between saved networks
If you’ve got more than one saved Wi-Fi network nearby — home, a neighbor’s, a phone hotspot you used once — ChromeOS can silently hop to whichever one it considers “preferred,” especially right after the Wi-Fi radio resets. This looks exactly like a random disconnect but it’s actually a reconnect to the wrong network.
- Click the clock in the bottom-right corner, then the Wi-Fi icon
- Select your actual network and open its settings
- Turn on Automatically connect to this network
- Turn on Prefer this network
While you’re in there, go to Known networks and delete anything you don’t use anymore. Fewer saved networks means fewer things for the Chromebook to get confused about.
Check if it’s dropping specifically when idle or the lid closes
If the pattern is “fine while I’m using it, dead the moment I look away,” this is a sleep/idle setting, not a Wi-Fi bug. Go to Settings > Power and set both While inactive and plugged in and While inactive and on battery to keep the display (and by extension, the connection) from sleeping. This won’t be the right call if you actually want your battery to last, so only leave it on when you’re troubleshooting or plugged in.
Rule out a DNS or IP renewal problem
Sometimes the Chromebook doesn’t actually lose the Wi-Fi signal — it loses the ability to resolve domains or renew its IP lease, and ChromeOS reports that as “disconnected” even though the radio link is technically still up. You’ll usually notice this as the Wi-Fi icon looking connected but nothing loading. Run a quick diagnostic from crosh:
network_diag --wifi
This dumps driver info and connection stats that’ll show you if DNS lookups are timing out. If they are, try switching your DNS to Google’s (8.8.8.8) or Cloudflare’s (1.1.1.1) under Settings > Network > Wi-Fi > your network > Network > Name servers, instead of leaving it on whatever your router hands out by DHCP.
Forget the network and rejoin from scratch
Chromebooks don’t have a “reset network settings” button the way phones do, so forgetting the network and re-adding it is the closest equivalent. It clears out any corrupted connection profile without touching anything else on the device.
- Click the clock, then the Wi-Fi icon
- Select your network, click Forget
- Reconnect and re-enter the password
Check for a pending ChromeOS update
Certain ChromeOS versions have shipped with known Wi-Fi bugs — it happens more often than Google would like to admit. If the disconnects started right after your Chromebook auto-updated, that’s not a coincidence. Go to Settings > About ChromeOS > Check for updates. If you’re already current, search the Chromebook Help Community for your exact ChromeOS version plus “wifi” — these bugs usually get reported and patched within a release or two.
Restart both ends
Obvious, but worth doing properly instead of skipping it: full shutdown on the Chromebook (not just closing the lid), and a full power cycle on the router — unplug it, wait 30 seconds, plug it back in. This clears temporary state on both sides and fixes a surprising number of “random” disconnects that nothing else explains.
Last resort: Powerwash
If none of the above sticks, a Powerwash (Chromebook’s factory reset) clears every saved network, cached credential, and misconfigured setting at once. It’s effective specifically because it removes accumulated network profile corruption that’s hard to isolate manually. But it wipes all local data — back up anything in your Downloads folder first, since that’s not synced to Google Drive automatically.
If the problem only started after visiting one specific network (a hotel, office, or campus Wi-Fi with a login portal), that network’s saved profile is often the actual culprit — forget just that one network rather than powerwashing the whole device.