How to enable TLS 1.3 support in Firefox and Chrome

Martin Brinkmann
Jun 15, 2017
Updated • Aug 14, 2018

The following guide provides you with instructions on enabling TLS 1.3 (Transport Layer Security) support in Mozilla Firefox and Google Chrome.

Transport Layer Security, short TLS, is a cryptographic protocol to communicate securely over a computer network. The current version of TLS is 1.2 while TLS 1.3 is available as a final version.

TLS 1.3 is based on TLS 1.2 but offers major security and privacy improvement over the protocol that web browsers support currently by default.

While it would go too far to list all improvements, you can check out the Wikipedia entry on TLS 1.3 for that, it does remove support for some cryptographic hash functions and named elliptic curves, prohibits use of insecure SSL or RC4 negotiations, or supports a new stream cipher, key exchange protocols or digital signature algorithms. It is also faster than TLS 1.2 by reducing the number of round-trips to 1 compared to TLS 1.2 using 2 round-trips.

Enable TLS 1.3 support in Firefox and Chrome

Both Firefox and Chrome support TLS 1.3, but the version of Transport Layer Security is not enabled by default. The main reason for that, likely, is that it is still only available as a draft.

Update: The final version of TLS 1.3 has been published.

Testing your browser's TLS capabilities

One of the first things that you may want to do is check which TLS and SSL protocols your browser supports.

One of the better options to test the capabilities is to visit SSL Labs, and there the "My Client" page which checks the browser's capabilities.

It reveals all protocols supported by the browser, checks whether the browser is vulnerable to certain known attacks, lists the supported cipher suites, protocol details, and how mixed content is handled by the browser.

If you run the test using Chrome or Firefox Stable right now, you will get a "no" next to TLS 1.3

Enable TLS 1.3 in Firefox

firefox tls 1.3 support

All recent versions of Mozilla Firefox support TLS 1.3 already. Users had to configure the maximum supported version previously on about:config to add support but that is no longer necessary.

Still, here is the way to make sure that TLS 1.3 is supported:

  1. Load about:config in the Firefox address bar.  Confirm that you will be careful if the warning screen is shown. The Firefox Configuration editor opens.
  2. Search for security.tls.version.max
  3. Change the value of the preference to 4 by double-clicking on it.

Enable TLS 1.3 in Chrome


Google Chrome supports TLS 1.3 by default as well. Google did change the flag recently that handles TLS. Currently, it is only possible to select different versions of TLS or disable it.

It is likely that Google will remove the option in the near future when it launches support for the final version of TLS 1.3

Please note that some Chromium-based browsers such as Vivaldi support the same flag. You can apply the change to these browsers as well.

  1. Load chrome://flags/ in the browser's address bar. This opens the experiments page of the web browser.
  2. Find Maximum TLS version enabled. You can also click on this link directly: chrome://flags/#tls13-variant
  3. You can set the feature to disabled, or pick one of the supported versions.
  4. Restart the web browser.

Closing Words

Some sites, like Cloudflare for instance, support TLS 1.3 already. Cloudflare customers may enable TLS 1.3 for their sites to "improve both speed and security for Internet users everywhere".

How to enable TLS 1.3 support in Firefox and Chrome
Article Name
How to enable TLS 1.3 support in Firefox and Chrome
The following guide provides you with instructions on enabling TLS 1.3 (Transport Layer Security) support in Mozilla Firefox and Google Chrome.
Ghacks Technology News

Tutorials & Tips

Previous Post: «
Next Post: «


  1. ilev said on August 4, 2012 at 7:53 pm

    Doesn’t Windows 8 know that www. or http:// are passe ?

    1. Martin Brinkmann said on August 4, 2012 at 7:57 pm

      Well it is a bit difficulty to distinguish between domains and files for instance.

    2. Leonidas Burton said on September 4, 2023 at 4:51 am

      I know a service made by google that is similar to Google bookmarks.

  2. VioletMoon said on August 16, 2023 at 5:26 pm

    @Ashwin–Thankful you delighted my comment; who knows how many “gamers” would have disagreed!

  3. Karl said on August 17, 2023 at 10:36 pm


    The comments section under this very article (3 comments) is identical to the comments section found under the following article:

    Not sure what the issue is, but have seen this issue under some other articles recently but did not report it back then.

  4. Anonymous said on August 25, 2023 at 11:44 am

    Omg a badge!!!
    Some tangible reward lmao.

    It sucks that redditors are going to love the fuck out of it too.

  5. Scroogled said on August 25, 2023 at 10:57 pm

    With the cloud, there is no such thing as unlimited storage or privacy. Stop relying on these tech scums. Purchase your own hardware and develop your own solutions.

    1. lollmaoeven said on August 27, 2023 at 6:24 am

      This is a certified reddit cringe moment. Hilarious how the article’s author tries to dress it up like it’s anything more than a png for doing the reddit corporation’s moderation work for free (or for bribes from companies and political groups)

  6. El Duderino said on August 25, 2023 at 11:14 pm

    Almost al unlmited services have a real limit.

    And this comment is written on the dropbox article from August 25, 2023.

  7. John G. said on August 26, 2023 at 1:29 am

    First comment > @ilev said on August 4, 2012 at 7:53 pm

    For the God’s sake, fix the comments soon please! :[

  8. Kalmly said on August 26, 2023 at 4:42 pm

    Yes. Please. Fix the comments.

  9. Kim Schmidt said on September 3, 2023 at 3:42 pm

    With Google Chrome, it’s only been 1,500 for some time now.

    Anyone who wants to force me in such a way into buying something that I can get elsewhere for free will certainly never see a single dime from my side. I don’t even know how stupid their marketing department is to impose these limits on users instead of offering a valuable product to the paying faction. But they don’t. Even if you pay, you get something that is also available for free elsewhere.

    The algorithm has also become less and less savvy in terms of e.g. English/German translations. It used to be that the bot could sort of sense what you were trying to say and put it into different colloquialisms, which was even fun because it was like, “I know what you’re trying to say here, how about…” Now it’s in parts too stupid to translate the simplest sentences correctly, and the suggestions it makes are at times as moronic as those made by Google Translations.

    If this is a deep-learning AI that learns from users’ translations and the phrases they choose most often – which, by the way, is a valuable, moneys worthwhile contribution of every free user to this project: They invest their time and texts, thereby providing the necessary data for the AI to do the thing as nicely as they brag about it in the first place – alas, the more unprofessional users discovered the translator, the worse the language of this deep-learning bot has become, the greater the aggregate of linguistically illiterate users has become, and the worse the language of this deep-learning bot has become, as it now learns the drivel of every Tom, Dick and Harry out there, which is why I now get their Mickey Mouse language as suggestions: the inane language of people who can barely spell the alphabet, it seems.

    And as a thank you for our time and effort in helping them and their AI learn, they’ve lowered the limit from what was once 5,000 to now 1,500…? A big “fuck off” from here for that! Not a brass farthing from me for this attitude and behaviour, not in a hundred years.

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.