How it works
The story of how your traffic gets through
Some networks put a checkpoint on the road to the internet. It opens every parcel, reads the labels, and quietly drops anything that looks like a VPN. Engineers call it deep packet inspection — DPI.
ForestVPN answers with an adaptive ladder of counter-moves — and always uses the lightest one that works. This page tells the whole story: simply enough for a five-year-old, precisely enough for an engineer.
The disguise game
Your traffic has to walk past a checkpoint. ForestVPN gives it better and better disguises — but only as many as the checkpoint demands.
Your message sets out. On easy networks, it just walks through.
Region tiers decide the starting rung: free / monitored / censored.
First trick: the walker wears no name tag. Nothing about it says what it is.
T0 — keyed discovery + obfuscated headers: no cleartext fingerprint. Always on, on every plan.
The guard starts measuring everyone. So the walker changes size — and uses a different door each time.
T1 — padding + multi-port: telltale sizes and the single well-known port go away.
Now the guard listens for a certain accent. The walker answers in a completely different language.
T2 — Shadowsocks-2022 encapsulation.
Best disguise yet: look exactly like everybody else.
T3 — QUIC mimicry: shaped like the busiest traffic on the internet.
Send three walkers down three roads at once. Whoever gets through first wins.
T4 — race all transports: first road through carries the session.
For the very strictest checkpoints, the walker even changes how it walks.
T5 — maybenot/DAITA traffic shaping. Opt-in — you switch it on.
ForestVPN climbs only as high as your network demands — and steps back down when it can.
Tiers are retuned per region, server-side — no app update needed.
The packet that vanished
Watch one marked parcel become impossible to pick out of the crowd.
Every message is a little parcel. An inspector can read the labels.
Classic VPN protocols announce themselves in cleartext.
First, we take the label off.
Keyed discovery + obfuscated headers — nothing left to read.
Then we make the parcel the same size as everyone else’s.
Padding evens out the telltale lengths.
New wrapping paper — the same kind everyone uses.
Re-encapsulation (Shadowsocks-2022) or QUIC mimicry: the wrapping itself is ordinary.
Now even a careful inspector sees five ordinary parcels. Only you know which is yours.
That’s the whole trick: not stealth theater — nothing to match.
That’s what “nothing to find” means.
How ForestVPN handles censored networks
The handshake that agrees the keys
Before any data moves, your device and the server run a modern handshake to agree on the keys that lock the tunnel — with fresh keys for every session.
A modern, WireGuard-style handshake
Every session opens with a modern WireGuard-style handshake, and the shared keys are derived through a BLAKE2s-based key-derivation chain.
Fresh keys, forward secrecy
The key exchange uses ephemeral per-session X25519 keys, and each session rekeys periodically — so a key that is ever exposed can't unlock past or future traffic.
For the curious
Under the hood: an X25519 key exchange with ephemeral per-session secrets, a HMAC-BLAKE2s key-derivation chain, and a ChaCha20-Poly1305 data cipher. Sessions rekey on a timer and old sessions are retired, so forward secrecy holds even if a single key is later exposed.
Post-Quantum Cipher Suite
The Post-Quantum Cipher Suite is a planned Premium and Enterprise feature: a hybrid key exchange that pairs today's classical handshake with a post-quantum algorithm, so both would have to be broken at once.
Why it matters: encrypted traffic can be recorded today and decrypted years from now, once quantum computers catch up. A hybrid exchange defends against that by combining two independent key agreements — if one is ever broken, the other still holds. Today ForestVPN's tunnel already uses a modern, forward-secret handshake; the post-quantum half is on the roadmap, not yet shipped.
Planned for Premium and Enterprise plans.
The road and the relay
When the straight road closes, another one lights up.
Usually your traffic takes the straight road.
Direct connections use UDP with NAT hole-punching.
Sometimes the road is closed.
Some networks block UDP entirely.
So ForestVPN sends it up and over — through a relay.
The DERP relay network, operated by ForestVPN.
The relay talks the same way normal websites do — so the road stays open.
When UDP is blocked, relays fall back to TLS; QUIC-DERP keeps it fast where QUIC is allowed.
You can tell it which roads you prefer.
Routing Mode: Automatic / Direct-preferred / Relay-only.
The moment the straight road opens again, ForestVPN takes it — that’s the fast lane.
Relays stay standing by; direct comes back the instant it works.
Chain hops into a route
On Pro and Premium you can send your traffic through more than one hop — Entry, then an optional Relay, then Exit — and leave through the last one.
Entry → Relay → Exit
Chain hops in order and route out through the last one; the order you chain them is the order your traffic is forwarded.
How many hops your plan allows
Hop depth is plan-gated: Free is a single hop, Pro allows up to two, and Premium up to three.
For the curious
Each route is a RouteChain of Entry, Relay and Exit hops. Every participant derives the same chain id independently from the hop list — there's no central coordinator, so a mismatch simply means the hop lists differ.
Choose what rides the tunnel
Split tunneling lets you exclude specific routes or apps from the tunnel, so they use your normal connection while everything else stays protected.
Exclude the routes you pick
Pick routes or apps to leave out of the tunnel — they take the normal connection, and everything else keeps going through ForestVPN.
A separate, on-device rule
Your exclusions are a separate, client-local policy — kept apart from the tunnel's normal routing, not folded into it.
For the curious
Exclusions are a client-local split-tunnel policy applied on top of the normal route table — the excluded routes are handed to the platform as a distinct exclude-list, never merged into the tunnel's own routes.
Devices that find each other by name
MagicDNS gives every device on your private mesh a real name — like nas.mesh.fvpn.net — so your devices reach each other by name, from any network.
Automatic names
Every device gets a name under *.mesh.fvpn.net the moment it joins — nothing to configure, no IP addresses to remember.
Split-DNS
Only your mesh names resolve through the mesh; every other lookup goes exactly where it normally would.
Rename on the fly
Rename a device and the new name follows instantly — the tunnel never restarts.
No DNS leaks
When you route through an exit node, DNS queries stay inside the tunnel instead of leaking to the local network.
Route out through your own devices
You can make a device you own the exit, so your traffic leaves through your own hardware — and the tunnel is built to keep as little as possible.
Own-device exit is free
Route your traffic out through a device you own as an exit node — single-hop, own-device exit is free on every plan.
Runs anywhere, even sandboxed
On mobile and other sandboxed platforms the exit runs in a userspace network stack, so it works without kernel-level routing.
Private by design
The relay only forwards already-encrypted packets and never reads what's inside, and your DNS lookups stay inside the tunnel. What we store is spelled out in our privacy policy.
For the curious
On iOS, Android and tvOS the exit runs on a smoltcp userspace network stack rather than kernel routing; the DERP relay forwards opaque WireGuard-encrypted packets by node public key and cannot decrypt them.
Common questions
What encryption does ForestVPN use?
Your traffic travels inside a WireGuard-family (Noise-protocol) tunnel sealed with the ChaCha20-Poly1305 authenticated cipher, so anyone watching the network sees only ciphertext and a verification tag — not your data.
Can the relay see my traffic?
No. When two devices can't connect directly, ForestVPN falls back to an encrypted relay (DERP) that only forwards already-encrypted packets by node public key — it never decrypts what's inside.
Does ForestVPN support multi-hop?
Yes. On Pro and Premium you can chain hops — Entry, an optional Relay, then Exit — and route out through the last one. Free is a single hop, Pro allows up to two, and Premium up to three.
Can I exclude some apps or routes from the VPN?
Yes. Split tunneling lets you exclude specific routes or apps so they use your normal connection while everything else stays protected.
Does ForestVPN use post-quantum encryption?
Not today. ForestVPN's tunnel uses a modern, forward-secret classical handshake. A Post-Quantum Cipher Suite — a hybrid key exchange — is planned for Premium and Enterprise plans, but it is on the roadmap, not yet shipped.
Can I use one of my own devices as the exit?
Yes. You can route your traffic out through a device you own as an exit node; single-hop, own-device exit is free on every plan.
Ready for a VPN that adapts?
One app. The right disguise, only when it's needed.