Guide
Upload a WoW combat log
Drop WoWCombatLog.txt on the dashboard and get a report for the raid night a few seconds later.
The whole workflow is sign in, drop the file, read the report. No addon, no Warcraft Logs account, and nothing to wait for. The file is on the logger's machine already.
What you need
- A Logbreakdown account: sign in with Discord and you are in. Reading a report needs no account, only uploading does.
WoWCombatLog.txtfrom the game's Logs folder, written with advanced combat logging on. The logging guide covers both.
1. Open the dashboard
Sign in and you land on the dashboard. Upload a log at the top opens the box that takes the file — or drag the file anywhere onto the page and it opens itself. Both fields are optional, and both can be changed after the upload.
| Field | What it does |
|---|---|
| Title | The heading of the report and the title of the Discord post. Left empty, the night is named after the instances in the log and the date, like MH, BT · Thu, 5 Sept 2026. |
| Team | Which team the night belongs to, including one you were invited to. A team carries the Discord webhook and the CLA lists, so pick one if you want the link posted, and the night counts on the team's attendance page. Leave it on No team and the report is the same report. Teams are set up under Raid teams. |
There is no third field for who may read it. Every report is public: anyone with the link can read it, it is listed on the site, and search engines may index it. The only way to take a night down is to delete it. More under sharing.
2. Drop the file in
Drag WoWCombatLog.txt onto the box, or click it and pick the file. The box then shows four steps with a clock on each, so you can see which one is running and how long it has been running:
- Checking the file. The browser reads it and asks whether this exact log is parsed already. If it is, the upload and the parse are skipped and the report opens straight away.
- Uploading, with a percentage, the speed and the time left. This is your connection and the file size, nothing else. The machine parses one log at a time, so this step starts by saying how many logs are ahead of you; your file stays on your computer until it is your turn. Cancel stops it.
- Building the report. Parsing a full night takes a couple of seconds; a long night with many pulls takes longer, and the clock keeps running so you can tell it apart from a hang. Leave the tab open.
- Saving the report. Then it opens.
A file that cannot be a combat log — an archive, a screenshot, an empty file, one over the size limit — is turned away before anything is sent, and says why.
If the team has a Discord webhook, the link is posted as the report opens.
A night with more than one raid
Many guilds run Gruul, Magtheridon and Karazhan on the same evening, or Hyjal and Black Temple. Logbreakdown finds every instance in the file and makes one report per raid, plus a page for the whole night. The Fights menu at the top switches between them and lists every boss under its raid; a one-raid log has the same menu without the Whole night group. The dashboard lists the instances with their own links.
When the team's Discord setting is Ask me after upload, the last step asks whether Discord gets one message for the night or one per raid. Not posting at all is a choice too.
Deleting a night
The bin at the end of a row on the dashboard removes the night: the report, its instance pages and the parsed log, all at once. The same is under Settings on the report itself. Links to it stop working the moment it is gone, and the upload does not count back against the weekly limit.
Limits
| File size | Up to 500 MB. A full night is well under that. |
| Uploads | 5 an hour and 15 a week per account, including files that are not a combat log, unless an admin raised it. Three raid nights a week fit with room to spare. |
| The same file twice | Recognised by its content before it is sent, so it is neither uploaded nor parsed again. The report opens straight away, and it does not count towards the limit. |
| One at a time | The machine parses one log at a time. If several people drop a file at once, they wait in line and the upload starts when it is their turn. |
If the upload fails
| Message | What it means |
|---|---|
| File is too small to be a combat log | Logging was not on. Type /combatlog before the first pull next time. |
| This is not a WoW combat log | The file is not a combat log. Drop WoWCombatLog.txt from the game's Logs folder, not a screenshot or a random text file. |
| This is not a TBC Classic combat log | Retail, Classic Era and other expansions are not supported. Anniversary TBC realms are. |
| This file has no combat events | The header is there but nothing was fought. Logging may have been turned on after the raid, or the file was emptied. |
| Too many logs are waiting to be parsed | The line is full. Wait a minute and drop the file again. |
| Another log is being parsed | The parser was busy when the file was sent. Drop the file again and it will wait in line. |
| Sign in first | The session ran out. Sign in again and drop the file again. |
| Upload limit | One of the limits above. The hourly one clears itself. |
| Could not reach the data service | The parser is down, or the upload was cut off. Try again in a minute. If it stays down, use Report a problem in the account menu. |
| The report opens, but Gear is empty | Advanced combat logging was off. It is a one-time setting, turn it on. |
Logbreakdown parses TBC Classic logs, Anniversary realms included. A file from Retail or Classic Era is not supported.
Next: share the report.