VPNClip Help Center

No email address is required. Create an account with a username and password. Use a unique password and keep your username safe. After submitting, make sure you can sign in to the user panel before choosing a plan. Account credentials and subscription links serve different purposes: credentials manage your account and orders, while subscription links let the client retrieve routes. Never post either in public discussions. If you have trouble signing in, check your keyboard input, letter case and any outdated information autofilled by your browser. For help, see the support instructions on the customer service page, and never include your password in a support request.

There is no limit on the number of devices that can be online at the same time, so you don't need to choose a new plan just because you changed devices. On the new device, open the user panel, download the client for your platform, then import the subscription linked to your account. Device limits and data allowances are different: unlimited devices does not mean unlimited data. Check your plan balance and billing terms before use. When handing off or retiring an old device, remove saved subscriptions and sign-in sessions so your account details aren't left somewhere others can access. Import options may have different names on different systems; follow the client’s current interface.

Sign in to the user panel to get your subscription, then add it using the client’s subscription import feature. To update routes, refresh the existing subscription configuration and check for a success message; there’s no need to repeatedly create the same configuration. If the subscription address in the panel changes, replace the old address in the client and refresh again. Then confirm the updated configuration is active. If an update fails, first check whether your local network can open the panel. Don’t mistake the sign-in page address for a subscription link. Subscription links contain access credentials, so fully obscure them in screenshots before sharing.

Clients are available for Windows / macOS / iOS / Android / Linux, all through the user panel. After signing in, you can download clients for Windows, macOS, Android and Linux; iOS download availability depends on whether the panel detects an active plan. Downloading a client and getting a working subscription are separate steps. After installation, sign in to the panel, get your subscription and import it. Choose the option for your operating system and follow the on-screen instructions to install the client and grant permissions. Don’t apply setup steps for another system to your device, and don’t download installation files attached to public comments.

First check your order status, current plan and remaining data in the user panel, then return to the client and refresh the subscription. The client may still be showing a previously imported configuration; simply closing the window may not refresh its contents. Once the update succeeds, make sure the correct configuration is selected and reconnect. If the panel also hasn’t updated to reflect your order, keep the order record and open a support ticket with your payment method, order status and a description of what happened. Don’t pay again or switch between accounts while troubleshooting, as this can make it harder to identify which account owns the order.

Disconnect and confirm your local network can access everyday websites, then check your plan status and remaining data in the user panel. Next, refresh your subscription, choose a route again and make sure the system proxy or required traffic-capture mode is enabled. A connected status usually means the client has established a connection; it doesn’t mean every app’s traffic is using that route. Test the browser and target app separately to see whether the issue affects everything or just one service. If only one site is affected, check its service status, account region requirements and routing rules. Don’t reinstall your operating system as a first step.

Apps can use different networking methods. Some don’t follow the system proxy, and others may keep a connection established before you changed routes. First check whether the client is using split tunneling or global proxy, and whether a rule is sending the app directly. Save your settings, fully quit the app and reopen it so an old connection doesn’t affect your test. If the client offers system-level traffic capture, follow the platform guide to check permissions and supported use cases. Don’t run multiple traffic-capture tools at once. Workplace apps may also be subject to organizational network policies, so check their requirements first.

Sign in to the user panel to get the subscription again. Make sure you copy the full address—not a page title, sign-in link or text truncated by a messaging app. Check that your client supports the import method, and note any error shown during the update. If the list is still empty, check your plan status in the panel and try updating from a network that’s working normally. Don’t delete existing configurations without a reason; first note the error and client name for reference. You can attach a screenshot to a support ticket after obscuring sensitive information, but remove the full subscription address, account credentials and other personal details.

Your existing connection may stop working after you switch networks. Disconnect the client, then reconnect on the new network. If other devices work but this one doesn’t, first check its proxy settings, system permissions and any conflicts with other network tools. Pause other proxy tools before testing to avoid multiple apps capturing the same traffic. Check that the system date and time are correct, and see whether you need to complete a network sign-in page first. Change and record one relevant setting at a time to help tell whether the issue is with the local network, client configuration or route.

Include your device’s operating system, client name, route, network environment, when the error occurred and the affected app. Describe the steps that reproduce it—for example, whether a subscription update fails, the connection won’t establish, or only one app is inaccessible after connecting. Include the exact error message and troubleshooting steps you’ve already tried to reduce back-and-forth. If a screenshot shows a subscription address, username or order payment details, obscure them first. Don’t send passwords or complete subscription links. If further diagnosis is needed, provide the checked information requested in the ticket instructions.

