Valorant .vrf file inspector
Drop a Valorant replay file in and this tells you what it is: the match id, how long the match ran, when it was recorded and which game build produced it. No account, and the file is never uploaded anywhere.
Why this is useful
Valorant names every replay after its match id, so a folder of them is a wall of identical-looking filenames with no dates, maps or scores. Working out which file is last night's game normally means opening the client and cross-referencing by hand.
This reads the header and tells you directly. It also catches the obvious failures: a file that is not a replay at all, one whose header is damaged, and one that is plainly shorter than its own header says it should be.
It cannot promise a file is complete. Only the first two kilobytes are read, and a replay has no field stating its total length, so a 60 MB file whose copy stopped at 30 MB still has a perfectly good header. What this rules out is the file being the wrong thing or obviously broken, not every possible truncation.
Nothing is uploaded
The file is read in your browser using the standard file API, and only the first two kilobytes of it are read at all, which is where the header lives. There is no request to any server, so a 60 MB replay costs nothing to check and never leaves your machine. Closing the tab is the entirety of the cleanup.
What the fields mean
Match id is the game's own name for the match and matches the filename. It is the most useful thing to quote when reporting a problem with a specific game.
Match length is the full duration the replay covers, buy phases included, so it runs longer than the sum of the rounds.
Recorded is read from a timestamp inside the file rather than from the file's modification date, so it survives being copied between machines.
Game build is which version of Valorant wrote the replay. This matters more than it looks: the replay format is not documented, and a patch can move things inside the file. A tool that has not been checked against a build can produce confidently wrong numbers, which is why valab flags an unverified build rather than reading it anyway.
What it does not do
This reads the header only, not the match. It cannot tell you the map, the agents or the score, because none of that is in the first two kilobytes; it sits in the compressed body, and getting at it means reading the whole file properly.
For that, upload the replay to valab. A free account gets a match a day with every feature on, and the match comes back as full browser playback with heatmaps, duels and a scouting report.
Where to find your replays
Under %LOCALAPPDATA%\VALORANT\Saved\Demos. Paste that into the File Explorer address bar; AppData is hidden by default, which is the usual reason the folder seems not to exist. There is more detail, including why replays disappear, in what is a .vrf file.