Installation

Windows · x64 / ARM64 macOS · Intel / Apple silicon Linux · DEB / RPM / AppImage Native multi-core support

Clash Nyanpasu supports Windows 10 and later, macOS 12.6 and later, and Linux with glibc >= 2.39. Choose the package for your device from the official releases page; package types and architectures vary by release.

Choose the right package

flowchart TD
  A[Check your operating system and CPU architecture] --> B{Operating system}
  B -->|Windows| C{CPU}
  C -->|Intel or AMD| D[x64 setup installer]
  C -->|ARM-based Windows| E[ARM64 setup installer]
  B -->|macOS| F{CPU}
  F -->|Intel| G[x64 DMG]
  F -->|Apple silicon| H[aarch64 DMG]
  B -->|Linux| I{Distribution or package type}
  I -->|Debian or Ubuntu| J[DEB · amd64 or arm64]
  I -->|Fedora or RPM-based| K[RPM · x86_64 or aarch64]
  I -->|Arch Linux| L[AUR · community packages]
  I -->|AppImage| M[AppImage · x86_64]

Check your CPU architecture. On Windows, open Settings → System → About and read System type. On macOS, open Apple menu → About This Mac. On Linux, run uname -m in a terminal.
Match the asset name. x64, amd64, and x86_64 refer to 64-bit Intel/AMD builds. ARM64 and aarch64 refer to 64-bit Arm builds. The release page may not offer every package type for every architecture.
Install the package and continue to your first connection. If you are using a Linux package, also read the notes for that package below.

Windows

Windows 10 or later x64 ARM64

Download the installer ending in _x64-setup.exe for most Intel/AMD PCs or _arm64-setup.exe for Windows on ARM.

Portable archive

Windows releases also provide _x86_64_portable.zip and _aarch64_portable.zip. Extract the archive and run the app executable. Fixed-WebView portable archives are also available and include the WebView2 runtime.

The standard portable archive does not contain WebView2, so the runtime must already be installed. Portable settings and data are stored under .config/ and .data/ beside the extracted app; keep that folder writable and together when moving or backing up the app.

The archive includes nyanpasu-service.exe; installing or starting the service requests elevated authorization and registers a Windows service. When the app starts, its deep-link handler also registers the clash: and clash-nyanpasu: URL schemes for the current user, so portable mode can still make these system changes. Windows system notifications are shown as app dialogs in portable mode. Portable packages do not receive the app’s in-app application updates, so install a newer portable archive manually when you update.

macOS

macOS 12.6 or later Intel · x64 Apple silicon · aarch64

Download the .dmg ending in _x64.dmg for an Intel Mac or _aarch64.dmg for an Apple-silicon Mac. Open the disk image and drag Clash Nyanpasu to Applications. If installation fails, see the FAQ.

Linux

Official Linux package availability depends on the release. Current package families include DEB for amd64 and arm64, RPM for x86_64 and aarch64, and an amd64 AppImage. The AppImage is not currently published for ARM64.

Download the .deb ending in _amd64.deb or _arm64.deb, then install it from the download directory:

sudo apt install ./Clash.Nyanpasu_*_amd64.deb

For an ARM64 system, use:

sudo apt install ./Clash.Nyanpasu_*_arm64.deb

The wildcard assumes that only one matching release package is in the current directory.

Download the .rpm ending in .x86_64.rpm or .aarch64.rpm, then install it with DNF:

sudo dnf install ./Clash.Nyanpasu-*.x86_64.rpm

For an ARM64 system, use:

sudo dnf install ./Clash.Nyanpasu-*.aarch64.rpm

The wildcard assumes that only one matching release package is in the current directory.

Download the .AppImage ending in _amd64.AppImage. After making it executable, you can double-click it in your file manager or launch it from a terminal. In the directory containing the download, run:

chmod +x ./Clash.Nyanpasu_*_amd64.AppImage
./Clash.Nyanpasu_*_amd64.AppImage

The wildcard assumes that only one matching AppImage is in the current directory. To enable launch at login, open Settings → System → Startup Settings → Start on system startup.

TUN depends on the selected core and needs suitable network privileges. Use System Service to install and start the service with elevated authorization, enable Service Mode, then enable TUN; keep the desktop app running as your normal user instead of launching the whole AppImage with sudo. Follow System Proxy and TUN for the steps.

If you encounter another AppImage issue, include your Linux distribution, architecture, app version, and package type when reporting it.

Optional AppImage launcher and autostart entry

The built-in login setting is under Settings → System → Startup Settings → Start on system startup. If you create a desktop entry manually, keep the AppImage at a fixed absolute path and replace VERSION with its actual filename. A launcher belongs in an applications directory; automatic login uses a separate autostart directory. Autostart=true is not a standard desktop-entry key, and update-desktop-database refreshes the applications directory only. Use either the built-in setting or the manual autostart entry to avoid launching the app twice.

