Site Scope
This site serves users looking for V2Ray clients and configuration references. It provides entry points for Windows, macOS, Android, and Linux, with installation, subscription updates, proxy modes, TUN, and troubleshooting broken into actionable steps. Download pages distinguish clients, system architectures, and package formats; tutorials focus on operation order and the impact of each setting, rather than mixing menus from different platforms into one set of instructions.
The Project V Open-Source Ecosystem
Project V is an open-source technology ecosystem built around proxy protocols, transport methods, and routing capabilities. V2Fly continues the community development path of V2Ray Core, while Xray extends protocol and transport capabilities within a similar configuration model. v2rayN is a graphical desktop client that can work with related cores; v2rayNG and v2flyNG target Android and follow different core lineages. Clients, cores, and protocols are separate layers, so confirm each one independently when choosing a setup.
Content Maintenance Principles
Download links are updated against version lists and categorized by operating system, processor architecture, and package format. Tutorials are based on the interfaces and common configuration workflows of publicly released versions. When menus change, they prioritize explaining how to identify the right option instead of recording only a fixed button location. Protocol and routing articles explain technical concepts, field behavior, and troubleshooting order without making performance claims that cannot be verified.
Usage Boundaries and Feedback
This site is for software installation, configuration learning, and technical reference. It does not provide network services or subscription resources. When using related software, follow the laws and regulations in your location, applicable network service terms, and internal organizational policies, and verify the source and purpose of every configuration yourself. For installation, import, or connection issues, start with the user guide →; for terminology and protocol relationships, continue with the glossary →.