Path of Building / DPS differences

Why PoE Ninja DPS and PoB DPS Differ

You import a build, the number drops by half, and something feels broken. Nothing is. The two figures were calculated under different assumptions against different targets, and the gap is entirely explainable once you know where to look.

Neither number is wrong. A damage figure is not a measurement, it is a calculation under stated conditions. Change the conditions and the figure changes, exactly as it should. The question is never which one is correct — it is which set of conditions each was answering.

Where the gap actually comes from

It is almost never one thing. A gap that looks dramatic is usually four or five modest differences stacking, each of which is individually reasonable. Broken out, the drop stops looking mysterious.

The same character, both figures reconciled Illustrative proportions

Five ordinary differences turn a hundred into twenty-nine. Not one of them is a fault, and not one of them would look alarming on its own. The drop only seems dramatic because you see the endpoints and none of the steps between.

Proportions are illustrative. Real contributions vary enormously by build — some builds are almost all buff uptime, others barely notice.

You are not comparing two calculations of the same thing. You are comparing two different questions that happen to produce numbers in the same units.

The five causes, roughly in order of size

Usually largest

Buffs and conditionals left off

The site's figure is generated with a standard configuration where the relevant buffs are treated as active. Your imported copy starts with conditionals unticked, because the tool cannot know what you keep up during a real fight.

For a build leaning on several stacking conditions this alone can account for most of the gap. For a build with none it accounts for nothing.

Large

Flask and charge assumptions

Flask uptime and full charges are assumed in the standard configuration and off in yours. Both are reasonable defaults for their purpose — one describes a build at its peak, the other describes it at rest.

Neither describes the average moment of actual play, which sits somewhere between them and is not a number either tool reports.

Moderate

A different enemy on the other end

Damage depends heavily on what you are hitting — its level, its resistances, whether it is treated as a boss. The site calculates against a standard high-level target so that every build is comparable on the same terms.

Your file may be pointed at nothing, at a different preset, or at settings you adjusted months ago and forgot. Same character, different target, different number.

Moderate

You are reading a different figure

Path of Building reports several damage numbers, and they are not interchangeable. Hit damage, damage including ailments, and combined totals can differ by a lot on the same character.

Comparing a hit-only figure against a combined one produces a gap that has nothing to do with configuration at all. This one catches experienced players regularly.

Small but common

A different main skill got selected

The ladder data does not state which skill a player considers primary; it has to be inferred from what is equipped. On import, your copy may default to a different skill in the list entirely.

If the number looks wildly wrong rather than moderately lower, check the skill selector before checking anything else. This is the same inference problem that causes characters to appear under the wrong skill in build overviews.

Which number are you even reading?

Worth spelling out, because "DPS" is not one figure and the labels are easy to skim past. Reading two different rows and calling it a discrepancy is the most avoidable version of this whole problem.

Damage figures that are not the same thing

Hit damage What a single hit deals, before anything that applies over time. Lowest of the figures on most builds, and the right one to compare if you are evaluating a weapon.

With ailments Adds damage that continues after the hit lands. On builds designed around this, it can be several times the hit figure — which is exactly why comparing across the two is meaningless.

Combined total Everything the character contributes at once, including sources that are not your main skill. Usually the largest number on screen, and the one people quote without noticing.

Effective against a target The figure after the enemy's defences are applied. Depends entirely on the configured target, and it is the only one that resembles what you experience.

Before concluding anything, confirm you are looking at the same row in both places. That single check resolves a surprising share of reported discrepancies, and it costs nothing.

Making the two agree

If you want a genuine comparison rather than a reassurance, this is the order to work through. Each step removes one contributor from the waterfall above.

Reconciliation checklist Top to bottom

Confirm the skill selectedBefore anything else. A different main skill explains a wild gap instantly and makes every other check pointless until fixed.

Confirm you are reading the same figureHit, with ailments, combined, or effective. Same row on both sides or the comparison means nothing.

Set the enemy configuration to matchLevel, resistances and boss setting. This is the single biggest lever in the configuration tab and the one most people never open.

Enable the same buffs and conditionalsWork down the list and tick what the standard configuration assumes. Expect the number to climb noticeably here.

Match flask and charge assumptionsThe last of the routine differences. After this the two should be close, and any remainder is worth investigating rather than ignoring.

When the gap is genuinely a problem

Almost never, but not never. Three situations where a difference is telling you something rather than reassuring you.

Worth investigating

The gap survives the checklist. If configurations match on both sides and a large difference remains, something in the import did not carry across — usually a gem, a jewel, or an item with a modifier the version you are running does not recognise.
Your version is significantly older or newer. Calculations change as the tool is updated. Comparing across versions compares two different models of the same game, and the difference is real rather than a setting.
The figure is higher in your file, not lower. The usual direction is downward. Upward often means you have enabled something the standard configuration deliberately does not assume, which makes your number the optimistic one.

What to do once they match

Then use it for what it is good at, which is comparison rather than prediction. A damage figure is excellent for telling you whether swapping one item for another improves things, and poor at telling you how a fight will go.

The important discipline is holding both sides of a comparison at identical settings. Once you do that, the absolute number stops mattering and only the difference does — and the difference is the only part that was ever reliable. The DPS difference calculator takes two figures and tells you whether the gap is large enough to be worth acting on, including flagging jumps big enough to suggest a configuration mismatch rather than a real improvement.

And when a figure assumes buffs you rarely hold, flasks you do not keep up, and a target you never fight, remember what it is describing: a ceiling. Useful for ranking options. Misleading as a promise. That distinction is covered further in common mistakes.

Parent guide Path of Building The full handoff from export code to a damage figure, and the three places it goes wrong. Tool DPS Difference Calculator Percentage, multiplier, and whether a difference is large enough to be worth the currency. Reading the ladder Build Data Guide What the sample includes, what it leaves out, and how funding distorts the top of it. Avoid these Common Mistakes Eleven misreadings ranked by how often they happen and how much they cost.