The most common misconception in multi-device VPN advice is treating the device count as a tier you have to pick. Under VPNTA's rules the number of devices is unlimited: one account can sign in on Windows, macOS, iOS, Android and Linux. What actually needs working out is the data allowance, and how a family sharing one account handles the subscription link. Below we take the three questions apart: how device counts work, what a household runs into when sharing one account, and how to choose between a monthly plan and a data pack with several devices online, plus a comparison method anyone can repeat.
Device count explained: account, data and concurrency
Break "how many devices can one account sign in on" into its parts and you find three different rule layers. Judge them as one and you easily reach the wrong conclusion: more devices means a pricier tier.
- Account layer: no device limit. Add a phone or laptop at home and you simply sign in on the same account, with no extra seat to buy and no effect on devices already online.
- Allowance layer: every device draws on one shared data pool. A phone streaming video, a laptop uploading files, a tablet updating in the background, all of it comes out of the same allowance.
- Connection layer: simultaneous devices add up. The more devices online at once and the longer they stay online, the faster the allowance drains. This has nothing to do with which plan tier you are on, only with actual usage.
When devices share an account, consistent configuration matters more than the protocol
Devices in one household often run different clients: some pull node lists automatically from a subscription link, others need the route picked by hand. At the protocol level, VLESS, VMess, Trojan, Hysteria2, TUIC and Shadowsocks all import into the mainstream clients; the differences come down to transport and congestion control. For a multi-device household, two things are worth standardising: split-tunnelling rules and DNS settings.
Split-tunnelling rules decide which domains go over international routes and which connect directly. With mismatched rules, the same video may go through the proxy on a phone and direct on a laptop, and the gap in experience is easily mistaken for a problem with the route. When troubleshooting, align the rules on both devices first, then judge the route.
A DNS leak means domain lookups do not follow the proxy but go back to the local network resolver. Two things follow: the queries are exposed to the local DNS, and you may be handed a CDN node chosen for your local location, which shows up as "connected but slow to load". A public DNS leak test page showing where the resolver sits is enough to confirm whether the client is routing DNS through the proxy as well.
Direct, relay and IEPL routes compared
Route type decides how stable the evening peak is. Direct means the client connects straight to the exit server: the shortest path, but jitter is obvious when the public internet is congested. Relay connects to an entry node first and forwards from there to the exit: a controllable path with one extra hop. IEPL runs over carrier-grade international Ethernet, so traffic from entry to exit never touches the public internet and evening-peak jitter is usually lower. When several devices are online and competing for bandwidth, the difference gets amplified. The full route list can be filtered by region and route type on the servers page.
Can a family share one account?
Short answer: yes. There is no device limit, so everyone's phone, tablet and laptop at home can sit under one account. Signing up needs only a username and password, with no email address required, and opening separate accounts for family members just means more credentials to keep track of.
Three things to settle before you share
- How the data is split. Start with who uses it hardest. A device streaming video for hours burns far more than a phone that only sends messages, so budgeting around the heavy devices is more realistic than dividing evenly.
- How the subscription link is handled. The subscription link works like an account credential: anyone who has it can import and use it. Pass it around once inside the household and never post it in group chats or public forums.
- How the clients are aligned. Keep household devices on the same split-tunnelling rules and DNS settings where you can. Fewer variables make it much easier to tell whether a problem sits with the device or the route.
What over limit actually means: devices, data and concurrency
People searching for "multi-device VPN over limit" usually worry about two things: too many devices getting kicked offline, or the account dying once the allowance runs out. Under the current rules these two behave completely differently and deserve separate treatment.
| Type | Does it happen | What you see and what to do |
|---|---|---|
| Device count exceeded | No | No device limit: a new device just signs in on the same account |
| Monthly plan data used up | Yes | Data resets monthly on your activation date; you can also upgrade mid-cycle, with the price difference prorated over the remaining days |
| Data pack used up | Yes | Runs until it is used up and never expires; buy another pack when you need one |
| Several devices online at once | Yes | Traffic from each device adds up; how fast the allowance drains depends on how many devices are online and how hard they are used |
Note: monthly plan data resets each month on your activation date, which is not the 1st of the calendar month. Writing that date down beats guessing at month end how much allowance is left.
Since device count is unlimited, in a multi-device setup "over limit" really comes down to one variable: data. Watching your usage is more useful than watching the device list.
Monthly plan or data pack: how to choose with several devices
With several devices, whether you pick a monthly plan or a data pack depends on how steady your usage is, not on how many devices you own. Device count is unlimited, so "we have a lot of devices at home" is not on its own a reason to upgrade; what drains the allowance faster is how many devices are online at once and how hard they are used.
| Aspect | Monthly plan | Data pack |
|---|---|---|
| Price and allowance | ¥9.9/month for 60GB; ¥18/month for 250GB; ¥28/month for 500GB | ¥158/300GB;¥358/1000GB;¥658/3000GB |
| Validity | Resets monthly on your activation date | Lasts until used up, never expires |
| Best multi-device fit | Household devices online long term, steady usage | Short bursts of heavy use, rotating devices, irregular usage |
| When the allowance runs short | Upgrade mid-cycle; the difference is prorated over the remaining days | Buy another pack; unused data does not expire |
| Device count | Unlimited | Unlimited |
Matching them to scenarios makes it clearer:
- Always-on devices: go monthly. Phones, tablets and laptops connected year-round with steady usage suit a plan whose allowance resets every month, so there is no running total to watch. A household built on messaging, web pages and music can start on the ¥9.9/month 60GB tier; if video and several devices at once are part of the picture, look at ¥18/month for 250GB or ¥28/month for 500GB.
- Short bursts: go with a data pack. Holidays, business trips and short projects concentrate usage into a few days, and paying for a full month does not add up. A data pack lasts until it is used up and never expires, so whatever is left carries over to next time.
- Not sure? Run the test first. A full refund, no questions asked, can be requested within 14 days of your first payment. Start on one tier, work through the process in the next section, then decide whether to upgrade mid-cycle. The full tier list is on the pricing page.
A repeatable test: four steps to real multi-device numbers
None of the steps below need specialist tools. Same account, same time window, same set of devices: rerun with a different route and the results compare side by side. The key is running the same actions every time.
-
Import the subscription on every device
Paste the subscription link into the client (it looks like
https://example.com/sub?token=xxxx), refresh the node list, then select the route you want to test by hand. Importing a subscription does not switch anything automatically, so check that the route you intend to test is the one selected; for the details, see the Guides. -
Fix the test window and the device set
Pick the evening peak (roughly 20:00 to 23:00) and a fixed set of devices; one laptop and one phone is enough. Only results taken under those two conditions can be compared.
-
Run the same actions on each device
Open the same web page, play the same video, start one file upload. Record three things: whether it opened, roughly how long the first screen took, and whether it stalled partway. A vague note that it felt fast or slow gives you nothing to compare later.
-
Switch routes, rerun, and log what failed
Work through nodes in different regions, noting the route type each one is labelled with (direct, relay, IEPL), and repeat step 3. Which route holds up best at the evening peak, and which fails most often on your home connection: write it down and you have your own comparison table.
Tip: run the test again with the client handing DNS to the proxy as well. When DNS goes through the local resolver, load times on the same route swing noticeably and are easily misread as an unstable route.
Common mistakes with multi-device use
- ✅ No device limit: a new device simply signs in on the same account, with no extra seat to buy.
- ✅ Data packs last until used up and never expire, so short bursts of heavy use do not have to fear a month-end reset.
- ❌ Posting the subscription link in a family group chat or a public forum: the link works as an account credential, and anyone who has it can import it.
- ❌ Choosing a plan on device count alone: the allowance is measured in data and has nothing to do with how many devices you have.
- ❌ Changing clients without checking DNS: with split-tunnelling rules and DNS out of step, lookups can land on a local CDN and speeds swing up and down.