DPS Calculator: How to Maximize Damage Per Second

I was standing in a Discord call, staring at a damage log, and my “upgrade” was doing less DPS

I’d just swapped one weapon for another because the tooltip number was bigger and, honestly, I wanted to feel smart for five minutes. Then the raid dummy told me I wasn’t smart. My DPS dropped. Like… not a little. Enough that my buddy said “did you unequip half your gear?” and I had to pretend my mic was cutting out.

So yeah, if you’ve ever looked at a shiny new item and thought “bigger number = more damage,” you’re in good company.

Tooltips lie. Or, okay, they don’t lie—they just leave out the stuff that actually matters.

DPS is basically three knobs: how hard, how often, how reliably

The thing is, “Damage Per Second” sounds like one clean stat, but it’s really a messy pile of other stats wearing a trench coat. You can make a DPS calculator as fancy as you want, but under the hood it’s almost always some version of:

• Damage per hit (your base + scaling + buffs + crit multiplier stuff)
• Hits per second (attack speed, cast time, animation locks, reloads, whatever your game calls it)
• Uptime and accuracy (miss chance, dodge, downtime, target swapping, you getting knocked on your butt)

And yes, crit is in there too, but crit isn’t magic. Crit is just “sometimes you do more,” which means it’s a probability problem, not a vibes problem.

I had no idea what “expected value” meant at first. I nodded like I understood. I didn’t. Then I realized it’s just the average outcome if you repeated the same fight a ton of times (or if you’re staring at logs for an hour like a goblin).

That’s the “clean” version. Real builds get gross fast (DoTs, multi-hit skills, proc effects, armor reduction, resist caps, snapshotting… you know the usual nonsense).

The worked example I use when I’m sanity-checking gear (and my ego)

So let’s do numbers. Not “theoretical perfect sim” numbers—just something in the ballpark that helps you decide between two items without opening a spreadsheet that looks like a tax form.

Say your skill hits once per 0.80 seconds. That’s 1.25 hits per second. Your base hit is 1,200. You’ve got 30% crit chance, crits do 2.0x damage, and you land hits 90% of the time because the boss is slippery or you’re panicking or both. And your uptime is about 0.85 because you’re dodging mechanics (or reloading, or running back, or whatever your game does to waste your time).

Step 1: Average damage per hit (with crit)
Average multiplier from crit = (1 − 0.30) + (0.30 × 2.0) = 0.70 + 0.60 = 1.30
Average damage before accuracy = 1,200 × 1.30 = 1,560
Apply accuracy = 1,560 × 0.90 = 1,404

Step 2: Multiply by hits per second
Raw DPS (no uptime) = 1,404 × 1.25 = 1,755

Step 3: Apply uptime
Final DPS = 1,755 × 0.85 = about 1,492

And that’s your “real-ish” DPS. Not perfect, but good enough that you won’t get baited by a tooltip that ignores accuracy and uptime. Which happens constantly.

And yes, if your new weapon adds 10% damage but costs you 15% attack speed, you can now see why your DPS faceplants.

So why does everyone get this wrong?

Because games love showing you the one stat that sells items, not the one that wins fights.

Quick comparison table: what changes DPS the most (usually)

Here’s a little cheat sheet I keep in my head. It’s not law. It’s just what tends to matter when you’re min-maxing and you don’t want to re-spec 14 times.

One sentence I wish more people tattooed on their brain: multipliers multiply each other.

So if you can bump uptime and accuracy and speed a little, you can beat a “bigger hit” build that’s constantly whiffing or standing around.

How I use a DPS calculator to min-max without spiraling

Okay, so here’s the part where you actually get faster at this. Because the goal isn’t to become a human calculator. The goal is to make better decisions in 30 seconds than the average player makes in 30 minutes (and still have time to play the game).

I do it in passes:

Pass 1: Lock the rotation/skill pattern.
If your “build” changes how often you press things, you’re comparing apples to… like… a toaster. Keep the same rotation and compare gear inside that reality. If the new setup changes rotation, cool, but then you’re doing a different test.

Pass 2: Compute baseline DPS with boring honesty.
Use your real hit chance, your real uptime, and your real attack/cast time. Not the best-case. Not the “if I never mess up.” You mess up. I mess up. Everyone messes up (especially when the boss decides the floor is lava again).

Pass 3: Change one thing.
Swap one item or one talent and re-run the same math. If you change five things at once, you’ll never know what actually mattered, and you’ll end up keeping the wrong piece because it “felt good.”

Pass 4: Watch for caps and breakpoints.
This is where calculators earn their keep. Some games have attack speed caps, crit caps, cooldown breakpoints, or weird rounding where 1.99 seconds and 2.01 seconds aren’t “basically the same” at all. If your game has those, you want to aim for the breakpoint, not just “more.”

Pass 5: Sanity-check with logs.
If you can, look at a 2-3 minute parse. Not because logs are perfect, but because they expose the stuff your napkin math didn’t include—downtime, target swaps, missed shots, panic movement. Sometimes your “lower DPS” build wins because it’s easier to execute, and that’s not cope, that’s reality.

And yes, sometimes you do all this and the answer is “keep the old gloves.” It’s painful.

But it works!

If you want calculators that do the annoying bits without you re-deriving probability every time, I built a bunch of these for exactly that reason:

FAQ (stuff people DM me after they “definitely did the math right”)