How to Read WoW Combat Logs — A Beginner's Guide That Actually Makes Sense

"Just check the logs," your raid leader says, as if reading WoW combat logs were as natural as opening your bags. So you open the link and find a timeline, numbers everywhere, tabs you don't recognize and graphs heading in directions that may or may not mean something. You click around for 30 seconds, absorb nothing, close the tab and type "yeah looks fine" in Discord.

Nobody teaches this part. This beginner's guide does: what to look at, in what order, and what it means for how you play, with every piece of jargon explained along the way.

What a combat log actually is

When you enable combat logging in WoW, the game writes a text file, WoWCombatLog.txt, that records every event in combat. Every cast, damage number, heal, buff, death and interrupt is in there, for every player, with timestamps down to the millisecond.

Nobody reads that file directly. It runs to millions of lines of comma-separated data, which is why parsing tools exist to turn it into something visual. Most players use one of two. WarcraftLogs is the industry standard, a deep and detailed toolkit; think of it as the Photoshop of log analysis. WowCoach is built for readability and AI-powered answers, the "explain it to me like I'm tilted at 1 AM" option.

Both read the same data and present it differently, and everything below applies to either. (For a full side-by-side that includes WoWAnalyzer, see WarcraftLogs vs WoWAnalyzer vs WowCoach.)

How to read a combat log in 5 minutes

A parsed log throws a lot at you at once. This is the order that matters.

Step 1: Deaths

Always start here. Deaths are the most consequential events in any fight: in a Mythic+ key, one can start a cascade that depletes the run, and in a raid attempt it is usually the beginning of a wipe. Before you look at who did the most damage, look at who died.

Three questions do most of the work. Who died first? That death almost always started the chain reaction. When did they die? A death at 0:30 suggests a mechanical failure, while one at 4:00 in a 4:30 fight might come from accumulated damage pressure. And what killed them? Click the death to see the damage sequence and decide whether it was a one-shot mechanic, a slow bleed or avoidable damage they stood in.

If nobody died, move on to Step 2. If several people did, trace the deaths in order to find the root cause. Survival comes first; there is no point optimizing a player who spent the last minute on the floor.

Step 2: Damage done

Now the scoreboard: total damage by player, highest to lowest.

Look for DPS players well below the rest. A gap of 10-15% between DPS is normal across different specs and fights; a gap of 30%+ means something is wrong. Compare DPS (damage per second) rather than total damage, since longer fights naturally produce bigger totals. And check the tanks. In Midnight, tank damage matters more than ever, and a tank doing half the DPS of another tank of the same spec is worth a look.

Don't obsess over who is #1. That player may be padding (hitting targets that don't matter) or ignoring mechanics. The damage summary is a starting point, not a verdict.

Step 3: Healing done

The same idea, with caveats. If one healer is far ahead of the others, the other healer may be underperforming, or the leader may be sniping heals; context decides. Overhealing (healing that lands on full-health targets) above 30-40% suggests heals are going to waste. And in Midnight especially, healers should be contributing damage during downtime. A healer doing zero damage is leaving value on the table.

Step 4: Mechanics

Most log tools break down boss-specific mechanics: who soaked what, who interrupted what, who stood in what.

Start with interrupts. If one player has 12 kicks and another has 0, that is a problem, and it raises the whole group's damage taken. Then avoidable damage, which most tools flag; players who take a lot of it are creating work for their healers. Finally, assignments. Did the assigned soaker actually soak, and did the tank swap happen on time?

Step 5: Cooldowns

This is where logs earn their keep. You can see exactly when every player used their major offensive and defensive cooldowns.

For DPS cooldowns, check whether they went out on pull, lined up with Bloodlust and were used often enough. A 2-minute cooldown used only twice in a 6-minute fight is a missed use. For defensives, check whether they were pressed in dangerous moments or sat unused while the player died, the single most useful thing to look for in a death recap. For healers, check whether raid cooldowns were staggered or whether two healers spent their big ones on the same damage event.

Mythic+ logs and raid logs

The two read differently, and you should look for different things.

