← Analyse a single pull

What repeats across many kills

One pull says how that pull went. Many pulls say which of the faults are habits. Name a character and a time frame, and this page measures every kill it can find in the window.

Sign in to WarcraftLogs

Sign in with your WarcraftLogs account to read your logs, including private and archived ones. You sign in on WarcraftLogs' own page — this one never sees your password, and there is nothing to paste.

First, register your own API client

WarcraftLogs meters its API per client, so this app cannot sign you in with one of its own — everyone using it would share a single hourly budget and run each other out of it. Registering your own takes about a minute and gives you a budget nobody else spends.

  1. Open warcraftlogs.com/api/clients and choose Create Client.
  2. Give it any name. You will see it on the consent screen when you sign in.
  3. Paste this as the redirect URL, exactly as it appears — a URL that differs by so much as a trailing slash is refused, and the refusal blames the client id rather than the URL.
  4. Tick Public Client so the client can use PKCE, then save.
  5. Copy the client ID it gives you back and paste it below. Not the client secret — this app has no use for one and should never be given it.

The client ID is kept in this browser so you do not have to paste it again, and unlike your access token it survives closing the tab. It is not a secret — PKCE publishes it with every sign-in — and it goes nowhere but warcraftlogs.com.

Name the character and the time frame

Sign in above first. The sweep reads your own logs with your own API budget.

There is no server, no cookies and no analytics. Nothing is stored except your token, and only until this tab closes. If you open DevTools → Network while it runs, you will see this page's own assets, POSTs to warcraftlogs.com, and spell icons from Wowhead's image host — the icon requests carry no token, no report code and nothing else.