How to Fix Slow WiFi on a Chromebook on Battery: ChromeOS Power Preferences, WiFi Adapter Settings, and Network Reset Fixes

If your Chromebook’s WiFi feels sluggish the moment you pull the charger, you’re not imagining it. ChromeOS aggressively throttles the WiFi adapter when running on battery to extend runtime. The radio periodically powers itself down for milliseconds at a time — a technique called WiFi power save mode — which adds small delays that pile up into noticeably slower speeds, higher ping, and choppy video calls. The good news: there are several targeted fixes before you need to consider a full reset.

Step 1: Disable Battery Saver Mode

ChromeOS includes a Battery Saver feature that, when enabled, reduces system performance and throttles background network activity to extend battery life. If it switched on automatically (which it does when battery drops below a threshold), it can compound the WiFi power-save slowdown.

To turn it off: open Settings, scroll down to Device, select Power, and toggle off Battery Saver if it’s enabled. You can also set the threshold at which it activates — raising it from 20% to “Never” while you troubleshoot ensures it isn’t interfering. Run a speed test immediately after making this change to see if speeds improve.

Step 2: Disable WiFi Power Save via Crosh

This is the most direct fix for battery-related WiFi slowdowns. ChromeOS includes a built-in shell called Crosh that exposes a dedicated wifi_power_save command.

Press Ctrl + Alt + T on your Chromebook to open the Crosh terminal, then type:

wifi_power_save disable

Press Enter. ChromeOS will immediately stop throttling the WiFi adapter. You should see a confirmation message, and running a speed test right after will usually show a significant improvement in both throughput and latency.

Important caveat: this setting does not survive a reboot. Every time you restart your Chromebook, WiFi power save mode re-enables itself automatically. There is currently no supported way to make the change permanent in standard ChromeOS. You’ll need to run the command again each session when on battery — or simply stay plugged in when you need full WiFi performance. To re-enable it (to restore battery savings), run wifi_power_save enable.

Step 3: Switch to the 2.4 GHz Band

The 5 GHz and 6 GHz bands deliver faster theoretical speeds but have shorter effective range and worse penetration through walls. When your Chromebook is on battery and the WiFi adapter is throttled, a weak 5 GHz signal degrades more noticeably than a strong 2.4 GHz one.

If your router broadcasts both bands under the same network name (band steering), you can force the 2.4 GHz band by temporarily splitting them in your router’s admin interface — assigning names like “HomeNetwork_2.4” and “HomeNetwork_5” — then connecting your Chromebook specifically to the 2.4 GHz SSID. This won’t solve the power save issue, but it provides a more stable baseline if signal quality is compounding the problem. See our comparison of 2.4 GHz vs 5 GHz vs 6 GHz bands for a deeper look at range trade-offs.

Step 4: Forget the Network and Rejoin

Corrupted network credentials or stale DHCP leases can cause slow performance that looks like a power management problem. Go to Settings → Network → WiFi, click the gear icon next to your network name, and select Forget. Then reconnect by selecting your network from the list and entering your password. ChromeOS will negotiate a fresh connection and pick up any updated router configuration.

Step 5: Change Your DNS Server

The “connected but everything loads slowly” symptom — where pages take 3–5 seconds to begin loading despite showing full WiFi bars — often points to DNS latency rather than throughput. Your ISP’s default DNS resolvers can be slow or temporarily overloaded.

To switch DNS on ChromeOS: go to Settings → Network → WiFi → click the gear icon next to your network → Network → Name Servers. Select Custom name servers and enter 1.1.1.1 and 1.0.0.1 (Cloudflare) or 8.8.8.8 and 8.8.4.4 (Google). Both are free and consistently outperform ISP resolvers in latency benchmarks. Our guide on the best DNS servers for faster internet covers the performance differences in detail.

Step 6: Update ChromeOS

Google ships WiFi driver fixes and power management patches in point releases. An outdated ChromeOS version can contain a known WiFi regression that a recent update already addresses. Go to Settings → About ChromeOS → Check for updates. If an update is available, install it and restart. Updates are typically 100–300 MB and install in the background; a restart applies them.

Step 7: Remove Unused Saved Networks

ChromeOS stores credentials for every network you’ve ever connected to. If it detects a saved network nearby — even one with poor signal — it may attempt to roam to it, causing brief disconnections that look like slowness. Go to Settings → Network → WiFi → Known networks and remove any networks you no longer use. This is especially relevant in apartment buildings where you may have connected to a neighbor’s open network at some point.

Last Resort: Powerwash

If none of the above resolves the issue, a Powerwash — ChromeOS’s factory reset — will wipe all local data, cached network settings, and any corrupted ChromeOS system files back to a clean state. Go to Settings → Advanced → Reset settings → Powerwash → Restart. Your Google account, cloud-saved apps, and Google Drive files all sync back automatically after you sign in. Run the Crosh wifi_power_save disable command again after setup if you want to disable power save on the fresh install.

When the Problem Is Hardware

If your Chromebook shows poor WiFi performance on every network, including new ones, and all software fixes fail, the WiFi adapter itself may be degraded. Some Chromebook models have known antenna hardware issues that worsen over time. A USB WiFi adapter can serve as a temporary replacement while you arrange a repair — ChromeOS supports most standard USB WiFi adapters without additional drivers. If your Chromebook is still under warranty, contact your manufacturer or Google support for a hardware diagnostic.