Percentage Increase Calculator

Quick answer: generic percent change

How to use this generic percent tool

1. Choose percent-from-values or new-from-percent.
2. Enter any matching units (price, headcount, annual salary, etc.).
3. Read the percent or new value and copy/share the link.

Formulas

percent = (new − old) ÷ old × 100. new = old × (1 + percent/100). Amount change = new − old.

Common mistakes

• Mixing monthly and annual bases.
• Dividing by new instead of old.
• Forcing a percent when old is zero.
• Rounding intermediate steps too early.

Related guides and tools

Use the homepage pay raise calculator for multi-lens raise math, read how to calculate a raise for step-by-step identities, and browse blog guides for scripts, taxes, and benchmarks.

Using percentage increase beyond salary

Percentage increase is a general identity: change ÷ starting value × 100. Salary examples make the tool concrete, but the same math prices inventory markups, headcount growth, and budget variances. Keep units identical on both sides—never divide a monthly change by an annual base.

When the starting value is zero, percent increase is undefined. Switch to a dollar or unit change narrative instead of forcing a percent. When the starting value is negative, interpret percent carefully; finance teams often prefer absolute change for losses.

Round for display, not for intermediate math. Compute with full precision, then round money to cents and percents to two decimals unless your policy says otherwise. Share links that include inputs so a manager and an employee do not retype different bases.

Salary worked example: $58,400 → $61,320 is a $2,920 change and a 5% increase. Reverse path: 5% on $58,400 yields $61,320. Both paths must agree. Pair this page with the salary increase percentage calculator when HR language is raise-specific, and with the pay raise calculator when you need paycheck and inflation lenses.

For spreadsheet cells, see raise percentage in Excel and Google Sheets. For conversation scripts after you know the percent, see how to ask for a raise.

Common mistakes include mixing hourly and annual bases, treating percent points as percent of percent without care, and quoting a rounded display percent that no longer reconstructs the dollar change. Write the dollar change next to the percent every time.

Inflation is a second lens: a 5% nominal increase against 3% CPI is not the same purchasing-power story as 5% against 6% CPI. Use cited indexes with years; do not invent a household inflation rate on this page.

Managers should convert proposed percents into envelope dollars before calibration. Employees should convert offered percents into paycheck views before celebrating. Same identity, different decisions.

If you only need raise-specific workflows with tax sketches, prefer the homepage tool. If you need a clean generic percent from any two positive numbers—including non-salary examples—stay here.

Document the effective date of any pay change separately from the day you ran the calculator. Percents do not carry dates; letters do.

International readers should confirm whether local practice quotes monthly or annual bases before comparing percents across borders. Convert to one basis first.

When benefits change with pay, percent of base is still the right starting point; layer benefits as a second table rather than burying them inside a blended “total rewards percent” nobody can audit.

Promotion scenarios sometimes use guideline bands rather than a free-typed percent—model the band midpoint and edges, then read how to read a promotion raise for interpretation.

Job-change offers are often larger in percent terms because they price a hire, not a pool. Convert the offer gap with the job offer vs current salary calculator before treating a headline percent as destiny.

Retroactive corrections need period counts after you lock the correct new rate—see the back pay calculator.

Keep this tool’s results labeled as planning arithmetic. Payroll systems, union contracts, and local law still govern what posts.

Revisit saved URLs after each cycle so last year’s base does not silently become this year’s fiction.

Part-time schedules need explicit hour assumptions before you annualize a percent increase that started as an hourly story.

When two systems disagree by pennies, ask which rounding rule prevails rather than assuming one side failed arithmetic.

Use sibling calculators when the next question is hours, COLA, promotion, or take-home—not when you only needed a clean percent.

None of this replaces legal, tax, or financial advice. It makes the percent identity explicit so conversations start from the same formula.

Salary and non-salary worked examples

Salary: $94,000 to $99,640 is a $5,640 change and a 6% increase. Reverse: 6% on $94,000 returns $99,640. Price tag: $40 to $45 is 12.5%. Headcount: 40 to 46 people is 15%. Always name the unit beside the percent.

Merit letter translation: if the letter says 3.25% on $72,800, new pay is $75,164 and the annual raise is $2,364. Biweekly gross lift ≈ $90.92 at 26 periods. Confirm the calendar before you budget rent.

Offer gap: current $110,000 versus offer $121,000 is 10%. That hire-pricing percent is not a merit-pool entitlement—read job-change context on the blog before treating it as an internal floor.

Verify before you send the number

Recompute percent from dollars and dollars from percent. If they disagree, you mixed bases or rounded too early. Paste both into the shared link. Then decide whether the next tool you need is paycheck, take-home, or a conversation script—not another percent with different inputs.

When HRIS, the offer letter, and your spreadsheet disagree, ask which system is system-of-record for base pay. Percent of the wrong base wastes a meeting.

Keep a one-line audit note: old value, new value, percent, date, and source document. Future you will not remember which PDF you used.

If the change spans currencies, convert both sides to one currency on the same day before computing percent. FX moves are not raise math.

Finally, label every percent with the population it describes: individual award, team average, or company budget. Those are not interchangeable.

Operational notes for HR and employees

HRIS fields sometimes store “compa-ratio” beside percent increase. Compa-ratio is position in range, not the raise identity on this page. Do not divide range midpoint by old salary and call it a raise percent without labeling the metric.

Mass uploads of percent awards should be reconciled in dollars against the envelope. Export proposed percents, multiply by eligible bases, sum, and compare to finance’s number before letters go out.

Employees comparing offers across companies should convert each offer to annual cash in one currency and one hour assumption before computing percent differences. Otherwise the “higher percent” can be the worse job.

