You take a screenshot. The archive does the rest.
Three steps, no launcher permissions and nothing running while you play.
Finish the match, keep the report.
Overwatch shows you a Game Report and then throws it away. That screen is the only thing OverAnalyzer needs: result, map, mode, and your stat line are all on it.
King's Row
3–2
Busan
2–0
Dorado
1–3OCR reads the scoreboard.
Drop the image into the web uploader. Every field comes back as text you can check, and anything misread is one click to fix before it's saved.
The trends re-measure themselves.
Each match joins the archive and moves your baseline. Rates stay grey until there are enough games behind them to be worth reading.
Kiriko24 gamesBusan19 games
Ana17 games
Widowmaker2 games, too fewOCR is not perfect, and OverAnalyzer has no access to Blizzard's data. Rank stays an estimate tracked forward from the last match you calibrated yourself.
One warning, and only on the GitHub download.
None of this applies to the web uploader, which is the path the three steps above describe. It applies to one thing: the optional Windows companion, downloaded as OverAnalyzer.exe from the public GitHub Releases page. That build is unsigned, so Windows may show "Windows protected your PC" and list an unknown publisher. Signing was not set up for the beta because it needs legal-entity identity validation and an ongoing subscription. The missing certificate is expected, but it is not a safety guarantee, which is why the checksum below is worth the minute it takes.
A Microsoft Store release is on the way, and it installs without this warning. Until it lands, GitHub Releases is the only download, and these are the steps.
- 1Open the
OverAnalyzer.exedownloaded from the official release. - 2On the "Windows protected your PC" dialog, select More info.
- 3Check that the app name is
OverAnalyzer.exe; an unsigned beta build shows Unknown publisher. - 4Select Run anyway. If the name or download source does not match, choose Cancel instead.
The link opens the releases page rather than downloading straight away, so you can read the notes and check the SHA-256 against the source before you run anything.
Microsoft Defender SmartScreen prevented an unrecognized app from starting.
Running this app might put your PC at risk.
In PowerShell, from the folder containing the EXE, compare this output with the SHA-256 published beside the same release. A locally computed hash is useful only when it matches a trusted published value.
(Get-FileHash OverAnalyzer.exe -Algorithm SHA256).Hash.ToLower()