Route types describe connection paths; the name alone can’t tell you how a route will perform on your device. IEPL is suited to scenarios where cross-border route stability is a priority. A relay forwards traffic from an entry point to an exit, so performance also depends on both the entry and onward paths. Direct routes rely more on public network conditions between your local network and the exit. Compare connection stability, page loading and session recovery with the same app in similar conditions before choosing a route for regular use. Meetings, browsing and file transfers have different needs, so you don’t have to use the same path for every app. A route name is not a speed guarantee.

Pause large file transfers and cloud sync on your device, then see whether your local network is also slow. Keep the target app the same while comparing different entry points or route types; changing your device, network and app at once makes results hard to compare. If all routes are affected, try another local network. If only one route is affected, note its name and when the issue occurred, then submit a support ticket. Video quality and background tasks can also affect performance, so keep test conditions similar. Don’t conclude that an entire route type is unsuitable based on one loading test.

Check the target service’s supported regions and account requirements, then test the matching exit. AI websites, API calls and streaming services have different requirements: opening a website doesn’t mean its API or all its content will be available. Try to keep the same exit during use, since frequent region changes can affect how a service evaluates your session. Streaming availability can also change with account settings, licensing regions and service policies. A route name doesn’t guarantee access to a particular catalog. If something doesn’t work, distinguish between a network error, an account permission notice and a restriction from the service.

VPNClip covers 120+ countries and offers 230+ routes. These figures describe the range of regions and routes available; they don’t mean every region has identical paths, app compatibility or access performance. When choosing a route, check the current list in the user panel, the target service’s region requirements and your local network—not just the country name. Start with a region you use regularly, then adjust for a specific service if needed. Route descriptions on promotional pages explain the route types. Before connecting, refresh your subscription and use the options currently shown in your client.

Split tunneling uses rules to send different requests either direct or through a proxy. Global proxy typically sends requests captured by the client through the selected proxy. “Global” doesn’t automatically mean every app on the device is captured; the actual scope depends on system permissions, client features and how each app handles networking. For everyday use, start with split tunneling as described in the platform guide. If an app has a problem, check which rule applies and use global proxy to help determine whether the rule is the cause. When troubleshooting is done, restore settings that suit your normal use, so traffic that can connect directly doesn’t stay on an unnecessary cross-border route.

Monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB and ¥28/month for 500GB. Data resets monthly on the date your plan starts, not at the beginning of each calendar month. Before choosing a plan, consider the apps you use and check your data usage in the panel; the number of devices alone doesn’t indicate how much data you need. If the client still shows old data information, check the user panel first, then refresh your subscription. Don’t treat the client’s own transfer statistics as the same thing as your plan balance in the panel. If they differ, ask support to check.

Data packages are ¥158 for 300GB, ¥358 for 1000GB and ¥658 for 3000GB. They last until the data is used and never expire. Monthly plan data resets each month on the plan’s start date. The main difference is how billing and data usage work: a data package doesn’t add the same allowance every month. If your usage varies, compare options based on your actual consumption. For regular use, consider whether the monthly allowance fits your needs. Check the panel to confirm how a new order relates to an existing plan; don’t assume there are stacking, rollover or credit rules unless the page says so.

The price difference for a mid-cycle upgrade is converted into remaining days. Before upgrading, check your current plan, the tier you’re considering and the order confirmation details in the user panel. Don’t assume the amount due is simply the difference between the two listed prices, or make assumptions about how the upgrade affects data or the start date. If the order page doesn’t match your expectations, stop before making another payment. Open a support ticket with your current plan and intended upgrade so support can check the details. Keep the order record for reference; creating or paying for duplicate orders can make your account status harder to review.

Alipay / WeChat Pay / USDT are supported. Pay through the order checkout in the user panel, following the information shown on that page for your order. If the order hasn’t updated after payment, return to the order page and check its status, account and order details. Don’t pay again just because the page hasn’t changed yet. If you need help, provide the order record and a redacted payment receipt in a support ticket, and describe the payment method and what happened. Don’t share full payment details publicly or follow unsolicited messages asking you to change payment information. Use the details on the current order page.

VPNClip offers a 60-day no-questions-asked refund policy. To request a refund, sign in to the user panel, open a support ticket, state that you’d like a refund and include the relevant order record. See the Terms of Service for the applicable terms. You don’t need to keep switching routes or place another order to start a request. If you’re also experiencing connection issues, you can include details in the ticket, but clearly state that you’re requesting a refund. Follow up in the same ticket to keep the conversation together. The ticket response will confirm the refund status and any information needed. No additional processing time is promised on this page, and you don’t need to share payment details in public comments.