Download sources & GPG verification

Prepare the package, signature and key

Use three files from the same release: the package, its matching filename plus .sig detached signature, and the release public key. For example, the x64 Windows ZIP requires v2rayN-windows-64.zip.sig, not a signature from another architecture or version.

Download buttons point directly to official release assets; no third-party downloader is required.

Choose a packageDownload the 7.25.6 public keyWindows x64 signature

Check the public-key fingerprint

Use GnuPG compatible with this key format and check gpg --version. The current release key is v5; an unsupported-version error calls for a compatible tool, not a conclusion that verification succeeded or the file is corrupt.

The complete fingerprint below matches the README and downloaded release key at review time. Display the key fingerprint and compare every group. A signer name alone does not establish key identity.

Release public-key fingerprintCopy

7694 5E9F 3E9A 168F 8070 F195 805D 661C
134D FAF6 8903 C199 463C 31E5 AE90 3AE0

Display, import and verify

Open a terminal in the folder containing the three files. Display the key first, compare the fingerprint, then import it and verify the signature against the original package. For another platform, replace both filenames on the last line with the matching pair.

GnuPG · run in order after checking the fingerprintCopy

gpg --show-keys --with-fingerprint v2rayN-public-key.asc
gpg --import v2rayN-public-key.asc
gpg --verify v2rayN-windows-64.zip.sig v2rayN-windows-64.zip

Interpret verification results

Successful signature verification plus the expected signer fingerprint establishes that the file matches that key’s signature. A SHA-256 calculation alone does not identify the publisher without a trusted expected digest.