# Install v2ray with Homebrew, apk, chocolatey, apt, MacPorts, Nix, pacman, scoop, winget, zypper

Platform for building proxies to bypass network restrictions. Version 5.51.2 via Homebrew; verified 2026-07-26. Also installable with debian: sudo apt install v2ray.

## Install

```sh
sudo av install brew:v2ray
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install v2ray
```

  Evidence: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install v2ray
```

  Evidence: MacPorts ports tree: net/v2ray/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- apk (92%):

```sh
sudo apk add v2ray
```

  Evidence: Alpine Linux edge package indexes: v2ray from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

- Debian apt (92%):

```sh
sudo apt install v2ray
```

  Evidence: Debian stable package indexes: v2ray from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

- Nix (92%):

```sh
nix profile install nixpkgs#v2ray
```

  Evidence: nixpkgs package indexes: pkgs/by-name/v2/v2ray/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- pacman (92%):

```sh
sudo pacman -S v2ray
```

  Evidence: Arch Linux sync databases: v2ray from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

- zypper (92%):

```sh
sudo zypper install v2ray-core
```

  Evidence: openSUSE Tumbleweed package metadata: v2ray-core from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

### Windows

- Chocolatey (92%):

```sh
choco install v2ray
```

  Evidence: Chocolatey community package catalog: v2ray from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','unikey'

- Scoop (92%):

```sh
scoop install main/v2ray
```

  Evidence: Scoop official bucket manifest trees: bucket/v2ray.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

- winget (92%):

```sh
winget install --id v2fly.v2ray-core -e
```

  Evidence: Windows Package Manager source index: v2fly.v2ray-core from https://cdn.winget.microsoft.com/cache/source.msix

## Package facts

- **Package key:** brew:v2ray
- **Package manager:** Homebrew
- **Version:** 5.51.2
- **Source summary:** Platform for building proxies to bypass network restrictions
- **Homepage:** <https://v2fly.org/>
- **Repository:** <https://github.com/v2fly/v2ray-core>
- **Last updated:** 2026-07-26T00:29:59+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- v2ray (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 5.51.2
## Project history and usage

V2Ray is the core tool of Project V, a proxy and network-routing platform maintained by the V2Fly community. Official V2Fly documentation presents it as a multi-protocol, cross-platform system for building dedicated communication networks with configurable inbound protocols, outbound protocols, routing, transports, and obfuscation.

### Project history

Project V documentation describes V2Ray as the core of a broader tool collection: V2Ray handles network protocols and communication, while other tools and user interfaces can build on top of it. The newer V2Fly site describes the project as community-led and points the official core source to `v2fly/v2ray-core`.

The official plain-language guide places V2Ray in the same historical neighborhood as Shadowsocks, but distinguishes it as a platform rather than a single proxy protocol. It says V2Ray was developed after pressure against the Shadowsocks creator and that Project V developed it as a protest; this is community documentation rather than a conventional corporate origin story.

The developer documentation shows the modern project as a Go codebase built and released through GitHub automation, with release artifacts archived for long-term availability and stable releases signed with the V2Fly signing key.

### Adoption history

V2Ray's adoption was driven by users who needed configurable proxying and routing across censorship-prone or restricted networks. The official guide assumes users are comfortable with Linux shells, VPS access, SSH, and editing configuration files, which reflects the self-hosted, operations-heavy adoption path.

Package-manager adoption broadened the install story. The supplied package facts list Homebrew, Chocolatey, Debian, Ubuntu, Arch, Nix, MacPorts, Scoop, WinGet, zypper, and apk names, matching the official project's cross-platform positioning.

### How it is used

V2Ray is configured primarily through JSON. The official FAQ shows troubleshooting with systemd logs and `v2ray -config=<config-file> -test`; protocol docs describe user IDs, transports, and protocol-specific authentication; and the home page highlights multi-entry/multi-exit routing, multi-protocol support, stealth, security, load balancing, and cross-platform operation.

In package-nerd terms, V2Ray is often installed as a daemon-capable CLI plus configuration tree. The interesting parts are not a simple `v2ray` executable alone, but the package's config-file locations, service integration, signed release artifacts, and compatibility with multiple inbound and outbound proxy protocols.

### Why package nerds care

V2Ray is significant because it packages a modular proxy platform into ordinary OS package-manager channels. It is a network tool whose real behavior is determined by structured config, protocol modules, transport choices, routing rules, and service-manager setup.

It also sits in a sensitive niche: anti-censorship and privacy-network tooling. For maintainers, that makes official-source provenance, signed releases, config-path clarity, and avoiding random mirrors especially important.

### Timeline

- 2015-present: V2Fly site footer identifies Project V/V2Fly community material across this period.
- 2020: The V2Fly-maintained plain-language guide documents V2Ray's relationship to Project V and Shadowsocks-era history.
- 2020s: Developer docs describe the Go codebase, GitHub-based release automation, release archiving, and stable release signing.

### Related projects

- Project V is the broader tool collection around V2Ray.
- Shadowsocks is the related single-protocol proxy tool used as a comparison point in official V2Fly guide material.
- VMess and VLESS are V2Ray-related protocols; VMess is documented as V2Ray's original encrypted communication protocol.

### Sources

- <https://guide.v2fly.org/en_US/ - Official V2Fly guide describes V2Ray as the core Project V tool and gives the Shadowsocks comparison/origin narrative.>
- <https://www.v2fly.org/en_US/ - Official V2Fly home page describes Project V, V2Ray capabilities, protocols, routing, security, load balancing, platforms, and community development.>
- <https://www.v2fly.org/en_US/developer/intro/compile.html - Official developer docs describe the Go codebase and source clone path.>
- <https://www.v2fly.org/en_US/developer/intro/releasearchive.html - Official developer docs describe release archiving.>
- <https://www.v2fly.org/en_US/developer/intro/releasesigning.html - Official developer docs describe stable release signing.>
- <https://www.v2fly.org/en_US/developer/protocols/vmess.html - Official protocol docs describe VMess as V2Ray's original encrypted communication protocol.>
- <https://www.v2fly.org/en_US/guide/faq.html - Official FAQ documents anonymous/community leadership, upgrade/troubleshooting commands, and repository authorization.>


## Security Notes

formula declares a Homebrew service.

- **Geiger risk:** orange / medium
- formula declares a Homebrew service


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Linux: /etc/v2ray/config.json, /usr/local/etc/v2ray/config.json, /opt/v2ray/etc/config.json
- macOS: config.json in the same directory as V2Ray
- Windows: config.json in the same directory as V2Ray
## Other Package-Manager Records

- Debian apt - v2ray - 4.34.0+ds-4+b12: normalized package name match | Debian stable package indexes: v2ray from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Command line tool for golang-v2ray-core | https://github.com/v2fly/v2ray-core
- Nix - v2ray: normalized package name match | nixpkgs package indexes: pkgs/by-name/v2/v2ray/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Ubuntu apt - v2ray - 4.34.0+ds-4: normalized package name match | Ubuntu 24.04 LTS package indexes: v2ray from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Command line tool for golang-v2ray-core | https://github.com/v2fly/v2ray-core
- apk - v2ray - 5.47.0-r3: normalized package name match | Alpine Linux edge package indexes: v2ray from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | A platform for building proxies to bypass network restrictions | https://v2fly.org
- apk - v2ray-openrc - 5.47.0-r3: normalized package name match | Alpine Linux edge package indexes: v2ray-openrc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | A platform for building proxies to bypass network restrictions (OpenRC init scripts) | https://v2fly.org
- pacman - v2ray - 5.49.0-1: normalized package name match | Arch Linux sync databases: v2ray from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A platform for building proxies to bypass network restrictions | https://github.com/v2fly/v2ray-core
- zypper - v2ray-core - 5.51.2-1.4: normalized package name match | openSUSE Tumbleweed package metadata: v2ray-core from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Network tools for building a computer network | https://github.com/v2fly/v2ray-core
- MacPorts - v2ray: normalized package name match | MacPorts ports tree: net/v2ray/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Chocolatey - v2ray: normalized package name match | Chocolatey community package catalog: v2ray from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','unikey'
- Scoop - main/v2ray: normalized package name match | Scoop official bucket manifest trees: bucket/v2ray.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- winget - v2fly.v2ray-core: normalized package name match | Windows Package Manager source index: v2fly.v2ray-core from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

View the package source record on GitHub. [combined/v2ray.yml](https://github.com/mxcl/pkgdb/blob/main/combined/v2ray.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph