Download v2rayN for macOS / Linux: which package do you need?
v2rayN covers the three major desktop platforms. On macOS, start with the chip; on Linux, start with the package format—then import a subscription and verify the connection to avoid detours.
First clarify: you want the desktop client v2rayN
macOS and Linux users should also download v2rayN—not the Android clients v2rayNG or v2flyNG. It sounds simple, yet it is one of the most common mistakes on the download page. If your primary device is a computer, lock the client to v2rayN first; only then choose among dmg, zip, deb, and rpm.
Cross-platform does not mean one package fits every OS. Install methods, permission models, and architecture names differ. Wrong architecture may refuse to open—or misbehave after install. Confirming OS and CPU architecture separately matters more than staring at version numbers.
macOS: Apple Silicon or Intel?
On a Mac, check the chip first. Apple Silicon (M-series) should prefer arm64 packages; filenames often include macos-arm64 and a dmg suffix. For Intel chips, choose the matching x64 / macos-64 package. Open About This Mac to see chip info. If unsure, do not guess from “it looks new”—system info is the accurate source.
dmg works for most users: open the image and follow the prompts or drag to install. If you prefer a portable folder, use the same-architecture zip. A first-launch warning about an unidentified developer is a common macOS security check. Allow it under Privacy & Security, or right-click the app and choose Open—still only if the package came from a trusted download channel.
Another often-missed point: mixing architectures causes odd issues. Forcing an old Intel build on Apple Silicon may run via translation, but performance and stability can suffer. Since the Download Center already ships matching packages, pick by chip—much simpler.
Linux: deb, rpm, or zip?
On Linux, start with the distro family. Ubuntu, Debian, and derivatives usually prefer .deb; Fedora, RHEL, CentOS, and similar systems usually prefer .rpm. On rolling releases, immutable systems, or when you just want to verify it runs, a generic .zip is often more flexible: extract and run without depending on a package manager.
For architecture, most PCs use x64; ARM devices (some SBCs or ARM laptops) use arm64. Do not map Android APK architecture names onto Linux desktop packages—the ecosystems differ. The Linux filter on the download page exists to reduce that mismatch: filter by OS first, then read arch and format in the filenames.
After a package-manager install, check that a desktop entry was created; with zip, keep the folder intact like a Windows portable build. When updating, overwrite the same location so you do not end up with three versions and lose track of where configs live.
How to filter quickly in the Download Center
Open the v2rayN download page and use System filter to switch to macOS or Linux. The page may also suggest a default platform from the browser UA, but auto-detect is not perfect—especially with unusual browser IDs or remote desktop. Always trust your own system info.
Do not panic when you see multiple packages. dmg and zip, or deb and rpm, exist for different install habits—not because you must download everything. Pick the recommended package that fits your environment; the Recommended badge usually marks the common choice, such as macOS arm64 dmg or Linux x64 deb.
One shared flow after install
On both macOS and Linux, the path after install is the same: import a subscription or node, pick a working server, enable the proxy, and verify. Desktop beginners should still start with system proxy, confirm the browser works, then explore TUN and richer routing as needed. If subscription updates fail, check the link, network, and time before switching clients.
If you use both a computer and a phone, keep v2rayN on desktop and choose v2rayNG—or v2flyNG if needed—on the phone. Both ends can share the same subscription source; do not mix package platforms. Get client choice, package choice, and proxy mode right, and macOS/Linux onboarding stays much more stable.
Final note: this site provides client downloads and usage guides. You must obtain your own node service and follow local laws. Tools solve how you connect; they do not replace lawful, compliant use.