The right package to get started

01 · System and architecture

Check your OS version and processor architecture. On Windows use Settings → System → About; on Mac use About This Mac. On Linux, uname -m reports x86_64 for x64 and aarch64 for ARM64.

02 · Packages, interfaces and storage

ZIP archives are portable: extract the entire archive into a writable folder, where its data is stored. Installed DEB, RPM and DMG editions may keep user data separately; use the client’s open-storage command to locate it.

Standard Windows ZIPs use WPF; names containing desktop use Avalonia. These are interface implementations, not paid editions or server plans. Some cores are included; add others only when needed.

Core referenceConfiguration files

03 · Windows installation

Use x64 for 64-bit Intel/AMD Windows, ARM64 for Windows on ARM and x86 for a 32-bit OS. The 7.25.6 release includes x86 assets; older FAQ notes about compiling them are historical.

Extract the entire matching ZIP and launch v2rayN.exe from the extracted folder. Do not run inside an archive viewer or copy only the executable. Ordinary system proxy usage does not require keeping the entire app elevated; follow client prompts for TUN permissions.

Import a profile and inspect the information panel. If launch fails, check architecture, complete extraction, writable storage and security-software logs.

Windows downloads

04 · macOS installation

Choose arm64 for Apple Silicon or 64 for Intel. Open the DMG, drag the app into Applications and launch it there. For a portable ZIP, extract everything, run chmod +x v2rayN in its folder, then ./v2rayN as a normal user.

The official installation instructions describe unsigned DMGs that may trigger a “damaged” message. After checking the official download and its signature, the command below clears extended attributes on this specific application before reopening it. It does not repair an incomplete download.

macOS · TerminalCopy

xattr -cr /Applications/v2rayN.app

macOS downloadsVerify the download

05 · Linux installation

Open a terminal in the download folder and select the command for your distribution and architecture. The ./ prefix identifies a local file. The published x64 RPM is named v2rayN-linux-rhel-64.rpm.

Launch from the application menu after installation. For a ZIP, extract, enter its folder, run chmod +x v2rayN and then ./v2rayN. Do not run the entire desktop app with sudo as a substitute for package installation permissions; handle TUN permissions separately.

Linux · choose one commandCopy

# Debian / Ubuntu · x64
sudo apt install ./v2rayN-linux-64.deb
# Debian / Ubuntu · ARM64
sudo apt install ./v2rayN-linux-arm64.deb
# Fedora / Red Hat · x64
sudo dnf install ./v2rayN-linux-rhel-64.rpm
# Fedora / Red Hat · ARM64
sudo dnf install ./v2rayN-linux-rhel-arm64.rpm

Linux downloads

06 · Make the first connection

Copy your own share link and import it through the menu or Ctrl+V outside text fields. For a subscription, save its URL in a group and update it. Activate a profile and enable automatic system proxy.

Visit your destination in a browser. If it fails, check core startup and logs. Importing a profile or completing a latency test does not itself configure browser traffic.

Subscription workflowConnection troubleshooting

07 · Upgrade, back up and restore

Use Backup and restore to save guiConfigs as a ZIP before upgrading; explicitly use the .zip extension on non-Windows systems. Record client/core versions and architecture.

For portable use, extract the new package to a new folder and restore the backup there. Keep the old folder until connections and subscriptions work. Upgrade installed editions with the same platform and architecture; uninstalling the app does not necessarily remove user data. Restore restarts the client; reopen manually if needed.

Version 7.25.6 changes core compatibility and generated configuration, so check the active profile, routing, DNS, subscriptions and TUN after upgrading.

Current release notesBackup reference