When comparing VPNs for multiple devices, the key issue is not just the device count shown on the plan page. Limits may be based on logins, active connections, or client authorizations. Family sharing also involves subscription imports, concurrent connections, protocol compatibility, and split-tunneling differences. Confirm how devices are counted first, then check whether members can use the service at the same time without disconnecting one another.
Many household device lists look simple: a daily computer, a personal device, a tablet, and living-room equipment may each need a connection, while older devices may still retain the client. In practice, operating-system reinstalls, duplicate client installations, and protocol changes can leave old authorization records behind. A vague claim of “support for multiple devices” is not enough to judge whether a service is suitable for long-term sharing.
What exactly does the device limit count?
The device count mentioned by a provider may refer to entirely different technical objects. Common approaches include recording clients that have logged in, limiting simultaneous sessions, or generating a separate authorization for each import. The first can be affected by device changes and reinstalls; concurrency limits usually allow installation on more devices but do not allow them all to connect at once.
You also need to distinguish between signing in to a dashboard and establishing a proxy connection. Opening an account page in a browser is an administrative action. Only after a client starts a Shadowsocks, VMess, Trojan, VLESS, Hysteria2, or TUIC session does it consume route resources. Some products count both client identifiers and sessions, so signing out of the dashboard may not release authorization; old records may need to be removed in device management.
Does connecting through a router count as one device?
From a network-architecture perspective, a router can establish one upstream connection for downstream devices, allowing living-room equipment and household devices to share the same gateway over the local network. However, counting still depends on the provider’s plan rules; do not assume that devices behind the router are unrestricted. The main benefit of a router setup is centralized configuration, not avoiding device policies.
Centralized connectivity also has trade-offs. When everyone shares one route, a high-bandwidth task on one device can affect others’ interactive use. Insufficient router performance can also make complex encryption and UDP traffic a bottleneck. If family members often use different networks, running the client separately on each device is usually more convenient.
How do capped-device plans compare with unlimited-device plans?
Testing a multi-device plan should not rely on a single speed-test screenshot. A more useful approach is to repeatedly switch networks in a real household setting, connect different operating systems at the same time, refresh the subscription, and observe whether older sessions are interrupted. Because the egress region, access provider, and test period all affect results, this article avoids context-free latency figures and compares repeatable behavior instead.
| Comparison criteria | Fixed device limit | Concurrent connection limit | Unlimited-device plan |
|---|---|---|---|
| Device changes and reinstalls | Old authorization may need to be deleted | Usually does not affect installation records | No need to manage device slots |
| Members online at the same time | Depends on authorized devices | New connections may be refused after the concurrency limit is reached | Better suited to shared use across members |
| Temporary devices | May occupy a long-term device slot | The session is usually released after disconnection | Fewer management steps |
| Troubleshooting | Check the authorization list first | Check sessions that are still online first | Focus on route, protocol, and traffic status |
| Household maintenance cost | Requires ongoing device cleanup | Requires coordinating online times | Members can choose routes for their own use cases |
Unlimited devices does not mean every device must use the same node, nor does it guarantee identical speeds in every network environment. It reduces friction around authorization and concurrency management. Actual speed still depends on local access, route load, egress quality, the destination, and the selected protocol.
The right way to configure family sharing
The most common family-sharing mistake is not installing the client; it is forwarding a subscription link as casually as an ordinary webpage URL. A subscription URL can usually retrieve node names, server addresses, ports, and connection credentials, so it should be treated as sensitive configuration. If a member leaves the sharing group or the link is exposed, update the subscription credentials in the dashboard and have remaining users import the subscription again.
A safer approach is for one account administrator to maintain the plan and subscription status, while each member imports it only on their own device. Do not have multiple people change the dashboard password, delete routes, or reset settings at the same time; otherwise it becomes difficult to tell whether a connection failure comes from the network or an account-setting change.
- ✅ Copy the current subscription URL from the user dashboard instead of importing an old link from a chat history.
- ✅ Label each subscription clearly in the client, such as household computer, personal device, or living-room device.
- ✅ After importing, refresh the node list, then choose a region and route that match the destination.
- ✅ Set direct-connection rules for local services so that not all traffic is sent through international routes.
- ✅ When handing a device to someone else or retiring it, delete the local subscription and update the shared credentials.
- ❌ Do not publish subscription QR codes, configuration files, or troubleshooting screenshots containing connection parameters.
How clients differ across platforms
Windows and macOS clients typically let you choose between system proxy and TUN mode. A system proxy mainly takes over apps that follow proxy settings, while TUN mode can cover more programs that do not read the system proxy. After switching modes, check local-network access, DNS resolution, and application split-tunneling behavior again.
Android and iOS typically use the system-provided VPN interface to handle traffic, but background policies, battery-saving settings, and network changes can pause the connection. Whether a TV box can install a client directly depends on its system and app compatibility. If it cannot run one natively, consider using a router for the connection and defining explicit rules for streaming and local services.
On Linux, it is more common to run a core program with a configuration file or command line. Before importing, confirm that the client supports the relevant protocol and subscription format. A visible node name does not prove protocol compatibility. Unsupported fields may be ignored, leaving the node listed but unable to connect.
How protocol choice and route type affect multi-device use
Shadowsocks is simple to configure and supported by many clients, but whether it proxies every app depends on the system proxy, TUN, and routing rules. VMess and VLESS are often used with different transport layers, so the client must correctly recognize the transport, security, and domain parameters. Trojan typically runs over a TLS connection; an incorrect system clock or certificate-related parameter can cause the handshake to fail.
Hysteria2 and TUIC mainly use modern UDP-based transport and have their own scheduling characteristics on unstable networks, provided the current access network permits the relevant UDP traffic. If a member’s network restricts UDP, the client may keep reconnecting. Switch to a node or protocol compatible with that network instead of repeatedly importing the same subscription.
Route structure matters as well. Direct connection means traffic follows a public-network path from the user’s access network to the egress, so it can be strongly affected by carrier interconnection and routing changes. A relay route first connects to a relay entry point and then moves on to the egress, which can improve some cross-network paths. An IEPL private line usually refers to a dedicated link or bearer segment in a cross-border path, but it does not mean every segment between the user’s device and the destination website is outside the public internet.
Family members with different destinations do not need to use the same node. Remote collaboration, web browsing, streaming, and software updates have different route requirements. One practical advantage of an unlimited-device plan is that each device can choose a route for its own destination instead of sharing one connection to conserve concurrency slots.
DNS leaks and split-tunneling rules must be checked together
A successful connection icon only shows that the client established a tunnel or proxy session; it does not prove that every request is taking the intended path. A DNS leak generally means that domain-resolution requests are still being sent to a local resolver that does not match the current policy, making the DNS and web-traffic paths inconsistent. This can affect region detection and cause split-tunneling rules to match incorrectly.
When testing, first confirm whether the client uses remote DNS, local DNS, or rule-based resolution. Then visit a trusted DNS test page and check whether the resolver region matches your settings. If the browser has its own encrypted DNS enabled, it may bypass the client’s default policy. Configure both consistently for your needs instead of treating multiple resolvers as automatic proof of a failed connection.
The purpose of split tunneling is to send requests that need acceleration through the proxy while keeping local websites, LAN addresses, and services that should retain their local egress on a direct connection. Rules may match by domain, IP, application, or rule set. Domain rules depend on correct resolution, while IP rules must account for changing destination addresses, so subscriptions and rule sets should be updated regularly.
- ✅ After connecting, confirm the egress region first, then check the DNS resolution path.
- ✅ Test whether LAN printers, file shares, and the router administration page remain accessible.
- ✅ Open services that should use a direct connection and those that should use the proxy separately, then verify the matched rules.
- ✅ After switching from home broadband to a mobile network, check the connection and resolution status again.
- ❌ Do not treat “a webpage opens in global mode” as proof that split tunneling is configured correctly.
What happens after exceeding the device limit?
Over-limit behavior varies by service. A fixed-device authorization may reject a new device login outright or require an old device to be deleted from the dashboard. A concurrency limit may appear as a failed handshake for a new connection, replacement of an existing connection, or a connection that drops shortly after succeeding. Some clients continue to display the node list while requests fail, which can easily be mistaken for a route problem.
When troubleshooting, check account status and device management before changing protocols. If an old device is powered off but its session is still retained by the server, terminate the session in the dashboard or wait for it to expire naturally. If there is no device-management entry, review the plan details and contact support to confirm whether the limit is based on authorized devices or simultaneous connections.
If the same subscription works on one platform but not another, the issue is more likely to involve client compatibility, protocol parameters, or system network permissions. If all devices fail around the same time, check the subscription status, traffic status, and route announcements. Separating these cases helps avoid repeatedly reinstalling the client without addressing the real cause.
How to choose the right VPN for multiple devices for your family
Make the final choice based on management effort, concurrent use, and client coverage. List the device types that will be used long term, then confirm whether members will connect from different locations at the same time. With fixed authorization, also check how device changes, reinstalls, and releasing old devices are handled. With concurrency-only limits, consider how often members’ usage overlaps.
Also check whether clients support the protocols, subscription imports, and rule modes you need. A product with a client for only one operating system may not cover living-room equipment or other desktop systems, even with ample slots. Conversely, a feature-rich client combined with strict device limits can force family members to coordinate login status over the long term.
87VPN uses an unlimited-device plan, making it suitable for families that need to import subscriptions on different types of devices and choose routes independently for each destination. Unlimited devices solves device authorization and sharing-management issues; connection quality should still be assessed separately based on the local network, destination region, route type, and protocol compatibility.