Percentage Decrease Calculator

What this calculator does

This calculator works out the percentage decrease between two values — how much one number has fallen compared to another, expressed as a percentage of the original. It also runs the reverse workflow: given a starting value and a percentage to apply, it tells you the resulting smaller value. Both modes show the calculation step by step so you can copy the figure, or copy the reasoning, into a report or a spreadsheet.

How to calculate percentage decrease

The formula is:

percentage decrease = ((old value − new value) ÷ old value) × 100

Three steps in plain language: subtract the new from the old to get the absolute drop, divide by the old value (the base against which the loss is measured), then multiply by 100 to express the result as a percentage rather than a decimal.

The single most common mistake on this calculation is dividing by the new (smaller) value instead of the old one. Both percent-increase and percent-decrease use the same denominator: the starting value. The reason is simple — the question is “what fraction of where I started did I lose?”, and the starting point is the only fixed reference. If you divide by the new value, the denominator depends on how far you fell, which makes the answer self-referential.

Worked example

A pair of sneakers cost $80 last month and is on sale for $60 this month. The percentage decrease is:

Note that dividing $20 by $60 (the new price) gives 33.3 %, which is a common but incorrect result. The sneakers were marked down 25 %, not 33 %.

Three more for reference:

• Headcount falls from 200 to 180 → (20 ÷ 200) × 100 = 10 %.
• Revenue falls from $1.2M to $1.05M → (150 000 ÷ 1 200 000) × 100 = 12.5 %.
• A phone bill drops from $45 to $36 → (9 ÷ 45) × 100 = 20 %.

”By” versus “to” versus repeated decreases

English overloads the word “decrease” in ways that cause real money to move in the wrong direction.

• Decreased by 30 % → new value is 70 % of old (multiply by 0.70).
• Decreased to 30 % → new value is 30 % of old (multiply by 0.30).
• Decreased by 30 % then by another 30 % → multiply by 0.70 × 0.70 = 0.49, a 51 % total decrease, not 60 %.

The last one trips up retail-pricing teams constantly. Two back-to-back 30 % markdowns are not the same as a 60 % markdown. Discounts compound multiplicatively, never additively.

Percentage decrease vs percentage change vs difference

Three related terms answer different questions:

• Percentage decrease is the positive magnitude of a drop. It always reports as a positive number; you separately state the direction in plain language (“the price dropped 25 %”).
• Percentage change is the signed version. A drop reads as a negative number (“the price changed by −25 %”). Use this when you don’t know in advance which way the value will move — stock prices, temperature, A/B test results.
• Percentage difference is symmetric. It uses the average of the two values as the denominator, and the order of inputs doesn’t matter. Use this when neither value is “the original” — comparing two thermometers, two store prices for the same product, two model predictions.

For the same two numbers (40 and 60), each of these formulas produces a different percentage. They are all correct — each answers a different question.

Common mistakes to avoid

Using the new value as the denominator. Always divide by the original. Dividing by the new value overstates the drop. Pattern: the smaller the new value, the bigger the over-statement.

Adding sequential percent decreases. Two 20 % cuts in a row are a 36 % total cut (0.80 × 0.80 = 0.64), not 40 %.

Confusing percent decrease with absolute decrease. A drop “from $1 000 to $900” is a $100 absolute decrease and a 10 % decrease — both true, both worth knowing, but they answer different questions in a report.

Reporting a negative decrease. If the formula returns a negative number, you actually have an increase. Reframe before sending. The calculator above flags this for you.

Privacy

This calculator runs as a few arithmetic operations in JavaScript on your device. There are no fetch calls, no analytics on the values you enter, no server-side logging.