Internet, Networking, & Security Browsers Google Chrome Not Responding? How to Fix It Get your browser up and running again By Nicholas Congleton Writer Nick Congleton has been a tech writer and blogger since 2015. His work has appeared in PCMech, Make Tech Easier, Infosec Institute, and others. our editorial process Twitter LinkedIn Nicholas Congleton Updated July 31, 2019 Browsers Chrome Safari Firefox Microsoft Tweet Share Email Google Chrome has grown well beyond simple browsing, to the point where it's really a suite of web tools all rolled into one extremely powerful package. There's a downside to all of this, though. As it becomes more complex, the more opportunities there are for something to go wrong. Quite often, this manifests in a frustratingly vague way, with you only being told, "Chrome is not responding." While there isn't a single all encompassing answer to this common problem, these steps can clear things up in most instances. How to Fix Chrome Not Responding Errors Even though there isn't one guaranteed solutions to the various problems that cause Chrome to stop responding, try these steps; there's a good chance Chrome will be as good as new by the end. Update to the latest version of Chrome. Before you start digging around in Chrome and risk losing settings or anything like that, select the three vertical dots > Help > About Google Chrome to open a new tab displaying information about your Chrome install. At the same time, Chrome will start searching for a newer version of itself. If it finds one, Chrome will automatically update. Clear your History/Cache. Cache is a funny thing. Most of the time, it helps you get where you need to much faster, but if it's corrupted, it can seriously ruin your day. It's almost always safe to clear your cache, so there's no reason not to try that next. You should throw your browsing history into that too. If there's any data that could have been corrupted, get rid of it. Disable extensions. Extensions are an integral part of the Chrome ecosystem, and they add an immeasurable amount of new features to the browser. However, some might not be actively maintained, and might fall out of date or develop incompatibilities with new versions of Chrome. Disable your extensions one at a time to see if one is the source of your problem. Clear your DNS Cache. While not actually related to Chrome itself, it does has a serious impact on your network connection. DNS allows your browser to find websites with URLs instead of IP addresses, so it's pretty important; to get to your favorite websites faster, your computer caches DNS. It's best to clear it out, in case something's corrupted or something went wrong. Make sure your firewall isn't blocking Chrome. It might seem like a no-brainer, but if you've been doing any work on your firewall, it's always a good idea to make sure your new settings don't blocking Chrome. Linux users can also check their firewall settings to see if Chrome is being blocked, though it won't explicitly be listed as Chrome. Open a terminal and check to see that both incoming and outgoing traffic are allowed on ports 80 and 443. Use either of these two commands: $ sudo iptables -S or $ sudo ufw status Reset Chrome to Default. Finally, when all else fails, you can reset Chrome to its factory default settings. It's always possible something was corrupted or your particular combination of settings is causing a problem. The only way to know for sure is to reset everything to the way it was when you installed Chrome the first time. Reinstall Chrome. If it seems like nothing is working, reset Chrome to default, uninstall it, and install it again. That's the most complete way to reset Chrome, but it's usually not necessary to go that far.