This article explains exactly how to import nodes into v2rayNG. It covers three methods—clipboard, QR code, and subscription—and explains how teams can reduce account verification caused by frequent changes to their exit IP. A successful import does not guarantee a working connection, or a stable account environment. Check the node, routing, and login devices separately.
1. Before importing: Check the client and link type
On an Android phone, install the client from the v2rayNG project’s official releases page or another trusted source. Avoid modified versions from unknown sources. The installation file should match your device architecture; if you’re unsure, check the release notes. When you first enable a connection, Android will prompt you to authorize the system VPN. Verify that the app is the one you intended to use, then grant permission.
Node links typically start with vmess://, vless://, trojan://, or a similar prefix. A subscription is usually an HTTPS URL that can contain multiple configurations. Import node links and subscription URLs through their respective options; don’t copy account credentials, webpage URLs, or explanatory text along with them.
2. Three ways to import: Choose based on what you have
- Import a single node from the clipboard: Copy the entire share link, open v2rayNG, tap “+” in the upper-right corner, and select “Import config from clipboard.” Return to the list and confirm that the new configuration appears, then select it. Menu names may vary slightly between versions.
- Scan a QR code: Tap the scan option under “+”, grant camera access, and scan the node’s QR code. If the code is saved on your phone, check whether the scan screen lets you load it from your gallery. If there’s no such option, display the QR code on another device or ask the provider for the share link.
- Add and update a subscription: Open “Subscription group settings” in the side menu, or a similarly named option. Create a group, enter a recognizable label and the full subscription URL, then save it. Return to the main screen, select “Update subscription” from the menu, and choose one of the nodes that loads.
Once you’ve selected a node, tap the connect button and confirm the system authorization prompt, then test by opening a webpage. You can start with the in-app connection test for reference, but its results don’t necessarily reflect how every website will perform. Free nodes offered on this site can also be imported using the published link format; availability depends on the results of tests at the time.
3. Team use: Import method doesn’t determine account stability
Clipboard, QR code, and subscription are simply ways to add configurations to the client. Account environments are influenced more by exit IP, region, device, and login behavior; changing the import method won’t resolve these factors. Teams can agree to use relatively consistent nodes and routing modes, and avoid logging into the same account from different regions in quick succession. Prefer member accounts and permission features supported by the platform instead of sharing a primary account.
Free nodes may change their exit IP or availability, so they can’t guarantee a fixed exit. Subscription URLs may contain access credentials and should be treated as sensitive information. Don’t post them in public groups or share screenshots of them. When a member leaves, revoke or replace their access using a method supported by the provider.
4. Import fails or connection doesn’t work: Check these in order
- Format error: Copy the entire link again, removing line breaks, spaces, and Chinese punctuation. Confirm that your version supports the protocol.
- Subscription update fails: Check whether the URL has expired, whether your network can access the subscription source, and whether the provider requires specific update conditions.
- Webpages won’t load after connecting: Test another node for comparison, check that your system time is set to update automatically, and pause other VPN apps to avoid conflicts.
- Only some apps have issues: Check per-app proxy settings, bypass rules, and routing mode to confirm the target app is actually using the proxy. If the issue persists, check the logs; redact addresses, UUIDs, and tokens before sharing them.
When troubleshooting, change only one setting at a time and record the result. If account verification issues persist after the node is working again, follow the platform’s verification instructions. Don’t assume every login issue is caused by v2rayNG.