← All open source projects

v2rayNG

2dust/v2rayNG

v2rayNG is an Android client for V2Ray, Xray, v2fly-core, and related proxy configurations.

Forks 7,663
Author 2dust
Language Kotlin
License GPL-3.0
Synced 2026-06-27

What it is

v2rayNG is an Android client for V2Ray, Xray, and v2fly-core. It helps manage proxy profiles, subscriptions, routing rules, and connection state on a mobile device.

The project covers a practical need: complex network cores require configuration, while an Android user needs an interface for adding profiles, switching servers, and checking status.

How the project is built

The repository contains the Kotlin application, Android project, build material, links to the wiki, and client development around different cores. It is not the protocol or server, but a mobile management shell.

Android-client role

This sketch shows where v2rayNG sits: between a user profile, the network core, and the Android system.

Language: Plain text
subscription or profile
  -> v2rayNG
  -> V2Ray/Xray core
  -> Android VPN service
  -> selected routing rules

The example is included for a practical reason: it shows the real shape of working with the project, whether that is a command, data structure, interface fragment, or diagram that appears in documentation and source code.

How it is used

A typical scenario is importing a profile or subscription, choosing an active node, configuring rules, and starting the connection. Actual use must follow laws, network rules, and organizational policy.

v2rayNG should be tested in a small controlled environment: profile format, server trust, routing rules, mobile or desktop behavior, and the requirements of the specific network. Network clients quickly become sensitive parts of user security.

It is also worth checking project boundaries: what it does itself, what it delegates to external services, what data it accepts, and which decisions stay with the user. That prevents expecting more than the repository promises.

For the catalog, the important point is not only that the repository exists, but what practical role it plays: where it fits into a stack, what manual work it removes, and which decisions remain with the team.

Strengths and limits

The strength is mobile convenience. The user gets graphical control over complex configuration, quick switching, and connection-status visibility.

The limitation is dependence on external profiles, servers, and network conditions. The client does not guarantee route quality, safety, or permissibility; those remain with the infrastructure owner and user.

Context

v2rayNG should be understood as a popular Android client in the proxy-tool ecosystem. It matters as a user-facing shell, not as a complete network solution by itself.

This kind of overview helps separate a repository as an attractive GitHub page from a repository as a real stack element with documentation, limits, community, and maintenance cost.

Before using a project like this, it is worth checking current status, license, recent changes, open issues, and fit for the actual task. That is especially important for infrastructure, AI tools, network clients, and older archived projects.