A subscription URL is not tied to one machine. The same link can go into your laptop, phone and tablet, each refreshing independently. Knowing that saves a lot of duplicated effort.
How a subscription works
It is just a web address that returns a list of servers. The client does three things: request the URL, parse the response, replace its own list.
So multi-device use is native: add the URL once per device. When servers change, each device picks it up on its next refresh.
Getting the URL onto a phone
| Method | How | Safety |
|---|---|---|
| QR code | Generate a QR on the computer, scan it with the phone | Never leaves your devices — safest |
| Local network transfer | Any LAN file/text transfer tool | Stays inside your network |
| Password manager | Store it as a secure note, synced across devices | Encrypted at rest |
| Message yourself | Chat app, saved messages | ⚠️ Passes through a server — avoid |
| Send to your own address | ⚠️ Stored in plaintext in your mailbox — avoid |
Why not share the config file?
- Port conflicts — different machines have different ports in use.
- Routing rules do not transfer — process rules from a desktop are meaningless on a phone.
- Platform differences — TUN and system proxy work completely differently per OS.
- Incompatible formats — desktop and mobile clients do not share a config structure.
Share the subscription, keep configuration local. Servers stay in sync while each device keeps its own settings.
How many devices can use one subscription?
- Concurrent connection limits — many plans cap simultaneous devices at three or so; extra connections displace older ones or fail.
- Refresh rate limits — hammering the subscription endpoint can get you throttled.
A sensible division of labour
| Device | Suggested setup | Why |
|---|---|---|
| Main computer | Full routing rules plus per-app routing | Most complex use — worth configuring carefully |
| Phone | Per-app routing, banking apps excluded | Saves quota and avoids fraud locks |
| Tablet | Simple global, toggled on demand | Used rarely; complexity is not worth it |
| TV / console | Via a computer on the LAN, or configured directly | Limited configuration capability on device |
There is no need to make every device identical — they are used differently, so they should be configured differently.