⚔️ PoE Attack Speed Calculator
Model weapon APS, increased and reduced attack speed, more and less multipliers, action speed, dual wield bonus, skill attack time overrides, repeats, warning bands, and DPS windows.
| Preset | Setup | Base APS | Speed idea |
|---|---|---|---|
| Cyclone Claw Raider | Dual avg | 1.95 | Action speed stack |
| Flicker Strike Slayer | Single sword | 1.85 | High increased speed |
| Lightning Strike Champion | Single claw | 1.90 | Balanced hit rate |
| Tornado Shot Deadeye | Bow | 1.55 | Projectile uptime |
| Boneshatter Slayer | Two-handed mace | 1.35 | Slower heavy hits |
| Molten Strike Juggernaut | Single sword | 1.75 | Repeating events |
| Weapon type | Slow APS | Fast APS | Planning note |
|---|---|---|---|
| Claw or dagger | 1.50 | 2.10 | Good for high APS scaling |
| One-handed sword | 1.40 | 2.00 | Flexible melee baseline |
| Bow | 1.20 | 1.85 | Projectiles add event load |
| Two-handed axe | 1.15 | 1.55 | Bigger hits, lower APS |
| Two-handed mace | 1.05 | 1.45 | Often slow but heavy |
| Shield attack | 1.20 | 1.80 | Skill rules may override |
| Layer | Input field | Formula use | Common check |
|---|---|---|---|
| Weapon APS | Main/off APS | Base rate | Tooltip already local? |
| Inc/Reduced | Inc minus reduced | Additive bucket | Do not multiply each line |
| More/Less | More 1, more 2, less | Multiplicative | Read exact wording |
| Action speed | Action speed change | Final multiplier | Separate from attack speed |
| Dual wield | Dual bonus | More style layer | Dual modes only |
| Final APS | Status | Likely bottleneck | What to inspect |
|---|---|---|---|
| 0-3 | Normal | Attack feel | Weapon base and skill time |
| 3-8 | Fast | Mana and accuracy | Sustain and hit chance |
| 8-15 | Very fast | Resource use | Mana, rage, charges |
| 15-30 | Extreme | Animation and events | Repeats and on-hit load |
| 30+ | Tick watch | Timing quantization | Server tick style limits |
| Input | Meaning | Result affected | Planning risk |
|---|---|---|---|
| Repeats per use | Extra attack events | Hit events/sec | On-hit overload |
| Repeat efficiency | Average repeat damage | DPS estimate | Overstated repeats |
| Hit chance | Accuracy or connection | Real DPS window | Missing fast attacks |
| Damage uptime | Time actually attacking | Total window damage | Boss movement phases |
| Warning cap | Chosen APS line | Status message | False breakpoint comfort |
Path of Exile’s attack speed is not “just” about damage output, however. It is also about the generation of resources and it is about rhythm. Your screen should either be a video game or a glitching spreadsheet, your choice.
While numbers may appear huge on paper, the way you stack up multipliers can mean the difference between flowy melee build and slow one. The first step is that most people is doing the wrong math for speed. They have a gem that gives them more attack speed. A tree node that gives them more attack speed. Dual wielding gives them more attack speed. Then they attempt to add it all up in their head.
Why Attack Speed Is Not Just About Damage
But you can’t just add those up, the game breaks that out into different buckets. Reduced and increased mods combine additively. Less and more multipliers stack into their own silos then multiply at end. Unless you understand how those layers work, you will be way off on your theorycrafting before you even log in. The above tool takes care of that separation for you so you can spend your time understanding the tradeoffs rather than the math.
And then there’s the little trickster: speed of action. The animation is timed based off this mechanic, not the base attack speed stat itself. Your click feels snappier but that doesn’t mean you’re triggering more of your on-hit effects. You would only trigger more if you pass a certain attack-rate threshold and change enough to reach it. That can make a big difference for builds that rely on mana regeneration per hit, curses, or other on-hit triggers.
Visuals may suggest you are destroying enemies with style, but your actual damage stays the same while you wait for next full attack cycle to begin.
Dual wielding adds a level of complexity. Wielding two weapons at once gives you a multiplicative bonus to attack speed, but only when you’re hitting with them (or using skills that also scales off of dual wield properties). One common mistake is aiming for the highest theoretical attacks per second without factoring in mana cost. Attacks that go up faster eat up resources faster. If you have a build where you spend more mana on each swing then you generate from life and dedicated nodes, you’ll be out of juice in mere seconds even if your attacks per second number looks good.
Attack speeds push server tick rates too. The game can only handle so many separate events before it starts dropping hits and becoming unplayable due to lag. Chasing extreme numbers has diminishing returns because the engine can only cleanly register each individual impact up until a certain point.
Instead of looking solely at raw speed, experienced players is looking at hits per second. Can I get enough resources to continue swinging? Can I maintain accuracy while fighting moving bosses? Can I stay in play long enough to deliver an attack? These factors are all things to weigh in favor of either a slower weapon with more base stats, or a quicker weapon with less damage.
Occasionally, that extra speed lets you hit certain breakpoints. It can also trigger a support gem to let you reach another big power spike. Other times it just uses too much mana and the build won’t be viable for long duration battle. If you want to know the real bottleneck for your build, you’ll have to simulate it with exact values. You must also use repeat times and uptimes to know where it stands. You should of used them.
By including some reference data with their calculator, it also places those decisions within the normal range of values for each type of weapon, skill preset, etc. This explains why certain weapons is inherently faster than others (claws vs. Axes) while pointing out that raw speed isn’t everything; it’s a multiple over your expenditure.
How fast do you want things? It should be fast enough to be responsive and produce the resources you need smoothly, but not so fast that it breaks the game or the moddern game engine itself. That sweet spot is where a janky series of animations becomes a fluid, deadly routine that feels just right as soon as your fist makes contact.
