Keep maintaining the client
Follow changes in v2rayN and in the technology around it, and keep improving stability, compatibility, and day-to-day use.
Everyday features should stay simple, while people who need more still have room to configure.
About us
A new start, a long commitment
2026 is the first year of a new stage of maintaining v2rayN.
This site is run by the maintainers of the v2rayN project. It is the official website. The code is hosted at 2dust/v2rayN on GitHub.
v2rayN has already come a long way. As the project has grown, new platforms, new proxy cores, new protocols, and richer configuration have been added. What people need from a stable client, clear documentation, and ongoing maintenance has changed with it.
Starting this year, we want to invest in the maintenance and development of v2rayN over the long term.
That means more than the client itself. It also means gradually completing the official site, download channels, version information, documentation, and the other project materials people actually see.
We are not here to redefine the v2rayN that already exists.
What we want is to keep moving forward on the work the project, its developers, and the community have already built: keep v2rayN open, stable, and easy to use, and let it keep developing as the technical environment changes.
What we are doing
More than maintaining a client
An open-source project that can last needs more than code.
Releases need to keep coming. New cores need to be supported. Each operating system needs maintenance. Feature changes need to be recorded. Documentation needs to be revised as the client interface changes.
So we are gradually improving the whole experience of using v2rayN.
Improve the cross-platform experience
Keep paying attention to Windows, macOS, and Linux desktops, so people on each platform get a clear, familiar v2rayN.
Features and implementation can differ between operating systems. The overall product logic should stay consistent.
Follow core and protocol changes
v2rayN stays closely tied to proxy cores such as Xray and sing-box, and to the protocol ecosystem around them.
As those projects move forward, we watch version compatibility and configuration changes, and update the related notes and guides.
Maintain downloads and version information
Operating system, processor, and release format can each mean a different installer.
We keep organizing version notes, what changed, and download guidance, so it is easier to tell which build to choose.
Improve the documentation
Documentation should be more than a list of parameters.
From the first download and install, to adding profiles and managing subscriptions, through routing, DNS, the system proxy, TUN, and other advanced features, we will build guides that are more complete and easier to follow.
Collect common questions
As more people use the client in more situations, the same questions keep coming back.
We keep collecting questions about install, configuration, cores, subscriptions, the system proxy, DNS, TUN, and each operating system, and we update the answers when versions change.
Why maintain it for the long term
When the software changes, the docs should change too
Open-source software is always changing.
A setup that is correct today may change in a later release. A download that used to be the right recommendation may stop fitting new users when platform support or the way builds are published changes.
So we do not want this site to be a static page that is finished and then left alone.
What is actually useful is ongoing maintenance.
When v2rayN publishes a new version, we update the version information.
When a client feature changes, we adjust the explanation.
When an older guide no longer fits the current version, we rewrite it.
When new questions keep appearing, we add to the documentation.
As the software moves forward, the information around it should move with it.
Our principles
Simple, open, ongoing
We want the maintenance ahead to follow a few basic principles.
Keep it simple
v2rayN can offer rich configuration. That does not mean the first time you open it has to be complicated.
The basics should be easy to understand. Advanced options are there when you need more room.
Keep it accurate
Versions, cores, protocols, and configuration all change over time.
For information that goes out of date, we revise it against the actual release instead of leaving old pages up indefinitely.
Stay open
v2rayN grew because it is open source.
The code, version changes, issues, and project history are part of the project. We will keep respecting open collaboration.
Respect the contributions
What v2rayN has today did not begin in 2026.
Developers, contributors, and community users who worked on the project before built the foundation it has now.
A new stage of maintenance should not erase that history.
We respect the existing code, commit history, contributions, and community work, and we continue from there.
Maintain it for the long term
We do not want to solve only today’s problems.
Adding a lot of content quickly matters less than whether someone is still maintaining it in one year, three years, and beyond.
2026 · Year one
The first year, and a new beginning
2026 is the first year of this new stage.
In the first year, we want to get the foundation right.
Finish the site, organize the download channels, build the documentation, keep adding version notes and common questions, and make v2rayN easier to understand and use on Windows, macOS, and Linux.
These things may not have a clear “done” date.
A project that keeps developing is never really finished.
We will keep improving this year.
We will still be doing it next year.
We hope that stays true every year after that.
When someone comes back here later, we want 2026 to mean more than a year in the footer. We want it to be the year a long period of maintenance actually began.
About open source
Openness lets the project go further
v2rayN grew on an open-source ecosystem.
The client itself, the cores it uses and supports, and the bug reports, code, and experience contributed by the community are what make v2rayN what it is today.
We value that way of working together.
We still want the code, version history, and development information to stay public, so changes can be read, discussed, and traced.
Open source is more than being able to read the source.
It also means respecting contributions, staying transparent, and leaving room for more people to take part.
What we will keep doing next
The next stage of v2rayN will not be about a single feature.
We will keep paying attention to:
- Client experienceKeep improving everyday use and configuration.
- Windows / macOS / LinuxKeep improving the experience on each desktop platform.
- Core compatibilityFollow version and configuration changes in the related proxy cores.
- ConfigurationKeep improving subscriptions, routing, DNS, the system proxy, TUN, and related features.
- DocumentationReflect feature changes in the guides in good time.
- Version historyRecord changes that are worth a user’s attention, more clearly.
- FeedbackUse real problems to find gaps, and keep improving the software and the docs.
We want to maintain this for many years
v2rayN will not stay as it is today.
Technology will change, operating systems will update, cores will keep developing, and the way people use the client will change too.
We cannot know what v2rayN will look like years from now.
We do hope one thing stays the same:
Someone is still maintaining it carefully.
In the first year, we get the foundation right.
Every year after that, we keep updating, maintaining, and improving.
Keep v2rayN simple and capable, and keep it moving forward.
2026 — the first year of a new stage.
Contact
Get in touch
If you have a question about v2rayN, the site, the documentation, version information, or anything related, you can reach us here.
For the site, documentation, project matters, and general questions.
Phone
Address
715 S Joy St
Corona, California 92879
United States