Basics

Getting Started

Make the first Tunna connection with a node, a simple route plan, and a clean safety check.

Updated 2026-06-02

Tunna is a proxy tunnel app for iPhone, iPad, and Mac. It does not sell servers or accounts. You bring a provider profile, a QR code, a node link, a subscription URL, or your own server details; Tunna gives you the place to import them, choose a node, decide how traffic should be routed, and start the tunnel.

Main features

Tunna brings Xray-powered, V2Ray-compatible profiles together with privacy, routing, health, and subscription tools.

Bring your own proxy

Tunna is a client for your provider or server. The app does not collect data.

Xray and V2Ray profiles

Import or create VLESS, VMess, Trojan, and Shadowsocks nodes when your provider gives compatible details.

Granular routing

Route by domains, IP ranges, ports, TCP or UDP, HTTP or TLS, and reusable GeoSite or GeoIP assets.

On-Demand startup

Eligible Proxy domain and asset rules can let Apple start the tunnel when matching traffic appears.

RTT, stats, and ZAP

RTT checks, latency dots, per-node stats, Active nodes, Top 10, and ZAP help you choose a usable node.

Subscriptions and live edits

Subscriptions manage long node lists, rules can bind traffic to different nodes, and many edits apply without making restarts the normal workflow.

Start with real provider details

A working setup begins with a node, subscription URL, QR code, or manual server details. If you do not have one yet, get it from your provider or from the server you operate before configuring Tunna.

A first connection has five quiet stages

Move slowly the first time. A warmed node and a simple routing plan are easier to diagnose than a busy setup with many rules.

Bring in a node

Create a manual node, scan a QR code, paste a provider link, paste a subscription URL, or accept shared resources from another Tunna device.
Review Resources

When Tunna opens Resources, review nodes, rules, subscriptions, duplicate warnings, and any fetch status before importing.
Let subscriptions settle

Managed lists may need time to fetch nodes, usage, expiry, and support details.
Warm health checks

Leave Tunna open briefly so latency results can guide sorting, ZAP, and node status.
Choose the node

Select one local node or one subscription node before starting the tunnel.
Start manually

Use the power control. On the first tap, Tunna installs its Apple Network Extension entry and the system may ask for VPN permission before the tunnel can start.

The first Power tap installs the Apple Network Extension

Tunna cannot carry traffic until iOS or macOS has a VPN configuration for its Network Extension. The first Power tap creates that system entry. After you approve it, later Power taps start and stop the existing tunnel.

The three ideas behind Tunna

Outbound is the server shelf

This is where local nodes and subscription nodes live. Add them, name them, check RTT, inspect stats, share them, use ZAP, and choose the current one.

Routing is the traffic decision

This is where matching traffic uses Proxy, Freedom, Blackhole, or a specific node. Rule order matters: first match wins.

Settings shape the behavior

This is where you tune tunnel startup, trusted networks, subscriptions, assets, checks, logs, shortcuts, support, and resets.

Before pressing power

At least one local node or subscription node is visible in Outbound.
The node details still match the provider profile: protocol, transport, security, address, port, and credentials.
The Default Route is simple for the first test, usually Proxy.
The current network is available if a subscription or asset must update first.
Trusted Networks will not immediately stop the tunnel on the Wi-Fi or cellular network you are using.

Treat node material like a password

Node links, QR codes, subscription URLs, Tunna share links, Reality keys, UUIDs, and passwords can let another device use your server. Share them only with people and devices you trust.