This article answers the question “How do I import nodes into v2rayNG?” It covers three import methods—clipboard, QR code, and subscription—and explains how teams can reduce login verification caused by changes to their exit IP. It is intended for Android users. Menu names may vary slightly between versions, so refer to the actual interface.
1. Before importing: Install the client and identify the link type
Download the Android installation package from the official v2rayNG project release page or another trusted source, and choose the version that matches your device architecture. If you’re unsure, check the release page for guidance. Don’t install modified versions from unknown sources in chat groups. The first time you connect, Android will ask to set up a VPN connection; you’ll need to allow it manually.
Before importing a node, distinguish between a single-node link and a subscription link. Links beginning with vless://, vmess://, or trojan:// are usually single-node share links. A subscription is generally an HTTPS address used to retrieve and update a set of configurations. Subscription addresses may contain access credentials, so don’t share them publicly or show them in screenshots.
2. Three import methods: Choose the one that suits your source
- Import from the clipboard: Copy the entire node share link, open v2rayNG, tap “+” in the upper-right corner, and select “Import from clipboard.” Check the list to confirm the new configuration appears. Make sure you haven’t also copied any explanatory text, quotation marks, or spaces.
- Import by scanning a QR code: Tap the QR code scanning option under “+” and grant camera access to scan the node’s QR code. If the image is saved on your device, check whether the scanning screen supports importing from your gallery. If not, ask the provider to send the original link.
- Add and update a subscription: Open “Subscription settings” in the side menu, add a subscription, enter a recognizable name, and paste in the subscription address. After saving, return to the main screen and select “Update subscription” from the menu. Saving the address alone usually won’t generate a node list automatically.
After importing, select a configuration and tap the connect button at the bottom. If this is your first time, test the connection before opening a browser to visit the intended website. Test results are only a guide and can’t guarantee that all apps will work normally. If the connection fails, try another configuration.
3. Team use: A successful import doesn’t guarantee a stable account environment
v2rayNG manages network proxying; it can’t guarantee that a third-party platform won’t trigger account verification. Account activity may also be affected by the device, browser cookies, login location, multi-factor authentication, and platform rules. Nodes with the same name or region don’t necessarily have a fixed exit IP, and the IP may change after a subscription update.
Teams should use clear configuration names that indicate the purpose and assignment date, and, where possible, keep commonly used devices and network environments consistent and compliant with platform rules. Avoid switching regions repeatedly during important operations. Prefer the platform’s member invitations and permission controls rather than sharing a password among multiple people. Free nodes may be suitable for learning or temporary testing, but shouldn’t be assumed to work for long-term account activity.
4. Troubleshooting import or connection issues
- No new configuration appears: Check that the link is complete and that the protocol is supported by your current version. Add subscription addresses in subscription settings, not as single-node links.
- Subscription update fails: Check whether the address has expired and confirm that your current network can reach the subscription service. Don’t submit the address to unfamiliar online conversion sites.
- The node appears but won’t connect: Make sure your phone’s time is set to sync automatically, close other VPN apps, and check whether the configuration is still valid.
- Some apps behave abnormally after connecting: Check routing and per-app proxy settings, and make sure the target app hasn’t been excluded. Record the original settings before making changes so you can restore them.
If the issue persists, you can ask for help by providing the client version, error message, and steps you’ve already tried. Be sure to hide subscription tokens, server credentials, and personal account information.