Site terms
Terms of Use
Last updated: September 2026
This page explains the terms that apply to the content, download entries and configuration references on V2Ray Desktop Edition. By accessing or using this site, you confirm that you have read and agree to the terms below.
1. Content scope and applicability
This site is aimed at users who want to learn about clients in the V2Ray ecosystem. It provides an index of download entries for three clients, v2rayN, v2rayNG and v2flyNG, along with configuration steps for Windows, macOS, Android and Linux and reference material on JSON configuration files. All content is intended for technical learning and software use reference, and does not constitute any quality guarantee for any network service, node or subscription.
This site only compiles client download entries and writes documentation. It does not run nodes and does not provide subscription services. The configuration snippets, field names and rule syntax in the examples are there to show how things are written; actual values must be filled in according to your own subscription details.
2. Lawful use requirements
When using the content on this site and the related clients, you must comply with the laws and regulations of your country or region, as well as the terms of the network service provider you use. The clients and the documentation on this site must not be used for any unlawful purpose, including accessing other people's systems without authorization, disrupting the normal operation of networks, infringing the lawful rights of others, or distributing malicious software. The documentation here only describes general client configuration methods and does not offer circumvention solutions for any specific network environment. Whether to use them, how to use them, and any consequences that follow are for the user to judge and bear.
Note
The clients are general-purpose network tools. Whether a given use case is lawful is for the user to judge; this site does not endorse any specific use.
3. Disclaimer
Clients such as v2rayN, v2rayNG and v2flyNG are maintained by their own independent open source projects. This site is not the publisher of these projects and takes no part in their development, operation or release cycles. The download entries on this site point to a version list maintained at the deployment layer; link availability, file contents and update frequency are decided by the respective projects, and this site cannot guarantee that any entry will be reachable at any given time.
Client interfaces and configuration fields change from version to version, so the descriptions here may differ from the latest release; always go by what the client actually shows. To the extent permitted by applicable law, this site is not responsible for: a client failing to install or run, an expired subscription URL, a failed configuration import, an unavailable node, system or data loss, or any other direct or indirect effect arising from relying on the documentation on this site.
4. Intellectual property
The client names, project names and related marks mentioned on this site belong to their respective open source projects or rights holders. Each open source project is licensed under the open source license it publishes; the specific terms are governed by the license file shipped with the project, and this site does not offer any additional interpretation of those projects' licensing scope.
The tutorials, explanations and page layouts written for this site are provided for learning and reference. If you republish or quote them, keep the source and credit the original; do not use them for misleading promotion, and do not remove any existing attribution.
5. Changes to these terms and feedback
These terms may be revised as content is adjusted or features change. When that happens, the Last updated date on this page will be changed, and continuing to use the site means you accept the revised version.
If a description on this site does not match what the client actually shows, first check the steps in the tutorial page and the field explanations in the configuration reference. If a discrepancy remains, go by the client's own interface prompts and the project documentation. For questions about how the documentation is worded, please include the specific page and field name so each item can be checked.