RivaTuner Statistics Server (RTSS) supplies an in-game on-screen display, frame-rate and frame-time monitoring, and frame limiting. It is commonly paired with MSI Afterburner, which supplies hardware telemetry and GPU tuning controls. Choose RTSS for the display or limiter task; you do not need to change GPU clocks to diagnose a missing overlay.
Editorial review: 6 October 2026 UTC. Current publisher pages were reviewed. A package download, file hash measurement, signature check, installation, game compatibility test and performance benchmark were not performed for this review.
Current final release and official source
The Guru3D distribution page identifies 7.3.7 Final, dated 30 September 2025. Its displayed 15 MB size is a publisher estimate, not a byte count measured here. Use the page’s RTSS download control; a nearby advertisement is not the software download.
Guru3D also recommends its Afterburner package, which includes a stable RTSS build. Check the versions actually offered in that package instead of assuming every Afterburner release bundles the same RTSS version. MSI’s current landing page separately lists Afterburner 4.6.6 Final and 4.6.7 Beta; those are Afterburner version numbers, not RTSS version numbers.
Freeware does not mean unrestricted redistribution
The download page lists RTSS as free freeware. The publisher’s hosting statement restricts distribution outside Guru3D without the author’s permission. This is not a GPL/open-source licence or permission to repackage the installer. We link to the publisher and do not host a copy.
What to check on your PC
The publisher lists Windows XP through Windows 11, x86 and x64, administrative rights, and a graphics card compatible with DirectX, Vulkan or OpenGL. That historical OS list is not a statement that Microsoft still supports every listed Windows version. Check your Windows edition’s lifecycle separately; see our Windows 11 24H2 support guide.
Game and overlay compatibility are separate from these system requirements. Guru3D notes that other on-screen display tools can conflict, and that some games’ anti-cheat may block overlays. Do not disable anti-cheat or security protections to force RTSS into a game.
Use a simple decision checklist
- You only need FPS: first check whether the game or your GPU software already exposes a suitable counter.
- You need hardware readings: confirm the sensor values in Afterburner before diagnosing their display in the game.
- You want to try a frame cap: write down the game’s existing cap, driver settings and any other limiter. Change one setting at a time so you can tell which limiter is responsible.
- Only one game fails: record its executable, rendering API and patch. Treat its profile separately from settings applied to every application.
If the overlay is missing
Use the Afterburner/RTSS overlay troubleshooting guide to separate sensor selection, RTSS operation and application-specific failures. Preserve your profile settings before attempting a reset or clean reinstall. The publisher suggests a clean reinstall for some post-update failures; removing profiles can discard your configuration, so it should not be the first blind step.
If you also use OptiScaler or Special K, check their own overlay/injection guidance. Avoid stacking several modifications while troubleshooting. A working overlay in one offline title is not proof that it is permitted in another protected title.
File checks and comparison limits
No release checksum was visible in the Guru3D page reviewed here. That does not establish that a checksum exists nowhere else. If you inspect a downloaded installer, record its exact filename, length, SHA-256 and Windows signature result; do not substitute a checksum from a different version. Our signature-check guide explains the read-only check.
For a permitted offline comparison, keep the same scene and settings and record frame times as well as FPS, with and without the tool. Average FPS alone cannot establish smoother output. This is a proposed comparison method, not a benchmark we ran. Keep a record of your original configuration so you can restore it if the change makes your result worse.
