Skip to main content
Primary formula: targetPay = sourcePay รท sourceHours ร— targetHours
Duc Nguyen X.By Duc Nguyen X.ยท Founder, Wage101Last reviewed: View update historyMethodology

Educational only: Work and pay decision support, not tax, legal, financial or career advice.

Privacy: No account is required. Tool inputs and results stay in this browser. Anonymous categorical usage analytics send only governed page, tool, cluster and action identifiers; tool inputs and results are never sent. Error monitoring is disabled. Optional saved state stays only on this device.

Update policy: Reviewed when formulas or official dependencies change.

Scope: Market-neutral work and pay planning using your own assumptions.

What this calculator helps you decide

Best for

Comparing part-time and full-time gross salary at the same implied hourly rate.

Outputs

Equivalent target annual pay, implied hourly pay and the annual difference.

Start here

Enter current annual pay and weekly hours, then choose target weekly hours.

Close-intent boundary
Do not use this to convert one quoted pay period directly; use Pay Period Converter for hourly through annual equivalents.

Compare pay and working hours

Part-Time Salary Equivalent: equivalent target annual pay

Equivalent target annual pay, implied hourly pay and the annual difference.

Current and target schedules

Enter current annual pay and hours, then the weekly hours you want to compare.

Your numbers stay in this browser

currency units

Gross annual pay for the current weekly schedule.

Paid hours in the current schedule.

Paid hours in the schedule you want to compare.

Paid weeks used for both schedules.

Calculated result

The target salary preserves the current implied hourly rate while changing weekly hours.

Use one currency consistently across all inputs.

PDF and CSV exports stay on this device. Clean page links contain no inputs.
Equivalent target annual pay80,000.00per year
Implied hourly pay38.46per hour
Annual pay difference20,000.00per year
Target hours ratio133.3%share of current hours

Scenario comparison

Each row names the assumption axis changed from the baseline.

ScenarioResultDifference
Entered scenario80,000.00Baseline
Target weekly hours: 4284,000.004,000.00

Save these results, change an input, then compare the updated figures with this baseline.

The baseline is temporary in this tab and is not added to shared scenario links or generated reports.

Calculation details

View calculation detailsView the formulas and inputs used for these results.

Equivalent target annual pay

Target annual paytargetPay = sourcePay รท sourceHours ร— targetHours80,000.00 currency units
Result80,000.00 currency units

Annual pay at the target hours while holding hourly pay constant. Displayed using the engine-rounded value.

Equivalent target annual pay formula โ†’

Implied hourly pay

Implied hourly payhourlyPay = sourcePay รท (sourceHours ร— weeksPerYear)38.46 currency units
Result38.46 currency units

Current annual pay divided by current annual hours. Displayed using the engine-rounded value.

Implied hourly pay formula โ†’

Annual pay difference

Annual pay differencepayDifference = targetPay โˆ’ sourcePay20,000.00 currency units
Result20,000.00 currency units

Target equivalent pay minus current annual pay. Displayed using the engine-rounded value.

Annual pay difference formula โ†’

Target hours ratio

Target hours ratiohoursRatio = targetHours รท sourceHours133.3%
Result133.3%

Target weekly hours divided by current weekly hours. Displayed using the engine-rounded value.

Target hours ratio formula โ†’

Inputs used

Current annual pay
60,000.00 currency units
Current weekly hours
30
Target weekly hours
40
Paid weeks per year
52
Open this calculator with preset values

This calculator supports documented, shareable scenario URLs. Compatible assistants and applications can construct links using the parameters below.

Scenario values are visible in the URL, calculations run in the browser, and optional saved state stays only on this device. Anyone you share the URL with can read those numbers, so do not include private or identifying data.

Example: https://wage101.com/tools/part-time-salary-equivalent/?sv=1&sourceHours=30&sourcePay=60000&targetHours=40&weeksPerYear=52

ParameterMeaningUnitAllowed valuesPresenceDefault
sourcePayGross annual pay for the current weekly schedule.currency units/year0.01 to 100000000Required60000
sourceHoursPaid hours in the current schedule.hours/week0.5 to 120Required30
targetHoursPaid hours in the schedule you want to compare.hours/week0.5 to 120Required40
weeksPerYearPaid weeks used for both schedules.weeks/year1 to 53Required52

Part-Time Salary Equivalent: equivalent target annual pay

Use target pay as the annual salary that preserves the current implied hourly rate.

Formula summary

Primary formula
targetPay = sourcePay รท sourceHours ร— targetHours

Read the full methodology

Data used here

  • The estimate uses your inputs and the work-value formula documented in the methodology.

Decision checks

Act on the result

Compare this time-equivalent figure with the actual offer and its benefits.

Stress-test the decision

Test the exact target weekly hours and paid weeks stated by the role.

When this estimate can be misleading

  • This is a like-for-like time conversion, not a market salary benchmark.
  • Benefits and paid leave may not scale directly with hours.
  • The result cannot determine whether an offer is fair or compliant.
  • Use target pay as the annual salary that preserves the current implied hourly rate.

Educational estimate, not advice. See all assumptions & limitations โ†’

Use these practical guides to interpret the decision and its assumptions.

Frequently asked questions

What annual salary at different weekly hours preserves the same hourly pay?

Compare this time-equivalent figure with the actual offer and its benefits.

Which official source and period does this use?

This market-neutral tool does not use an official local policy rule.

Can I share or save a scenario?

Tool inputs and results stay in this browser. Anonymous categorical usage analytics send only governed page, tool, cluster and action identifiers; tool inputs and results are never sent. Error monitoring is disabled. Optional saved state stays only on this device.

What should stay consistent when I compare the options?

Keep the time basis, units and included costs consistent across options, then verify the assumptions that create the largest difference.