How to Import Nodes in v2rayNG: Stability Settings for Team Use

This guide explains how to import nodes into v2rayNG and why, when multiple people share an account environment, some can connect while others experience instability. You’ll learn how to import individual nodes or subscription links into v2rayNG on Android, and how to improve stability with grouping, testing, and regular updates.

1. Check the node type before importing

v2rayNG supports common links such as VMess, VLESS, Trojan, and Shadowsocks, as well as subscription URLs. You don’t need to understand the technical details, but make sure you have a complete link or subscription URL. The free nodes on this site usually come with copyable links that are suitable for temporary testing. For long-term team use, subscriptions are recommended because they make it easier to keep everyone’s nodes up to date.

• Individual node: Usually starts with vmess://, vless://, trojan://, or ss://.
• Subscription link: Usually starts with http or https and returns a list of nodes when accessed.
• QR code: Scan it directly with v2rayNG to import the node.

2. How to import an individual node into v2rayNG

1. Install and open v2rayNG on your Android phone. If this is your first time using it, allow VPN permissions.
2. Copy the node link, return to the v2rayNG home screen, and tap “+” in the top-right corner.
3. Select “Import from clipboard.” Once the import succeeds, the new configuration will appear in the list.
4. Tap the node so that a check mark appears beside it.
5. Tap the circular button in the bottom-right corner to connect. A VPN icon in the status bar indicates that you’re connected.

To import a QR code, tap “+” and select “Scan QR code.” After importing, tap the menu in the top-right corner and run “Test all configurations for connectivity.” Don’t rely on latency alone—a low latency doesn’t guarantee that webpages will load.

3. Import a subscription link—recommended for teams

In a team setting, the most common issue isn’t not knowing how to import nodes; it’s that each person manually copies a different version, resulting in inconsistent setups. We recommend having an administrator compile the working nodes into a subscription so everyone can import them from the same URL.

1. Open v2rayNG, tap the menu in the top-left corner, and go to “Subscription group settings.”
2. Tap “+” in the top-right corner and enter a group name, such as “Office backup.”
3. Paste the subscription link into the address field and save.
4. Return to the home screen, tap the menu in the top-right corner, and select “Update subscriptions.”
5. Once the update is complete, select a working node and connect.

This way, when nodes change, you only need to update the subscription—team members don’t have to copy them manually each time. For account environments shared by multiple people, using the same subscription, updating it consistently, and testing it together is more reliable than importing nodes individually.

4. How account stability relates to the import method

Importing nodes into v2rayNG won’t improve the connection quality, but it can affect consistency across users. If someone on the team imports an expired node, uses the wrong protocol, or has an outdated subscription, the same account can perform very differently for different people. When using v2rayNG as a team, follow these three guidelines: don’t use nodes from unknown sources, update subscriptions regularly, and label working nodes clearly—for example, by region, purpose, or backup status.

Frequent node switching and having several people share the same free connection can also cause instability. The free nodes on this site are better suited to connectivity testing, temporary access, or backup use. We don’t recommend having every team member rely on the same free node.

5. Troubleshooting checklist

• No nodes appear after importing: Check that you copied the entire link, especially any parameters at the end.
• Connected, but webpages won’t load: Switch the routing mode or test for actual connectivity.
• Subscription update fails: Make sure the subscription URL is accessible, then try updating again on a different network.
• One team member can’t connect: Have them delete the old configuration and import it again from the same subscription.
• Frequent disconnections: Switch nodes and avoid having multiple people use the same connection at once.

Finally, keep at least two backup nodes after importing, and give each node a clear label. For teams, following a consistent import process matters more than finding one perfect node: it reduces back-and-forth and makes problems easier to diagnose.