1. Home
  2. Protocols overview

Protocols overview — WireGuard, OpenVPN, Stealth and when to switch

A working editorial guide to Proton VPN supported protocols. WireGuard for speed, OpenVPN for legacy compatibility, Stealth for restrictive networks. The trade-offs that matter and when to switch between them.

Read the security overview

01. What this page covers

Three primary protocols cover most use cases.

WireGuard is the modern, fast, default choice. Lower latency, higher throughput, smaller code surface than OpenVPN. WireGuard is the right default unless a specific failure mode requires switching.

OpenVPN (UDP and TCP variants) is the legacy battle-tested protocol. Slower than WireGuard but compatible with restrictive networks where WireGuard might be blocked. Use OpenVPN UDP first, OpenVPN TCP only if UDP fails.

Stealth is a Proton-specific protocol designed to evade VPN-blocking firewalls. Trades speed for connectivity in the most restrictive networks. Use Stealth when both WireGuard and OpenVPN fail to connect.

Read the security overview →

02. How it fits with the rest of the Proton VPN reference hub

How protocol choice affects user experience.

WireGuard typically delivers 30-50 percent higher throughput than OpenVPN UDP on identical hardware. The latency difference is smaller but still favors WireGuard. For streaming, file transfer and gaming use cases, WireGuard is meaningfully better.

OpenVPN remains useful where WireGuard's UDP-only nature creates problems. Some corporate firewalls block UDP entirely; OpenVPN TCP works in those environments.

Stealth's connectivity trade-off matters most for travelers and users in restrictive regimes.

Read the security overview →
Proton VPN protocols at a glance
ItemDetailNotes
WireGuardModern, fast, UDP-onlyDefault for most users
OpenVPN UDPLegacy battle-testedUse if WireGuard blocked
OpenVPN TCPSlower, more compatibleUse if UDP blocked
StealthDisguises as HTTPSUse in restrictive networks
IKEv2Mobile-friendly legacyLimited Proton support

Protocols overview — reader questions

Five common questions reproduced from the reader inbox.

01. Which Proton VPN protocol should I use?

WireGuard for most users. OpenVPN UDP if WireGuard fails. OpenVPN TCP if UDP fails. Stealth in restrictive networks.


02. Is WireGuard secure?

Yes. Modern cryptographic primitives, smaller attack surface than OpenVPN, audited extensively. Industry-standard for new deployments.


03. Why is OpenVPN slower than WireGuard?

Larger code surface, older cryptographic primitives, less efficient encapsulation. WireGuard was designed specifically to address these limitations.


04. What is Proton VPN Stealth?

Proton-specific protocol that disguises VPN traffic as regular HTTPS to evade VPN-blocking firewalls. Slower than WireGuard but more connective.


05. Should I switch protocols often?

No. Pick a default (WireGuard) and switch only when a specific failure mode demands it.

Methodology — how we research and revise

A reproducible methodology beats opinion-based recommendation at every horizon longer than a single subscription cycle.

The reader desk works from four recurring inputs. Weekly catalog and pricing scrapes capture promotional cycles and feature changes. Annual third-party security audits, when published by independent firms, inform the security overview pages. Reader inbox traffic — roughly 600 messages per week on the privacy-software beat — identifies the friction points real users hit. Published Swiss court rulings affecting the broader privacy-software ecosystem, when issued, drive event-driven jurisdiction-page updates.

Revision cadence is weekly for tracker pages, monthly for category explainers and event-driven for security audits, regulator actions or major policy changes. Every page carries a visible last-updated date in the byline. When facts change, the portal prefers visible revision notes over silent edits, because privacy-software readers benefit from seeing how context evolves rather than reading a static snapshot.

Independence is enforced, not claimed. Editors do not hold equity in any privacy-software provider, do not accept affiliate income from any provider, and decline partner-authored copy under any byline. Conflicts of interest, when applicable to a contributor's prior employment in privacy-software, surface at the top of the affected article rather than buried in disclosures footers. Reader donations and newsletter subscriptions are the only revenue streams. The Electronic Frontier Foundation and Privacy International archives provide external frameworks the reader desk consults.

Privacy-software market context in 2026

Understanding the broader privacy-software landscape helps shoppers evaluate any single offering in proper context.

The privacy-software market expanded materially through the 2020s as households became more aware of internet service provider tracking, public Wi-Fi exposure and the data-broker ecosystem. The post-2020 shift toward remote work pushed adoption further, particularly in households where employer-supplied corporate VPNs did not cover personal browsing.

Three structural dynamics shape the 2026 market. First, jurisdictional differentiation: providers domiciled outside major surveillance alliances (Switzerland, Panama, British Virgin Islands) have positioned legal independence as the central trust-building claim. Second, audit transparency: open-source clients with independent security audits have become table stakes for credible providers. Third, multi-product bundling: privacy companies have expanded from single-product offerings into broader privacy-tool ecosystems covering email, file storage, password management and calendar. The bundle math now competes directly with single-product specialty offerings.

Regulatory attention from consumer-protection bodies and privacy commissioners affects how providers communicate features. The Federal Trade Commission has issued guidance on VPN advertising claims; the European Data Protection Board issues rulings affecting EU-jurisdictions providers. The portal tracks regulator actions as event-driven inputs to coverage.

What this hub is and is not

A scope statement keeps reader expectations aligned with reality.

This hub is editorial. It does not sell subscriptions, does not run affiliate links, does not accept supplier placement fees and does not link to commercial properties from body content. Outbound links route to government, educational and editorial sources only. Reader donations and newsletter subscriptions are the funding model. The desk reads every inbound message and synthesises monthly into category-page revisions.

The hub is not the official site for any privacy-software product. Account creation, subscription billing, official client downloads and customer-support tickets all live on the relevant company's official property. Search the official URL directly when reaching for those functions. The disambiguation page covers this distinction in detail.