Fantasy points per dollar is a simple way to measure fantasy value against salary. It answers a practical question: if a player costs a certain amount, how many fantasy points are you getting for each $1,000 spent?

You can use it to compare players across similar roles, separate ceiling from value, and look for efficient lineups. The idea is straightforward, but the result only makes sense if you use the same scoring system and salary format for every player.

What fantasy points per dollar means

This metric turns raw fantasy points into a salary-adjusted value. A player who scores fewer points can still be a better value than a more expensive player if the salary gap is large enough.

A calculator like this is based on a basic ratio:

Fantasy points per $1,000 = fantasy points ÷ (salary ÷ 1,000)

That can also be written as:

Fantasy points per $1,000 = fantasy points × 1,000 ÷ salary

If you want a broader view, some players also look at related value metrics such as fantasy points per $1,000 of salary, fantasy points per dollar, or projected value relative to price. The core idea stays the same: divide expected fantasy output by cost.

If you are comparing this with other player evaluation tools, a salary calculator helps with salary-based comparisons, while a Return on Investment ROI calculator uses the same general logic of return versus cost.

When you would use it

This calculation is useful whenever player prices matter as much as player projections. Common use cases include:

  • building DFS lineups with a fixed salary cap
  • comparing two players at the same position with different prices
  • checking whether a high-salary star needs a big projection to justify the cost
  • finding cheaper players who can support the rest of your lineup
  • ranking players by efficiency instead of only by raw projection

It is especially useful when you want to answer “Which player gives me more scoring for the money?” rather than “Who projects for the most points?”

The formula and method

The standard method is simple:

  1. Take the player’s fantasy points, usually a projection or actual result.
  2. Take the player’s salary.
  3. Divide fantasy points by salary in thousands.

In symbols:

Value = FP ÷ (Salary / 1,000)

Equivalent form:

Value = FP × 1,000 ÷ Salary

Where:

  • FP = fantasy points
  • Salary = player salary in dollars
  • Value = fantasy points per $1,000

Sometimes people say “fantasy points per dollar,” but they usually mean “per $1,000 of salary,” because the raw per-$1 metric produces very small numbers. For example, a player with 4.8 fantasy points per $1,000 is easier to compare than 0.0048 fantasy points per $1.

If you are using projected points, the result is only as good as the projection. If you are using actual points after a game, it becomes a retrospective efficiency metric.

For planning future lineups, this is often paired with future value calculations when you want to estimate how current salary and expected output translate into later value.

Worked examples

Example 1: mid-priced player

Suppose a player has a salary of $6,500 and is projected for 19.5 fantasy points.

Fantasy points per $1,000 = 3

That means the player returns 3.00 fantasy points per $1,000 of salary.

How to read it: for every $1,000 you spend on this player, you are getting about that many projected fantasy points. This is a direct way to compare with another player who may project a little lower but costs much less.

Example 2: cheaper value play

Suppose another player costs $4,200 and is projected for 13.8 fantasy points.

Fantasy points per $1,000 = 3.29

That returns 3.29 fantasy points per $1,000.

This player may look less impressive in raw points than a star option, but the value score can be stronger because the salary is lower. That is the kind of edge many users look for in DFS contests and lineup optimization.

Example 3: expensive star

Suppose a top player costs $10,000 and projects for 27 fantasy points.

Fantasy points per $1,000 = 2.7

The value is 2.70 fantasy points per $1,000.

Even with a large projection, the expensive salary can make the efficiency look modest. That does not mean the player is bad; it means you are paying for raw ceiling and floor, not just salary efficiency.

How to interpret the result

A higher fantasy points per $1,000 number means better salary efficiency. A lower number means you are paying more for each point of production.

That said, there is no single universal “good” number. The result only matters when compared with:

  • other players at the same position
  • the scoring format
  • your contest type
  • your roster construction goals

For example, a tournament lineup may tolerate lower value on one player if the upside is strong. A cash-game style build often prefers more efficient salary use across the lineup.

