TLS 1.3 vs TLS 1.2: Key Differences, Security Improvements, and How to Enable It

What is TLS 1.3?

TLS (Transport Layer Security) is the cryptographic protocol that secures HTTPS connections. TLS 1.3 is its current version, replacing TLS 1.2 (2008) with a design that was informed by a decade of real-world attacks — BEAST, CRIME, POODLE, FREAK, Logjam — that exploited weaknesses in TLS 1.2's negotiation flexibility.

Where TLS 1.2 offered dozens of cipher suite combinations and multiple key-exchange modes, many of them insecure, TLS 1.3 takes the opposite approach: it defines a small, all-modern cipher suite list, removes every optional algorithm that contributed to historical attacks, and mandates the cryptographic properties that were previously optional.

The handshake: 2-RTT (TLS 1.2) vs 1-RTT (TLS 1.3)

The handshake is the negotiation phase before any application data flows. Each "round-trip" (RTT) is one exchange between client and server — a full network latency penalty. Reducing round-trips directly reduces page load times, particularly on high-latency connections like mobile networks.

The key difference: in TLS 1.3, the client includes its key share guess in the very first message (ClientHello), so the server can compute the session key immediately and begin encrypting from step 2. In TLS 1.2, the key material wasn't exchanged until step 3. The result: TLS 1.3 connections open in roughly half the round-trips, which on a 100 ms latency path saves a full 100 ms per new connection.

Security improvements

TLS 1.3 does not merely add new features — it removes entire categories of risk by eliminating the mechanisms that made past attacks possible.

TLS 1.3 cipher suites

TLS 1.2 supported well over 300 cipher suite combinations — the product of multiple key-exchange algorithms, bulk encryption algorithms, and MAC algorithms. Many of those combinations were weak. TLS 1.3 defines exactly five cipher suites, all AEAD-based. The naming convention changes too: TLS 1.3 suites specify only the symmetric encryption and hash functions, because the key exchange is no longer part of the cipher suite (all exchanges use ephemeral DH).

In practice you don't need to configure cipher suites for TLS 1.3 — the server and client negotiate the best available option automatically. This is a deliberate design choice: the old model of administrators hand-picking cipher suites was a major source of misconfiguration. If you want to learn how to read a suite name and which legacy TLS 1.2 suites to disable, see our guide to TLS cipher suites.

0-RTT resumption: speed vs safety trade-off

TLS 1.3 also introduces 0-RTT (zero round-trip time) resumption. When a client reconnects to a server it visited recently, it can send encrypted application data in the very first message — before the handshake completes. This eliminates handshake latency entirely for returning visitors.

Note that 0-RTT also breaks strict forward secrecy for the resumed session: the pre-shared key used for 0-RTT data derives from the previous session's key, so a compromise of that key can expose 0-RTT data. For most production sites, the performance gain of 0-RTT is modest (it only helps returning visitors) and the security trade-off isn't worth it. Enable it only after a deliberate application-layer review.

Browser and server support

TLS 1.3 is supported by all major browsers and web server software since 2019. In 2026, it is the default negotiated version for connections between modern clients and servers that advertise it.

Enable TLS 1.3 on Nginx

If you're new to Nginx SSL setup, start with our Nginx SSL installation guide first. To add TLS 1.3 to an existing Nginx config, update the ssl_protocols directive in your server block:

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    server_name yourdomain.com;

    ssl_certificate     /etc/ssl/yourdomain.crt;
    ssl_certificate_key /etc/ssl/yourdomain.key;

    # Enable TLS 1.2 and 1.3; disable 1.0, 1.1
    ssl_protocols TLSv1.2 TLSv1.3;

    # TLS 1.2 cipher suites (TLS 1.3 ciphers are auto-negotiated)
    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305;
    ssl_prefer_server_ciphers off;

    # Session resumption
    ssl_session_timeout 1d;
    ssl_session_cache shared:SSL:10m;
    ssl_session_tickets off;

    # HSTS (optional but recommended)
    add_header Strict-Transport-Security "max-age=63072000" always;
}

After editing, test and reload:

sudo nginx -t && sudo systemctl reload nginx

Adding HSTS alongside TLS 1.3 eliminates the remaining HTTP downgrade window and is strongly recommended for any production site.

Enable TLS 1.3 on Apache

See our Apache SSL installation guide for complete setup. To enable TLS 1.3 on an existing Apache virtual host, update your SSL directives:

<VirtualHost *:443>
    ServerName yourdomain.com

    SSLEngine on
    SSLCertificateFile    /etc/ssl/yourdomain.crt
    SSLCertificateKeyFile /etc/ssl/yourdomain.key
    SSLCACertificateFile  /etc/ssl/ca-bundle.crt

    # Enable TLS 1.2 and 1.3; disable older versions
    SSLProtocol -all +TLSv1.2 +TLSv1.3

    # TLS 1.2 cipher suites (TLS 1.3 ciphers are handled automatically)
    SSLCipherSuite ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305
    SSLHonorCipherOrder off
    SSLSessionTickets off

    # HSTS
    Header always set Strict-Transport-Security "max-age=63072000"
</VirtualHost>

Test and restart:

sudo apachectl configtest && sudo systemctl restart apache2

Enable TLS 1.3 on IIS

IIS 10.0 on Windows Server 2022 enables TLS 1.3 by default. On Windows Server 2016 and 2019, TLS 1.3 may require a manual registry edit. See our IIS 10+ SSL installation guide for the full certificate setup context.

To enable TLS 1.3 via the Windows Registry, open regedit.exe as Administrator and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

Create the following key structure if it doesn't exist, then create DWORD values:

# TLS 1.3 Server (enable)
Protocols\TLS 1.3\Server
  Enabled        = 1 (DWORD)
  DisabledByDefault = 0 (DWORD)

# TLS 1.3 Client (enable)
Protocols\TLS 1.3\Client
  Enabled        = 1 (DWORD)
  DisabledByDefault = 0 (DWORD)

# TLS 1.0 Server (disable)
Protocols\TLS 1.0\Server
  Enabled        = 0 (DWORD)
  DisabledByDefault = 1 (DWORD)

# TLS 1.1 Server (disable)
Protocols\TLS 1.1\Server
  Enabled        = 0 (DWORD)
  DisabledByDefault = 1 (DWORD)

Restart the server after making registry changes. Alternatively, use IIS Crypto (a free tool from Nartac Software) for a GUI-based approach — it automates the registry edits and supports applying Mozilla's recommended cipher suite profiles.

Verify your TLS 1.3 configuration

After enabling TLS 1.3, confirm it's negotiated correctly using one of these methods:

# Test TLS 1.3 connection
openssl s_client -connect yourdomain.com:443 -tls1_3

# Confirm protocol in the output — look for:
# Protocol  : TLSv1.3
# Cipher    : TLS_AES_128_GCM_SHA256

Frequently asked questions