In Mythic+, start with the route: how many pulls, how long each took and where the time went. Then deaths and battle rezzes, since every death costs time and the question is whether it was preventable. Compare trash damage with boss damage, too. Some players pump bosses and coast on trash, and in M+ trash often matters more because that is where most of the clock goes. Finally, interrupts per player. In a 5-person group every missed kick hurts, so check who is carrying the rotation.

In a raid, count pulls and ask whether the wipes are getting closer to a kill (progress) or staying flat (stuck). Look for death patterns, such as the same person dying first on every pull. Check phase performance: a group that is clean through phase 1 and falls apart in phase 2 knows where to focus. And look at raid cooldown coordination, from staggered healing cooldowns to DPS cooldowns lined up with boss vulnerability windows.

Common mistakes when reading logs

The first is reading only the DPS rankings. The top player may be ignoring mechanics, padding on irrelevant targets or riding externals like Power Infusion. Always check the context.

The second is comparing different specs. A Destruction Warlock and a Subtlety Rogue have completely different damage profiles, so comparing their raw DPS tells you nothing. Compare players with others of the same spec; WarcraftLogs percentile rankings are useful for this (here's what those parse scores mean).

The third is skipping the timeline. Summary numbers are averages. The timeline tells the story of the fight: when damage spiked, when people died, when cooldowns went out. Two players with identical DPS can have completely different timelines, one steady throughout, the other with a massive burst window followed by a long coast.

The fourth is over-reading one bad pull. Everyone fat-fingers a rotation or gets unlucky with a mechanic now and then. Look at trends across pulls and ask whether the same mistake keeps coming back.

The fifth is never opening your own logs. Critiquing teammates is easy. Checking your own deaths, uptime and cooldown usage is harder and far more productive, because your own play is the part you control.

If you'd rather not learn all this

That is a reasonable position, and it is why WowCoach exists. (It's also why we think the manual log-review workflow is dying: AI review handles the boring 80% so you can focus on the 20% that's actually interesting.)

Upload your log to WowCoach and, instead of navigating tabs and timelines, ask a question in plain words, such as "Why did we wipe?", "What killed me on the third pull?" or "Am I using my cooldowns at the right time?" You can also ask who took the most avoidable damage, or how to raise your DPS on a given boss.

The coach reads the same data as WarcraftLogs, every event, timestamp and ability. Instead of handing you graphs and tables to interpret, it answers in plain English, with specifics and timestamps, and the occasional well-deserved roast.

You don't need to become a log expert to learn from your combat logs. Enable logging, upload and ask. You can also connect WowCoach to Claude or ChatGPT and ask "why did we wipe on the last pull?" from there. Here's a WoW raid analyzer you can talk to, with real Mythic examples.

Frequently asked questions

Do I need to learn WarcraftLogs to be a good player? No. You need to learn from your mistakes, and logs are the best tool for that, but you don't have to become a WarcraftLogs expert. Tools like WowCoach let you ask questions in plain English and get specific answers.

How often should I review my logs? After every progression raid night, spend 5-10 minutes on deaths and wipe causes. For farm content or M+, review when something goes wrong or when you're pushing performance. You don't need to analyze every pull. (For a structured pass over a whole raid night, see how to review your raid night in 10 minutes.)

Can I read logs on my phone? Yes. WarcraftLogs and WowCoach both work in mobile browsers. With the WowCoach Desktop App, your logs upload automatically, so you can review on your phone between pulls without alt-tabbing.

What's the minimum I should look at after a raid night? Deaths: who died, when and what killed them. If you only have 2 minutes, that is the highest-value information in any log. Everything else is optimization.

My logs show I'm doing less damage than WoW's built-in meter. Why? The native damage meter and the combat log can differ slightly because of timing, absorb shields and how damage events are recorded. The combat log is the authoritative source, and it's what WarcraftLogs, WowCoach and every other external tool reads. Trust the log.

---

WowCoach.gg turns combat logs into plain-English analysis. Upload a log and ask about your performance, no log-reading expertise required.