Supported browsers

For the best experience with GitHub, we recommend using the latest version of Chrome, Edge, Firefox, or Safari.

In this article

About web browser support

We design GitHub with the latest web browsers in mind. We recommend that you use the latest version of one of the following browsers.

If you do not use the latest version of a recommended browser, or if you use a browser that is not listed above, GitHub or some features may not work as you expect, or at all.

For more information about how we maintain browser compatibility for GitHub's products, see the github/browser-support repository.

Some browser vendors provide extended support releases. We do our best to ensure that GitHub functions properly in the latest extended support release for:

In earlier extended support releases, GitHub may not work as you expect, and some features may not be available.

Public preview and developer builds

You may encounter unexpected bugs in public preview and developer builds of our supported browsers. If you encounter a bug on GitHub in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer.

Troubleshooting browser behavior

Even when you use a supported browser, software or settings on your device or your network configuration can change how GitHub behaves. If you experience unexpected behavior, try the following steps to identify possible causes.

  • Disable browser extensions and plug-ins. Content blockers, ad blockers, and other third-party extensions can alter or block expected functionality. Disable them, or test in a private or incognito window with extensions turned off.
  • Check for a proxy, firewall, or content filter. Network devices such as proxies, firewalls, or content filters, including any that inspect Transport Layer Security (TLS) traffic, can modify or block requests to GitHub. If possible, retest on a network without these devices.
  • Disconnect from your virtual private network (VPN). A VPN can route your traffic through proxies, firewalls, or inspection services that alter or block requests. If possible, disconnect from the VPN and retest.
  • Check your antivirus or endpoint security software. Web protection, HTTPS scanning, or similar features in antivirus and endpoint security software can alter page behavior. Temporarily disable these features if your organization's policies allow, and retest.
  • Clear your cache and cookies. Stale or cached assets from a previous session can cause unexpected behavior. Alternatively, test in a fresh private or incognito window.
  • Retest in a different supported browser. This helps you determine whether the issue is specific to one browser or environment.
  • Try a different device or network. Testing from another device, or from a different network such as a mobile connection, helps you determine whether the issue is specific to your device or network.

If the behavior continues after you rule out these factors, your network or system administrators may be able to provide further assistance, as they manage settings such as proxies, firewalls, and content filters. If the issue persists, contact us through the GitHub Support portal.