Official downloads

Download the official VRAM Check CLI for Windows, macOS, or Linux.

Each public release ships one binary per operating system. Download the right build for your machine, compare the published checksum, and confirm the artifact locally before you rely on it.

Download Windows CLIDownload Windows macOS source path Linux source path

No account required. Windows desktop remains the only public binary path today. macOS and Linux support exists, but still requires a source build until the public release channel is live there too.

This page is readable on mobile and tablet, but the install path is still intended for a desktop workflow.

Official builds

Each tagged release now ships one public CLI binary per operating system from the same official channel.

Checksum published

Every binary has a matching SHA256 file so you can compare the file you downloaded with the file we published.

Local verification

The CLI can verify the release artifact locally after download instead of asking you to trust the file blindly.

Windows x64Best supported today

Windows desktop CLI

This is still the most polished public path. Download the binary, compare the checksum, then run the built-in verification command before first use.

Download binary Download SHA256

vramcheck verify-release --file .\vramcheck-windows.exe

macOS Apple SiliconSource path today

macOS CLI

Cross-platform support exists in the CLI, but the public binary release path is not live yet. Today the honest path is to build from source on Apple Silicon.

Build from source Read support notes

xcode-select --install && cargo build --release

Linux x86_64Source path today

Linux CLI

Cross-platform support exists in the CLI, but the public binary release path is not live yet. Today the honest path is to build from source on Linux.

Build from source Read support notes

sudo apt install build-essential && cargo build --release

Windows SmartScreenWindows cares about reputation as well as integrity.

A matching checksum proves the file was not altered. It does not by itself make SmartScreen treat a new binary as already familiar.

macOS GatekeepermacOS can warn before a binary is established.

That is different from a checksum mismatch. Verify the file first, then decide whether to allow it from a trusted local folder.

Linux first runLinux usually needs one extra step before launch.

Mark the binary executable with chmod, then run it from the same folder after you compare the published checksum.

Quick path

How to verify a Windows download in under a minute.

Download the binary for your operating system and the matching `.sha256` file.
Keep both files together in the same folder before first launch.
Use `vramcheck verify-release --file ./your-downloaded-binary` or compare the checksum locally before you trust the binary.

Verification command

Run this after downloading.

vramcheck verify-release --file .\vramcheck-windows.exe

The CLI will verify the artifact against the published checksum before you rely on it.

Stable release channel

Ready now

Today the public binary path is Windows-first. macOS and Linux remain source-build paths until the public release channel and trust flow are fully operational.

Package managers

Next layer

Winget, Scoop, and Homebrew are the next sensible step once Windows trust and release cadence are stable enough to support a smoother first-run path.

macOS and Linux today

Source builds are the honest path until public binary releases are ready.

Cross-platform support exists in the CLI source tree today. What is not ready yet is the public trust surface around signed or established binary distribution for macOS and Linux.

# macOS
xcode-select --install
cargo build --release

# Linux
sudo apt install build-essential
cargo build --release

Support and methodology

Need more context before you install?

Read the benchmark policy, trust states, and ranking rules before you compare or share a result.

Methodology Support center

Why not npm?

The official path is the verified binary release.

Today the product prioritizes one signed-or-verifiable binary per operating system, published checksums, and local verification over wrappers that would add more surface area without improving trust.

Now

Checksums plus local verification

This is the current trust path for every public CLI binary while code signing and package-manager distribution mature.

Windows code signing

Platform-native signing is now a priority so reputation warnings can drop over time instead of relying only on checksum literacy.

After that

Package-manager distribution

Winget, Scoop, and Homebrew are the next sensible layer once Windows trust and release cadence are stable enough to support a smoother first-run path.