WireGuard client setup: Windows, macOS, iOS, Android, Linux
Once you have a WireGuard server running, connecting a client is mostly the same flow on every platform: install the official app, import a config, toggle the tunnel. The details differ in places that matter — DNS, kill-switch behavior, auto-reconnect. Per-platform notes below.
Before you start
- You need a WireGuard server. If you don't have one, follow our bare-metal install or use wg-easy.
- You need a
client.conffile (text) or a QR code generated from it. - Always install the official WireGuard app — third-party "fast VPN" apps in the App Store are not the same thing.
iOS
Install: "WireGuard" by WireGuard Development Team in the App Store.
Import:
- Open the app, tap "Add a tunnel."
- Pick "Create from QR code." Point the camera at the QR generated by wg-easy or by
qrencode < client.conf. - Name the tunnel ("Home VPS" or similar).
- iOS prompts to add a VPN configuration — confirm with Face/Touch ID.
Activate: toggle the switch next to the tunnel. The VPN indicator appears in the status bar.
Verify: open Safari, visit ifconfig.me. The IP shown should be the server's VPS IP, not your cellular IP.
iOS gotchas:
- On-demand: the "On-Demand" toggle (Settings → tunnel → On Demand) auto-activates the VPN on certain networks. Useful for "always on when on untrusted Wi-Fi." Be aware that it can fire when you don't expect it.
- Per-app routing: not possible on iOS. AllowedIPs in the config decide what's tunneled, full stop.
- Battery: idle drain is negligible. Active throughput uses ~5-10% more battery than non-VPN browsing.
Android
Install: "WireGuard" by WireGuard Development Team in the Play Store, or via F-Droid.
Import:
- Tap the "+" button → "Scan from QR code."
- Or use "Import from file or archive" to load a
.conffile from local storage.
Android-specific features:
- Per-app inclusion / exclusion: Edit tunnel → "All applications" → switch to "Excluded applications" and pick apps that should bypass the VPN. Banking apps, geo-locked streaming apps are common picks.
- Auto-connect on boot: Settings → "Restore on boot." Useful for always-on tunnels.
- Background restriction: some OEMs (Samsung, Xiaomi) kill background VPN apps to save battery. Whitelist the WireGuard app in your phone's battery settings.
Windows
Install: download the official MSI from wireguard.com/install/.
Import:
- Open WireGuard. Click "Add Tunnel → Import tunnel(s) from file."
- Pick your
client.conf. - Click "Activate."
Windows gotchas:
- Killswitch: when AllowedIPs is
0.0.0.0/0, ::/0, the GUI also exposes a "Block untunneled traffic (kill-switch)" checkbox — turning it on prevents any traffic from leaving the machine if the tunnel drops. Recommended. - DNS leaks: Windows tends to leak DNS queries to non-VPN resolvers. Setting
DNS = 1.1.1.1, 9.9.9.9in the client config and enabling the kill-switch fixes this in practice. - Service mode: WireGuard installs as a Windows service — the tunnel can stay connected when the GUI is closed and during a user logoff.
macOS
Install: "WireGuard" from the Mac App Store.
Import:
- Click "+ → Import tunnel(s) from file."
- Pick the
.conf. - Click the toggle in the menu bar icon to activate.
macOS gotchas:
- System extension prompt the first time — approve in System Settings → Privacy & Security.
- DNS behavior is solid out of the box; the config's
DNS =value takes effect immediately. - On-Demand is available, similar to iOS.
Linux (CLI, systemd-based)
Install:
sudo apt install -y wireguard wireguard-tools # Debian/Ubuntu
# or
sudo dnf install -y wireguard-tools # Fedora
Import:
sudo cp client.conf /etc/wireguard/wg0.conf
sudo chmod 600 /etc/wireguard/wg0.conf
sudo wg-quick up wg0
sudo wg show # verify handshake
curl ifconfig.me # should report VPS IP
# Enable on boot
sudo systemctl enable wg-quick@wg0
Bring it down: sudo wg-quick down wg0.
Linux (GNOME / NetworkManager GUI)
- Install the NetworkManager plugin:
sudo apt install network-manager-l2tp-gnome network-manager-openvpn-gnome— and on newer distrosnetwork-manager-openconnect-gnomehandles WireGuard via the standard import dialog. - Settings → Network → "+" → import the
.conf. - Toggle the connection on.
Verifying everything actually works
- IP test: visit ifconfig.me before and after activating. The IP should change to the server's VPS IP.
- DNS leak test: visit
dnsleaktest.com(or any equivalent). The DNS resolvers shown should be the ones in your tunnel'sDNS =line, not your ISP's. - IPv6 leak test: if your tunnel only includes
0.0.0.0/0(not::/0), IPv6 traffic bypasses the VPN entirely. Either include both, or disable IPv6 on the client. - WebRTC leak test: use any "WebRTC leak test" page; if it reveals your local IP, your browser is leaking — disable WebRTC or use a hardened browser.
Reconnect and roaming
WireGuard handles network changes silently — switching from Wi-Fi to cellular doesn't require a manual reconnect. The first few packets after a change may drop until the handshake re-establishes (typically < 2 seconds). The PersistentKeepalive = 25 line in the client config keeps the tunnel alive through NAT timeouts.
Common client-side issues
"Handshake never completes"
Public key on the client doesn't match what's registered on the server, or the server endpoint IP/port is wrong, or UDP 51820 is blocked between client and server (corporate firewalls, some captive-portal Wi-Fi).
"Tunnel active but no internet"
The server-side NAT (iptables MASQUERADE) didn't get applied. Re-run sudo wg-quick down wg0 && sudo wg-quick up wg0 on the server, or restart the wg-easy container.
"Some sites work, others timeout"
MTU mismatch. The default WireGuard MTU is 1420; if your client's network has unusual MTU (mobile carriers, satellite, some VPN-over-VPN setups), packets get dropped. Add MTU = 1280 to the [Interface] block of the client config and try again.
"Tunnel disconnects after 5-10 minutes of idle"
NAT timeout on the client's network. Set PersistentKeepalive = 25 in the client's [Peer] block.
"DNS works but very slow"
The DNS server in your config is geographically far from the VPS. Change to one closer to the VPS, e.g. 9.9.9.9 (Quad9 has many anycast nodes) or set the VPS itself as the resolver (if you run one).
Need a VPS for the server side?
If you haven't already provisioned the server, the $3.49 Inferno plan handles a single-user VPN comfortably. Pick a location close to where you spend most time — latency adds up across every connection.
What to do next
- Split tunneling — route only specific apps through the VPN.
- Server-side install if you skipped ahead.
- wg-easy if hand-editing configs gets old.
- Best VPS for a personal VPN if you're picking a host.
Author: Hanna Wagner — Frankfurt. Last tested: 2026-05-22 on WireGuard iOS 1.0.16, macOS 1.0.16, Windows 0.5.3, Android 1.0.20231030, Ubuntu 22.04.