A useful habit is to compare both projection and value together. A player with strong value but a weak ceiling may not fit every contest, while a player with elite projection and only fair value may still be worth the salary.

Common mistakes to avoid

Mixing salary units

The most common mistake is dividing by the full salary amount without converting to thousands. If you do that, the result will be tiny and hard to compare. Always check that the denominator is salary divided by 1,000, or use the equivalent multiplied form.

Using different scoring systems

Fantasy points depend on the rules of your contest. A projection from one scoring format does not belong in a calculator built for another format unless the scoring is consistent.

Comparing unlike roles without context

A quarterback, running back, and kicker may all have very different value profiles. Even within the same sport, raw value scores should be interpreted alongside position, roster rules, and expected usage.

Treating value as the only goal

A cheap player with a strong value score is not automatically a better choice than a more expensive star. Salary efficiency matters, but so do upside, floor, role, and lineup fit.

Forgetting that projections can change

If your projected fantasy points are stale, the value score becomes stale too. Injury news, playing time, matchup, and usage changes can move the projection quickly.

What this metric does not tell you

Fantasy points per dollar is useful, but it is not a complete player evaluation. It does not directly measure:

  • variance or volatility
  • game script sensitivity
  • ceiling versus floor balance
  • correlation with teammates or opponents
  • roster scarcity at a position

A player can rate well on value and still be risky. Another player can look expensive on a per-dollar basis and still be a strong pick because of elite ceiling or stability.

If you want to estimate how a salary choice affects the rest of your build, you may also find a present value calculator useful in a general financial sense, because both tools focus on converting a current cost into a more usable comparison metric.

Practical way to use the result

A simple workflow is:

  1. Estimate or enter fantasy points using your scoring system.
  2. Use the player salary in dollars.
  3. Compare the value score with other options at the same position.
  4. Balance efficiency with projection and roster needs.
  5. Recheck after injury and lineup news.

If two players project similarly, the cheaper one usually has the stronger value score. If one player projects much higher, the more expensive option can still be the better play even with weaker per-dollar efficiency.

For a quick mental check, ask yourself whether the player’s projection is high enough for the salary tier. The calculator turns that question into a number you can compare directly.

For more background, see Wikipedia.

Frequently asked questions

What does fantasy points per dollar mean?
It measures how many fantasy points you get for each $1,000 of salary. It is a way to compare player efficiency across different price levels. Higher values mean better salary efficiency.
Why is it usually calculated per $1,000 instead of per $1?
Per $1,000 is easier to read and compare. Per $1 produces very small decimals that are harder to use in lineup decisions. The underlying ratio is the same either way.
What formula should I use for fantasy points per dollar?
Use fantasy points divided by salary in thousands: FP ÷ (Salary / 1,000). You can also write it as FP × 1,000 ÷ Salary. Both give the same result.
Is a higher fantasy points per dollar always better?
Usually yes for pure salary efficiency, but not always for lineup quality. You still need to consider ceiling, floor, contest type, and position. A more expensive player can be the better pick if their raw projection is much higher.
Can I use projected points or actual points?
Yes. Projected points are useful for building lineups, while actual points are useful for post-game analysis. Just make sure you know which one you are using, because the meaning changes slightly.
Does this work for every fantasy sport?
The ratio works anywhere you have fantasy points and salary, but the scoring rules must match the sport and contest. A point total from one format should not be mixed with salary from another unless the scoring is consistent. The method stays the same even when the sport changes.
What is the biggest mistake people make with this metric?
The biggest mistake is comparing values without checking the scoring context. A second common mistake is forgetting to divide salary by 1,000. If you keep the formula consistent, the result becomes much easier to use.

About this article

Written by Yahav Atia, WSO – the digital agency (wso.co.il) that owns and founded this site, with the help of AI, and passed automated quality checks before publication. Numbers in the worked examples were computed in code, not estimated.