Getting Started
Make the first Tunna connection with a node, a simple route plan, and a clean safety check.
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.
What you need before setup
Start with the provider or server material in front of you. Tunna can import common proxy profile shapes, but it cannot guess private credentials or repair mismatched server settings.
- A provider profile, node link, QR code, subscription URL, Tunna share link, or manual server details.
- Protocol and credential values such as VLESS, VMess, Trojan, Shadowsocks, UUID, password, or method when your provider uses them.
- Transport and security values from the same profile, including WebSocket, gRPC, XHTTP, TLS, REALITY, SNI, ALPN, or fingerprint details when present.
- A simple first route plan, usually one selected node and a Default Route that is easy to verify before adding On-Demand automation.
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.
Use provider-compatible profiles
Import or create VLESS, VMess, Trojan, and Shadowsocks nodes when your provider gives compatible details.
Decide what uses the tunnel
Route by domains, IP ranges, ports, TCP or UDP, HTTP or TLS, and reusable GeoSite or GeoIP assets.
Start only when needed
Eligible Proxy domain and asset rules can let Apple start the tunnel when matching traffic appears.
Find a healthy node
RTT checks, latency dots, per-node stats, Active nodes, Top 10, and ZAP help you choose a usable node.
Keep provider lists current
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.
The three ideas behind Tunna
Use these cards as a map of the visible labels in this view. Each card names one field, control, or status item and explains what it is for before you change it or rely on it.
Everyday map
Use these three work areas as the stable map before opening deeper pages.
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.