Warcraft Logs is the closest thing WoW has to a universal report card. Anyone who raids past LFR, pugs Mythic+, or applies to a half-serious guild has been pinged for their logs at some point. Most players know the colors and not much else. They glance at a yellow parse, blame the tank, and close the tab.
That is the cheap way to use it. The real value of Warcraft Logs is the second click, the third click, the timeline scrubbing that tells you why phase two went sideways. This guide covers what every panel actually means, how to find the mistake that lost you 8 percent damage on Mythic prog, and how to upload your own logs without anyone in your guild having to teach you.
What Warcraft Logs Actually Tracks
Behind the colored parses is a packet-by-packet record of every event in your raid. Every cast, every cooldown, every absorb shield, every flame patch your hunter ate on purpose. The site sits on top of the combat log file your client writes locally during a fight. Someone in raid runs an uploader, that file gets parsed server side, and you get a public report.
The important thing to understand: a parse is not a measure of how hard you tried. It is a measure of damage or healing per second across one fight, ranked against everyone else of your spec who killed the same boss on the same difficulty during the current ranking window. If your guild kills a boss in 5 minutes and the world record kill was 3, your number is fighting a boss for 2 extra minutes of execute phase you never reached.
The Parse Colors, In Plain English
Every parse is a percentile from 1 to 100. The colors are just thresholds:
Grey (1 to 24): bottom quarter. Something is off, usually rotation or uptime.
Green (25 to 49): below average. Often a gear or talent issue, sometimes a fight you stood in too much fire on.
Blue (50 to 74): average to above average. The big middle bucket.
Purple (75 to 94): high. You know your spec.
Orange (95 to 98): top of your spec for this kill window.
Pink (99): pretty much the best players of your spec.
Gold (100): a server first or raw all-stars parse, very rare in pug groups.
One parse is not a verdict. A single Mythic+ kill or one boss attempt can swing two colors purely on RNG. Look at five to ten parses across different fights before you make a call on a player.
The Two Numbers People Confuse
Warcraft Logs shows two parse numbers side by side, and people argue about them constantly in guild Discord. They measure different things.
Parse (also called rDPS or Historical): ranks your damage including external buffs your group provided to you. If your warrior popped Skull Banner on you, the boost shows up in this number. It rewards being in a stacked group.
Ranking by aDPS (Adjusted): strips out the value of external buffs you were given. This is the number most class theorycrafters look at because it measures what your own keys did.
Both are useful. If your raid leader is grading you on contribution to the kill, parse is the right number. If you are trying to find your own mistakes, switch to aDPS or "All-Stars" rank instead.
The Four Tabs That Fix Most Damage Problems
Open a single boss report and you are looking at maybe twelve tabs and twenty filters. You do not need them all. These four cover almost everything that drops a parse.
1. Damage Done
Open Damage Done, click your name, and look at the ability breakdown. Are your highest-damage abilities in the right order? Is a filler dealing more than a flagship spender? If you main Frost Mage and Ice Lance is your top spell, something is wrong with your shatter setup. If you main Frost DK and Obliterate is below Frost Strike, you are runic-power capped. Use the Frost DK BiS in War Within Season 3 guide for a current rotation reference.
2. Casts
The Casts tab is where lazy parses get exposed. You can see exactly how many times each cooldown went out, how many GCDs you wasted standing still, and whether you actually used your trinket on cooldown. Most parses below blue have at least one major cooldown that was used three fewer times than it should have been.
Quick test: take the fight length in seconds, divide by your major cooldown's cooldown length, and that is roughly how many casts you should see. If your two-minute window cooldown shows up twice in a five minute fight, you left one in the tank.
3. Buffs
The Buffs tab tells you the uptime on every dot, debuff, and self-buff you maintained. For most damage specs, the difference between a green parse and a purple one is just uptime on three or four key things. If your Mastery proc is only up 40 percent and the top parser has it at 78 percent, you found the gap.
4. Timeline
The Timeline view is the most underused tab on the entire site. It draws every event for your character as a horizontal track. Long blank gaps are dead GCDs. Stacked icons at the wrong moment are wasted cooldowns. Look at a top parser's Timeline next to yours and the difference is often visible without reading a single number.
How to Find Your Own Mistakes Without a Coach
The trick is to compare yourself to yourself, then yourself to the rank one. In any report:
Open your parse on a fight where you played well, and a parse from the same week where you played badly.
Open Casts on both. Lay them side by side.
Count your major cooldown usage. Almost always, the bad parse has one fewer.
Open Buffs on the bad parse. Look for any maintenance buff with under 90 percent uptime that was at 95 plus on the good one.
Then open the top-ranked parse for the same fight, same difficulty, same spec. Compare their Casts to yours. If they used a cooldown in pull seconds 12, 75, and 138 and you used yours at 8, 90, and 175, that delay is your first homework item.
This whole loop takes ten minutes and beats two hours of guesswork on Reddit.
Reading Healing and Tanking Logs
Healers and tanks have their own ranking systems. Healers parse on HPS, with separate ranks for absorb shields and overhealing. A 99 parse with 60 percent overhealing is real, but it is a flag that you may be pre-shielding more than the fight needs.
For tanks, the Damage Taken tab is the one that matters. Look for physical damage spikes between active mitigation windows. If your Ignore Pain or Shield of the Righteous uptime is below 80 percent on a heavy melee boss, your healers are paying for it.
How to Upload Your Own Logs
The Warcraft Logs uploader is a small desktop app. Install it once, point it at your WoW Logs folder, and run it during raid. After the raid you click a button and the report uploads.
Before your next raid:
Open WoW. Type
/combatlogat the start of every raid. Or install the AutoCombatLog addon and forget about it.Download the Warcraft Logs Uploader from the official site.
Sign in, set your WoW directory, and choose live logging if you want kills to appear during the fight.
After raid, hit upload and share the report link in your guild Discord.
Live logging is the best feature for prog. Your raid leader can watch the report update boss by boss and call out who is missing buffs without alt-tabbing.
Warcraft Logs for Classic, MoP Classic, and Hardcore
The site supports every active WoW version. Classic Era, Season of Discovery, Mists of Pandaria Classic, Cataclysm Classic, and Hardcore all have their own rankings tab. The site filter at the top of every report controls which version you are viewing.
A few quirks worth knowing:
MoP Classic rankings reset on every patch. A purple parse from prepatch will not count for the current tier.
Hardcore logs include a deaths tab that is more important than DPS. If you raid Hardcore, the Deaths tab on a boss is the one your guild master is going to open first. See our Hardcore Shaman leveling guide for how positioning habits formed in leveling carry into raid logs.
Season of Discovery rankings are split by phase and rune build. Apples to apples comparisons only work inside the same phase.
Looking Up Other Players' Logs
The fastest way to scout a raid applicant or a Mythic+ pug leader is to drop their character name into the search at the top of Warcraft Logs. You get every recent report they appeared in, ranked by parse. Combine that with the broader WoW Character Lookup workflow and you can vet a player in under 60 seconds.
Things to watch for when scouting:
Recency. A purple parse from two seasons ago is not the same player. Look at this season only.
Sample size. One Mythic kill at 95 means less than fifteen kills averaging 70.
Hidden logs. Some players hide their reports. That alone is not a red flag, but combined with a wiped Raider.IO profile it usually means they had a bad week somewhere.
What Warcraft Logs Will Not Tell You
The site has limits worth respecting. It cannot tell whether you took an interrupt assignment, whether you swapped to the priority add, or whether you stayed silent when your raid leader needed callouts. Plenty of 99 parsers are nightmares to raid with, and plenty of blue parsers are the glue holding the roster together.
Logs are a tool for catching mechanical mistakes, not a personality test. Use them to fix your rotation, not to decide who you respect.
Bottom Line
If you open exactly four tabs in any report, in this order, you will fix 80 percent of your mistakes:
Damage Done, sorted by ability.
Casts, compared to a top parser on the same fight.
Buffs, looking for any maintenance window under 90 percent.
Timeline, scanning for blank gaps and stacked cooldowns.
The rest of the site is great for guild officers and theorycrafters. For the average raider trying to climb out of grey into blue, the four tabs above plus an honest comparison to one top parser per week is enough to move two colors in a tier.
Once your parses start climbing, the next bottleneck is usually gear and consumables. Our Best WoW Gold Farming Spots guide covers how to fund your raid week without grinding for hours.