| Season | Cap Ceiling | Equivalent Cap Hit | % of Cap | Share |
|---|---|---|---|---|
| Enter a salary above to build the table. | ||||
Cap Era 2005 to Present
The salary cap is rising at an unprecedented clip, so raw dollar figures are misleading. Enter any cap hit, pick the season it belongs to, and see what percentage of the cap it consumes and what the equivalent contract would have cost in every other season of the cap era.
| Season | Cap Ceiling | Equivalent Cap Hit | % of Cap | Share |
|---|---|---|---|---|
| Enter a salary above to build the table. | ||||
The saved table selects its twenty-twenty-five to twenty-six row by default, with an authored ninety-five-point-five-million-dollar ceiling. An entered twelve-million cap hit divided by that ceiling gives about twelve-point-five-seven percent. Six million gives about six-point-two-eight percent. Bars use thirty pixels per percentage point of the stored ceiling. This is arithmetic on saved table values, not a verification of current league limits, contract rules, prorated payroll or individual eligibility. The percentage compares cap allocation only and does not establish player value or purchasing power. For each table row the calculator multiplies the original cap-share fraction by that row ceiling. The stored two-thousand-five to six ceiling is thirty-nine million, so the twelve-million cap hit in the default row maps to about four-point-nine-zero-zero-five million in that earlier row. Bars compare that equivalent amount and entered twelve million at forty pixels per million dollars. Every row retains the same twelve-point-five-seven-percent share. This is proportional cap context, not consumer-price inflation adjustment or a claim that contract terms, league revenues and labor rules are economically equivalent across seasons. Keeping twelve million but selecting the stored thirty-nine-million ceiling makes the base fraction about thirty-point-seven-seven percent. Bars compare this with the default twelve-point-five-seven percent at fifteen pixels per percentage point. The source marks its twenty-twenty-six to twenty-seven and twenty-twenty-seven to twenty-eight rows projected; those are saved labels, not confirmation of announcements. The input parser accepts M and K suffixes and parse-float behavior, while invalid input returns before clearing earlier table and copy data. Native checks cover a valid six-M calculation and reset only. The explanation does not validate all historical values or full input and clipboard behavior.