v2rayN 7.12 Released: New Interface & Performance Boost

If you've been using v2rayN for the better part of a year, you've probably noticed the main window getting a bit "crowded" over time — the node list gets sluggish as it grows, subscriptions take forever to update, and it's easy to lose track of which core version you're even running. Rather than a routine update, 7.12 feels like the team tackled all of these long-standing pain points at once: a reorganized interface, a rewritten subscription parser, simplified core management, and a batch of overdue bug fixes. Here's a rundown of everything worth knowing about this update, along with benchmark data and a few things to watch for when upgrading.

A Lighter Interface, and No More Memorizing Core Versions

The first thing you'll notice is the overall balance of the main window — the server list, log window, and status bar are now proportioned more sensibly, and scrolling lag with over a hundred nodes is largely gone. Icons, spacing, and fonts have also been retuned, noticeably reducing eye strain during long sessions. It's all part of the same "decluttering" push: the server list now supports collapsible groups so a large number of subscriptions doesn't overwhelm the screen; the status bar's rate display now refreshes every 500ms instead of every second; the log window supports keyword filtering so you don't have to scan line by line; and even your window layout is remembered between sessions, so panel widths and positions stay exactly where you left them.

The core side got a diet too: previously, switching between Xray-core and sing-box meant digging through a submenu just to check version numbers. Now, "Check for Core Updates" shows both cores' current and latest versions side by side, and switching no longer requires restarting the client. Downloads also support resuming — so a flaky connection won't force you to redownload the whole core file from scratch.

Subscription Updates 40% Faster, Plus a Few Bug Fixes

If your subscription has a lot of nodes, you'll notice this update right away. The team rewrote the subscription parsing logic — in their own testing with an 800-node subscription, version 7.9 averaged about 6.8 seconds while 7.12 got it down to around 4.1 seconds, a nearly 40% reduction. Auto-testing and sorting after updates are faster too, especially noticeable when updating several subscriptions at once. Two easily-overlooked edge cases were also fixed along the way: node order occasionally getting scrambled after a subscription update, and subscriptions with non-standard characters sometimes failing to parse entirely — both long-standing minor annoyances that are now resolved.

A Batch of Bugs Fixed, But Two Loose Ends Remain

Beyond those two headline changes, this release also quietly fixed a batch of smaller issues: Windows occasionally failing to create the virtual adapter in TUN mode, deleting one subscription in a multi-subscription setup sometimes removing nodes from other groups by mistake, low text contrast in some dark mode dialogs, custom hotkeys occasionally failing after a system restart, and date/time formatting mismatches with system settings in certain locales — all fixed in this version. That said, two known issues remain unresolved: on some older graphics drivers, the window's transparency effect can still occasionally glitch — if you hit this, disabling transparency in Settings works as a temporary fix. Also, a few third-party skin plugins haven't yet been updated for the new interface, so it's worth checking whether your skin has a compatible update before upgrading, to avoid layout issues.

How to Upgrade, and What to Do If Something Goes Wrong

Upgrading is simple — just overwrite the install or replace the existing program files, and your config and node data will be preserved automatically, with no need to re-import subscriptions or nodes. If you're coming from an older version (7.9 or earlier), follow these steps to avoid any hiccups during the upgrade:

1. Quit any running instance of v2rayN to make sure no leftover process is locking the config files.
2. Manually back up your config directory so you can roll back quickly if something goes wrong.
3. Download the new version's archive and extract it over the existing folder, or extract to a fresh folder and manually import your config.
4. After the first launch, verify your node list and subscriptions are intact before deleting the backup.

Grab the full installer at the download center, and if you're not yet familiar with the basics, check out the quick start guide first. If you run into connection issues after upgrading, you can roll back to the previous version to check whether it's related to this update — usually the culprit is a skin compatibility issue or an outdated config setting.

Looking ahead, the team's public roadmap mentions plans to focus on multi-device sync, more granular rule group management, and lower resource usage on weaker hardware. The server list is also planned to get custom tags and color labels, making it easier to manage large numbers of nodes from different providers. Follow our blog to stay in the loop — we'll cover every major release with a detailed changelog as soon as it drops.