When a retention increase stacks on a scheduled merit increase, compute the combined new base once, then derive a single effective percent from original old to final new. Stacking percents sequentially without a combined check double-counts in hallway stories.

Keep audit trails: who entered the percent, which guideline cell applied, and which base was used. Disputes six months later are won by documentation, not memory.

If your organization quotes increases in “points” for some programs and percents for others, publish a glossary. Language drift creates fake disagreements.

Contractors and W-2 employees may see different increase mechanics; do not paste a W-2 percent story onto a contractor rate card without rewriting the agreement terms.

Equity refresh grants are not base percent increases. Track them on a separate ledger so total rewards conversations stay honest.

When market adjustments apply to a job family, show both the market percent and any remaining merit percent rather than a single blended sticker that nobody can reverse-engineer.

Close the loop by re-reading the letter’s effective date after you run the calculator. A perfect percent on the wrong date still fails payroll.

Additional guidance

Publish a one-page “how we compute percent” note in the compensation wiki so vendors and HRIS agree.

When importing CSV awards, validate that percent × base equals the dollar column within a penny.

Reject uploads that blank the base or store percent as a fraction without documenting the scale.

For negative bases in finance contexts, escalate to finance policy rather than forcing this raise-oriented tool.

Keep example libraries with salary and non-salary cases so analysts see the identity is general.

Version your guideline matrices by year and link that year next to every percent award.

If leadership wants a single “average increase” slide, also show the dollar-weighted average, not only the mean of percents.

Mean of percents across people with different bases misleads; dollar-weighted views match the envelope.

Document whether terminated employees are included in averages before anyone quotes them externally.

When communicating to employees, prefer personal old/new/percent over company averages as entitlement.

More planning notes

Document every assumption you feed the calculator: hours, weeks, inflation source, promotion guideline, and whether overtime is included. Shared assumptions prevent two people from arguing about arithmetic when they actually disagree about inputs.

Gross figures are the right starting point for compensation math. Taxes, benefits elections, and retirement deferrals change take-home later. Settle the gross identity first, then estimate net with a separate method you trust.

When schedules change mid-year, re-run the model rather than stretching an old annualization across a new reality. Stale hour assumptions are the most common source of overstated income in household budgets and loan applications.

Managers should translate percent language into dollars before approving grids, and translate cents-per-hour awards into annual cost before claiming a pool is balanced. Employees should do the reverse translation so a raise conversation stays bilingual.

Offer letters, merit worksheets, and payroll stubs sometimes use different rounding. If two systems disagree by a few dollars a year, ask which rounding rule prevails rather than assuming one side made an arithmetic error.

Geographic moves, remote policies, and second jobs all change the meaning of the same headline salary. Convert units carefully, then layer location and risk as separate decisions instead of hiding them inside a blended number.

Retroactive corrections belong in their own workflow: lock the correct new pay, count missed periods from the true effective date, and keep approval notes. Mixing effective dates with decision dates is how back-pay disputes begin.

Use sibling tools on this site when you need the next step: percent from two salaries, hourly raise cents, multi-year compounding, merit pools, COLA, promotion scenarios, offer compares, or back pay. Each page keeps one job clear.

None of these calculators replace payroll systems, union contracts, or legal advice. They make the planning arithmetic explicit so conversations with HR, managers, and recruiters start from the same formulas.

Revisit your saved inputs after every raise cycle. A link with last year’s hours or an outdated overtime pattern can quietly mislead next year’s negotiation if you forget to refresh it.

Part-time, seasonal, and academic schedules deserve explicit weeks-per-year edits. Forcing a fifty-two-week model onto a forty-week role invents income that never arrives and distorts every percent comparison downstream.

When benefits matter, estimate employer-paid dollars you can defend, then compare total cash plus benefits beside base-only math. Treat vague “great benefits” claims as incomplete until they have numbers.

Inflation overlays answer whether a nominal raise preserved purchasing power. Enter an index you can cite; do not invent a universal COLA. Holding purchasing power is not the same as advancing real living standards.

Promotion math should start from the new role’s pay range when available. A percent from current pay is a planning shortcut; range placement and compa-ratio still decide whether the promotion is competitive inside the band.

If overtime eligibility disappears in a move to salary, model busy-season cash both ways. Predictability can be worth a cash tradeoff, but only when the tradeoff is visible before you accept.

Keep base pay separate from one-time bonuses and equity grants when you annualize or compare offers. Blending temporary money into a recurring identity inflates every future percent conversation.

Semi-monthly and biweekly calendars split the same annual salary differently per check. Use period views for cash-flow planning, then confirm against an actual pay stub before you commit to a budget.

Written guidelines beat memory. If your handbook lists promotion bands, merit matrices, or COLA policies, enter those numbers rather than a rumor from another department’s cycle.

International readers should adapt hour norms: some labor markets standardize nearer thirty-five or thirty-seven-and-a-half hours. Change the hours field so the equivalent rate stays meaningful locally.

After you finish the math, decide what action it unlocks: ask for more cash, ask for workload limits, accept, or keep looking. Clear arithmetic makes the decision sharper.

More percentage-increase guidance

Publish a one-page “how we compute percent” note in the compensation wiki so vendors and HRIS agree. When importing CSV awards, validate that percent × base equals the dollar column within a penny.

If leadership wants a single average increase slide, also show the dollar-weighted average, not only the mean of percents. Mean of percents across people with different bases misleads; dollar-weighted views match the envelope.

Document whether terminated employees are included in averages before anyone quotes them externally. When communicating to employees, prefer personal old/new/percent over company averages as entitlement.