Microsoft Store install
Use the Store listing for managed package delivery and updates without handling the executable manually.
Measure your machine. Keep the evidence.
VRAM Check for Windows is available in Microsoft Store with a graphical interface. Inspect your hardware, run a local benchmark, and choose whether to publish your result.
The published Store package v0.4.3.0 includes Desktop 0.1.0-alpha.3 and Engine 2.0.0-alpha.30. Experimental Model Lab response sessions stay local and do not create leaderboard scores. The direct EXE is the older command-line application, not the graphical app.
From installation to an answer.
- 1
Install for your computer
Use Microsoft Store on Windows, or choose an available package below. Open VRAM Check to begin.
- 2
Give the GPU a clear run
Close games and other GPU-heavy apps. Follow the benchmark prompts; first-run setup may need additional downloads.
- 3
Read the measured result
Review your speed, explore estimated model fits and decide whether to publish. A low result is a reason to investigate, not automatically to buy.
Local benchmarkInference runs on the machine you are testing.
Explicit publishingYou choose whether a result is submitted publicly.
Trusted distributionWindows installs through Microsoft Store; direct artifacts remain traceable.
Choose the build that matches the machine.
Choose your operating system below. If a public package is not available, we say so.
PlatformRuntimeStatusReleaseAction
Windows x64VulkanMicrosoft StoreDesktop app · Engine 2.0.0-alpha.30Get from Store macOS Apple SiliconMetalNot available yetNo public download is activeCheck support options Linux x86_64VulkanBinary available · native test pendingCLI v0.3.0 · 45.5 MB · SHA256 publishedDownload binary Desktop app or legacy CLI: choose deliberately.
Do not repeat a benchmark to fix a timing-contract or unregistered-binary rejection. These require a corrected release and server registration, not a hardware change.
Legacy CLI: no digital signature
The direct EXE does not include the graphical interface. Windows may block it. Prefer Microsoft Store; do not disable antivirus protection. A checksum verifies file identity, not software safety.
Platform availability
The platform list reflects the published release registry. The Linux CLI artifact is checksum-verifiable, but native installation and Vulkan benchmark validation are still pending. A missing package is not a public source-build option.
Know the method behind every score.
See how verification, ranking eligibility, measured performance, and estimated model fit stay separate.