How to Completely Disable ‘Quic Protocol’ (UDP HTTP/3) in Google Chrome

Modern internet browsing relies heavily on the TCP protocol to ensure packets of data arrive in the correct order. However, Google developed a faster, experimental protocol called QUIC (Quick UDP Internet Connections), which is now the foundation for HTTP/3. By default, Google Chrome uses QUIC to drastically speed up connections to Google’s own servers (like YouTube and Gmail) by firing UDP packets without waiting for traditional TCP handshakes.

While this is great for raw speed, it is a nightmare for network administrators and users with strict firewall configurations. Many enterprise firewalls, parental control routers, and older VPNs do not know how to inspect or filter QUIC’s encrypted UDP traffic. Because the firewall cannot read the packets, it simply blocks them or lets them bypass security rules entirely. If you are experiencing strange connection drops on YouTube while connected to a corporate VPN, or if your network monitoring software is failing to log traffic, you must completely disable the QUIC protocol in Chrome.

Disabling QUIC via Chrome Experimental Flags

Because QUIC is deeply embedded into Chrome’s networking stack, you cannot turn it off from the standard settings menu. You must disable it using Chrome’s advanced developer flags.

  1. Open the Google Chrome web browser.
  2. Click into the URL address bar at the very top of the window.
  3. Type the following exact string and press Enter:
    chrome://flags
  4. You will be taken to a page with a large warning stating “Experiments.”
  5. At the top of this page, there is a dedicated “Search flags” search box. Click into it and type QUIC.
  6. The page will filter down to a single flag named Experimental QUIC protocol.
  7. Look at the dropdown menu to the right of this flag. By default, it is set to “Default.”
  8. Click the dropdown menu and change the setting to Disabled.

Relaunching the Network Stack

Changing a networking protocol requires a complete restart of the browser.

  1. As soon as you change the dropdown to Disabled, a large blue Relaunch button will appear at the bottom of the Chrome window.
  2. Click Relaunch. Chrome will close all your tabs, shut down its background processes, and immediately reopen.

Once Chrome restarts, it will completely abandon HTTP/3 and the QUIC protocol. It will fall back to using standard, highly-compatible TCP over HTTP/2 for all website connections. This will instantly resolve conflicts with strict firewalls, deep packet inspection tools, and older VPN clients.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.