How to Read a Warcraftlogs Report

The first time most people open a Warcraftlogs report, they see a wall of numbers, a dozen tabs, and a color-coded ranking they did not ask for. It is genuinely intimidating. But a WCL report is just a structured recording of everything that happened in a fight, and once you know which four or five views to look at, you can diagnose almost any performance problem in a couple of minutes. This guide walks through a report top to bottom.

The fight list

Every report opens on the list of fights — sometimes called pulls or segments. Each row is one attempt at an encounter: a boss kill, a boss wipe, or in Mythic+ a full dungeon run. The list shows the encounter name, the difficulty, the duration, and whether it was a kill or a wipe (with the boss health percentage at the time of the wipe).

The single most important habit when reading a log is to pick the right fight before you analyze anything. A wipe at 40% and a clean kill produce completely different numbers, and comparing across them is meaningless. If you are evaluating performance, start from a kill. If you are diagnosing why you wiped, open the wipe itself.

Damage Done

The Damage Done tab is where most people live, and it is the most misread page in the tool. The default column is DPS, but Warcraftlogs actually computes four damage numbers — DPS, rDPS, aDPS and nDPS — that distribute the value of external buffs differently. The ranking color you see on the right is based on the appropriate normalized metric for your spec, not the raw DPS column. If your meter said you topped the chart but your parse is mediocre, this tab is usually where the explanation lives. We cover this in depth in DPS, rDPS, aDPS and nDPS Explained.

Click any player to expand their ability breakdown. This is the real diagnostic view: it shows every spell they cast, how many times, the hit and crit counts, and what share of total damage each ability contributed. A rotation problem almost always shows up here as a filler spell doing far too much of your damage, or a core ability with far too few casts for the fight length.

Healing Done

The Healing tab works the same way but is even more deceptive, because raw healing rewards overhealing. A healer who blankets the raid with inefficient heals can post a huge number while a more precise healer who only heals real damage looks low. The expand view shows overhealing percentage per spell, which is the number that actually matters. There is a dedicated guide on this: How to Actually Evaluate a Healer.

The Deaths tab

Deaths is the highest-value tab in any progression report and the least used. For each death it reconstructs the final several seconds of that player's life: the damage events that killed them, the overkill amount, their health pool over time, and which defensive cooldowns were or were not active. It turns "why did I die?" from a guess into a fact. Reading death logs well is its own skill, covered in Reading Death Logs to Stop Dying.

The timeline and the Replay

The timeline view shows the fight as a horizontal track: boss ability casts, phase transitions, raid cooldowns, and deaths all laid out against the clock. This is how you check cooldown alignment — whether the raid's burst windows actually landed on the boss's vulnerable phase, or whether half the raid blew cooldowns ten seconds before a phase change and had nothing left when it mattered.

The Replay (sometimes called the pin or map view) plays the fight back as dots moving on the encounter floor. It is the fastest way to see positioning problems: who stood in the wrong spot, who was late to a stack, who was clipping the melee with a spread mechanic. For mechanically complex fights it answers questions no numeric table can.

Buffs, Debuffs and Casts

The Buffs and Debuffs tabs show uptime on everything that ticks: your personal damage buffs, the boss's damage-amplification debuffs, raid consumables, and crowd-control durations. A surprising amount of lost damage is just a personal buff sitting at sixty percent uptime when it should be near a hundred. The Casts tab is the raw cast log — useful when you want to verify exactly when something happened rather than how much it did.

These uptime tabs are also where you confirm the boring things that win fights: did everyone have flasks and food, did the prepot go out, was the damage-taken cooldown rotation actually executed. None of that shows on the DPS column, and all of it decides progression.

A practical reading order

When you open a report, a fast and reliable order is: pick the correct fight, glance at Damage and Healing for the shape of the pull, open Deaths to see what actually went wrong, check the timeline for cooldown alignment, and only then expand individual players to dig into rotations. Most players do the opposite — they stare at the DPS column first and draw conclusions from the one number that is hardest to interpret in isolation. Reverse that order and a log stops being intimidating and starts being useful.

If you want a shareable summary of a fight rather than a deep dive, ParseCard reads the same report data and turns it into a recap card — see how that works. Next, learn what actually counts as a good parse.