World of Tanks Replays
Upload your .wotreplay and we parse the battle — match results, engine WN8, and how your damage compares to the tank's expected. The one place the Wargaming API can't reach: your individual battles.
A .wotreplay file is the battle itself — every packet the client received. That is strictly more information than the Wargaming API exposes, which only reports per-account totals.
- Match result and full scoreboard
- Both teams, every player, their vehicle, damage, kills and experience — reconstructed from the battle results packet, not from the client UI.
- Damage, assist and spotting split
- Direct damage is separated from damage dealt by allies on your spots and on your tracks. The in-game after-battle screen merges the two, so a high-assist scout looks weaker there than it actually played.
- Engine WN8
- Recomputed from the replay itself using current XVM expected values, so it reflects the battle you actually played rather than a running account average.
- Damage versus expected
- Your damage against the tank's expected damage for its tier and class — the single most useful number for deciding whether a battle was genuinely good.
The after-battle screen shows what the client believed at the moment the battle ended. A replay is the authoritative record, so three things routinely disagree.
Assist is attributed differently. The client credits assist to whoever last spotted a target; the replay carries the full spotting chain, so shared spots resolve more accurately.
WN8 is not the account figure. Per-battle WN8 uses that battle's damage, spots, frags, defence and win outcome. It is normal for a single strong battle to score far above the account average shown on a leaderboard. See how WN8 is calculated for the formula.
Expected damage moves.Expected values are re-published as the population's performance shifts, so a replay parsed today can score slightly differently from the same replay parsed a year ago.
Most replay sites are archives. They store the file and list what the client already wrote into it — damage, frags, a WN8 figure — so you can sort the table and find a big battle. That is a good way to find a game worth watching. It is not a way to understand one.
A number needs a baseline.Four thousand damage in a Tier X tank destroyer and four thousand in a Tier 6 medium are not the same battle, but a listing sorted by damage ranks them identically. Every replay here is scored against the expected damage for that vehicle's tier and class, so the figure means something on its own.
The summary is not the battle. A .wotreplay holds every packet the client received, not only the totals written at the end. We read the spotting chain to separate the damage you dealt from the damage allies dealt on your spots and tracks, and rebuild the scoreboard for both teams from the battle results packet. Those splits are in the file whether or not a site reads them.
Nothing stops you using both. Upload a replay you found elsewhere and it parses here exactly the way your own does.
Replays are saved to a replays folder inside your World of Tanks install:
C:\Games\World_of_Tanks_NA\replays\
The folder suffix (_NA, _EU, _ASIA) follows the region selected in the header — swap it if your install lives elsewhere. If the folder is empty or missing, recording is switched off — enable it in Settings → General → Record battle replays, then play one battle and it will appear. Files are named by date, map and vehicle, so the most recent battle is the last one alphabetically.
Replays are tied to the client version that produced them. After a patch, old files still upload and parse here, but the in-game viewer will refuse them.