This site brings together download links, installation steps, and configuration guides for v2rayN, v2rayNG, and v2flyNG, helping readers find the right package for their platform before importing configurations, connecting, and troubleshooting.
V2Ray Download Center is for readers who need graphical clients, covering Windows, macOS, Android, and Linux. Download pages are organized by operating system, CPU architecture, and package type. Tutorials break subscription imports, node selection, system proxies, routing modes, and common issues into clear steps, so readers spend less time searching across separate sources.
Project V is an open-source ecosystem built around proxy protocols, transport methods, routing rules, and client tools. Graphical clients provide the configuration and control interface, while connection capabilities are usually supplied by a core. Client names, core names, and protocol names should therefore be understood separately.
V2Fly continues the community-maintained path of V2Ray Core, while Xray extends transport and protocol capabilities while remaining compatible with common configuration approaches. v2rayN can work with different cores; v2rayNG mainly uses Xray, while v2flyNG corresponds to V2Fly. Check client support first, then verify the server configuration requirements.
The download page checks application names, operating systems, CPU architectures, and package types against publicly available release lists. Links are updated when versions change to keep desktop packages, mobile packages, and architecture-specific files from being mixed under the same button.
Tutorials are organized around the client's actual interface, with particular attention to menu paths, import order, connection status, and error logs. When the interface changes, steps affecting installation or connectivity are revised first. For further troubleshooting, continue searching from the tutorials page →
This site provides software information, download navigation, and configuration knowledge. It does not provide network services or guarantee the availability of third-party services. Users should assess each use according to local laws, network management requirements, and service terms, and are responsible for safeguarding subscription URLs, account details, and configuration data.
Names of third-party software, protocols, and projects belong to their respective rights holders. For the full scope of responsibility, please read the disclaimer →