User directories
System directories

Set APPIMAGE_PATH to the absolute path of your AppImage. This example uses the standard hicolor icon directory:

APPIMAGE_PATH="$HOME/Applications/Clash.Nyanpasu_VERSION_amd64.AppImage"
ICON_DIR="$HOME/.local/share/icons/hicolor/256x256/apps"
APP_DIR="$HOME/.local/share/applications"

chmod +x "$APPIMAGE_PATH"
mkdir -p "$ICON_DIR" "$APP_DIR"
curl -fL "https://raw.githubusercontent.com/libnyanpasu/clash-nyanpasu/main/frontend/nyanpasu/src/assets/image/logo-box.png" -o "$ICON_DIR/clash-nyanpasu.png"

cat > "$APP_DIR/clash-nyanpasu.desktop" <<EOF
[Desktop Entry]
Type=Application
Name=Clash Nyanpasu
Comment=Clash proxy client
Exec="$APPIMAGE_PATH" %U
Icon=clash-nyanpasu
Terminal=false
Categories=Network;
EOF

update-desktop-database "$APP_DIR"

For automatic login, create a separate entry in the user autostart directory:

APPIMAGE_PATH="$HOME/Applications/Clash.Nyanpasu_VERSION_amd64.AppImage"
AUTOSTART_DIR="$HOME/.config/autostart"
mkdir -p "$AUTOSTART_DIR"

cat > "$AUTOSTART_DIR/clash-nyanpasu.desktop" <<EOF
[Desktop Entry]
Type=Application
Name=Clash Nyanpasu
Exec="$APPIMAGE_PATH"
Terminal=false
EOF

Place the AppImage at a fixed path readable by all users, such as /opt/clash-nyanpasu/, and replace VERSION with its actual filename. The first command copies it from Downloads; change that source path if needed.

APPIMAGE_PATH="/opt/clash-nyanpasu/Clash.Nyanpasu_VERSION_amd64.AppImage"
ICON_DIR="/usr/share/icons/hicolor/256x256/apps"
APP_DIR="/usr/share/applications"

sudo install -D -m 0755 "$HOME/Downloads/Clash.Nyanpasu_VERSION_amd64.AppImage" "$APPIMAGE_PATH"
sudo install -d "$ICON_DIR" "$APP_DIR"
curl -fL "https://raw.githubusercontent.com/libnyanpasu/clash-nyanpasu/main/frontend/nyanpasu/src/assets/image/logo-box.png" -o /tmp/clash-nyanpasu.png
sudo install -m 0644 /tmp/clash-nyanpasu.png "$ICON_DIR/clash-nyanpasu.png"

sudo tee "$APP_DIR/clash-nyanpasu.desktop" >/dev/null <<EOF
[Desktop Entry]
Type=Application
Name=Clash Nyanpasu
Comment=Clash proxy client
Exec="$APPIMAGE_PATH" %U
Icon=clash-nyanpasu
Terminal=false
Categories=Network;
EOF

sudo update-desktop-database "$APP_DIR"

To start it automatically for all users, add a separate entry under /etc/xdg/autostart:

APPIMAGE_PATH="/opt/clash-nyanpasu/Clash.Nyanpasu_VERSION_amd64.AppImage"
sudo tee /etc/xdg/autostart/clash-nyanpasu.desktop >/dev/null <<EOF
[Desktop Entry]
Type=Application
Name=Clash Nyanpasu
Exec="$APPIMAGE_PATH"
Terminal=false
EOF

If update-desktop-database is unavailable, install your distribution’s desktop-file-utils package.

Arch Linux · AUR

Community-maintained Choose one package

AUR packages are maintained by community contributors, not by the Clash Nyanpasu project. These package variants conflict with one another; install only one. The versions below are from AUR RPC records checked on 17 October 2026; verify the current record before installation.

Package: clash-nyanpasu. This variant builds the app from source.

Package: clash-nyanpasu-bin. This variant installs a prebuilt app instead of compiling it locally.

The AUR record reports 2.0.0rc.2-1, which corresponds to upstream 2.0.0-rc.2. Although the AUR package is the prebuilt stable variant, its current upstream version is a release candidate.

paru -Syu clash-nyanpasu-bin
# or
yay -Syu clash-nyanpasu-bin

Package: clash-nyanpasu-git. This variant builds from the source revision tracked by its AUR recipe. The RPC record reports 2.0.0.r6931.f6538a47-3 (revision f6538a47); development builds can change frequently and may include bugs.

paru -Syu clash-nyanpasu-git
# or
yay -Syu clash-nyanpasu-git