This article explains how to import nodes into v2rayNG in practice. It covers three methods—links, QR codes, and subscriptions—and describes how teams can reduce account environment changes caused by accidentally switching routes. It is intended for Android users. Menu names may vary slightly between versions, so follow the labels in your app.
1. Install the client and identify the node format
Download the Android installation package from the official v2rayNG project release page or another trusted source, then install and open the app. Avoid modified versions from strangers, and do not grant permissions unrelated to proxy functionality. First, check whether you have a single node link, a node QR code, or a subscription URL.
Single node links often begin with vmess://, vless://, or trojan://. Subscription URLs usually begin with https:// and are used to fetch multiple configurations. Do not confuse node links with subscription URLs. Clash-specific YAML content cannot be imported directly as an ordinary node link; ask the provider for a compatible format.
2. Choose from three import methods
- Import from the clipboard: Copy the entire node link, return to v2rayNG, tap “+” in the upper-right corner, and select “Import from clipboard.” When the new configuration appears, check its name and server address. Make sure your copy does not include explanatory text, quotation marks, or extra line breaks.
- Scan a QR code: Tap the scan option under “+” and grant camera access when prompted, then point the camera at the entire QR code. If the code is on the same phone, check whether your version supports importing from an image. If not, display it on another device and scan it.
- Import via subscription: Open “Subscription settings” or a similarly named page from the side menu, add a subscription, enter a descriptive label, and paste the subscription URL. Save it, return to the main screen, and select “Update subscription” or “Update current group subscription.” A subscription appearing in the list does not mean its nodes have finished downloading.
After importing, check that the configuration appears in the list. You can add clear labels to frequently used nodes, such as their purpose and route name, so team members do not pick the wrong configuration based on similar names alone. When using free nodes from this site or elsewhere, check the format and last-updated time; actual connectivity determines whether they work.
3. Connect and verify—don’t rely only on test results
Select the node you want to use, then tap the connect button. The first time you connect, Android will display a VPN connection request. Once you confirm, a VPN icon will usually appear in the status bar. This uses the system VPN interface; it does not mean the node protocol itself is a traditional VPN.
After connecting, open a browser and visit the target website to confirm that it loads correctly. Latency and connectivity tests can help, but they do not guarantee that every app will work. If the browser works but a particular app does not, check whether the app is excluded from per-app proxy settings or whether routing rules are sending its traffic directly.
4. Troubleshoot import or connection issues
- Format error: Copy the original link again and check that its beginning is present, that it has not been truncated, and that you have not used a subscription URL by mistake.
- Subscription update failed: Check that the URL is complete and has not expired, and confirm that your current network can reach the subscription service. Do not submit private subscription URLs to unfamiliar online conversion sites.
- Configuration is present but there is no internet access: Test both Wi-Fi and mobile data, check your phone’s date and time, pause other VPN apps, and look in the logs for timeouts or authentication errors.
5. Team use and account environment stability
A successful import does not guarantee a stable account environment. Teams should agree on which devices and routes to use for each account and establish a consistent switching process. Avoid sharing accounts among multiple people or logging in frequently from different regions. The exit route may change after a subscription update, and nodes with the same name may not use the same exit IP. Confirm the route before important actions, and follow the platform’s official process if verification is required. Do not share nodes or subscription URLs in public groups, and do not treat a proxy as a guarantee against account risk controls.