Convert between annual salary, monthly, weekly, daily, and hourly pay — enter any one value to see all the others.
Divide annual salary by total hours worked per year — typically hours per week × weeks per year (commonly 40 × 52 = 2,080 hours).
No, this converts between gross pay periods only. Actual take-home pay after taxes and deductions will be lower and varies by jurisdiction.
Adjust the "Weeks Worked per Year" field to reflect actual weeks worked, such as 50 weeks if you take 2 weeks of unpaid leave.
Yes, adjust "Hours per Week" to your actual part-time schedule for accurate conversions.
No, every calculation happens locally in your browser. Your income details are never transmitted anywhere.
Reduce "Weeks Worked per Year" below 52 to reflect actual paid working weeks, which will slightly increase the calculated hourly rate since the same salary is now being divided across fewer working hours.
Yes, enter your target annual income and realistic billable hours per week to find a baseline hourly rate — though freelancers typically need to add a margin above this baseline to cover non-billable time, taxes, and business expenses that a salaried calculation doesn't account for.
This tool converts pay between any period — annual, monthly, weekly, daily, or hourly — letting you enter a figure in whichever format you know and instantly see the equivalent in every other period.
All conversions are built from a base calculation: total hours worked per year, found by multiplying hours per week by weeks worked per year. A standard full-time schedule of 40 hours per week for 52 weeks yields 2,080 hours per year — the baseline most salary-to-hourly comparisons use. From there, annual salary divided by annual hours gives the hourly rate; that hourly rate multiplied by hours per day, week, or month gives each other period's equivalent pay.
The commonly cited "2,080 hours per year" figure assumes a full 52 weeks of work with no unpaid time off at all, which doesn't reflect most real working situations. Most salaried employees take some combination of paid vacation, sick leave, and public holidays, and freelancers or contractors often have unpaid gaps between projects. Adjusting the "Weeks Worked per Year" field to reflect your actual working weeks — say, 48 or 50 rather than the default 52 — gives a meaningfully more accurate hourly rate than relying on the unadjusted default, since the same annual salary divided across fewer actual working hours works out to a higher true hourly equivalent.
When comparing job offers or freelance rates across different countries, converting everything to a common period — typically hourly or annual — makes the comparison far more concrete than trying to mentally compare different quoted periods side by side. This is especially useful for remote work and international freelancing, where a client in one country might quote a project rate while you're used to thinking in terms of your local hourly or monthly rate, and converting both to the same basis removes the guesswork from deciding whether an offer is genuinely competitive.
When comparing a salaried job offer to freelance or contract work quoted at an hourly rate, it's easy to undervalue the salaried position's additional benefits — paid time off, health insurance, retirement contributions, and employer-side tax contributions — none of which show up in a simple salary-to-hourly conversion. A contract role needs to pay a meaningfully higher hourly rate than an equivalent salaried position's converted hourly rate to actually come out ahead once these additional costs and benefits are factored in, which is worth keeping in mind beyond just the raw numbers this calculator produces.
This calculator works with gross pay — the amount before taxes, insurance, retirement contributions, and other deductions. Actual take-home (net) pay will be lower and depends heavily on your specific tax situation, benefits elections, and local regulations, which vary too widely to calculate generically.
All calculations run directly in your browser — your salary information is never sent to a server, logged, or stored anywhere.
Having a clear, instant conversion between pay periods is especially useful during salary negotiation, where an offer might be presented in one period while your own mental benchmark is in another — comparing a new offer's annual figure against your current hourly rate, for instance, requires converting one into the other before a fair comparison is possible. Walking into a negotiation conversation already knowing your current position's equivalent in whatever period the new offer uses removes a layer of mental math under pressure, letting you focus the conversation on the actual value being discussed rather than scrambling to convert numbers on the spot.
The "hours per week" field has an outsized effect on the resulting hourly rate, which is worth double-checking carefully before trusting the output. Someone who regularly works 50-hour weeks but calculates their hourly rate assuming a standard 40-hour week will significantly overstate their true hourly rate, since the same salary is actually being earned across more hours than the calculation assumes. For anyone regularly working beyond a standard schedule, entering a realistic average hours-per-week figure — rather than the officially stated or contracted number — gives a far more accurate picture of what's actually being earned per hour worked, which can be an eye-opening number to see clearly.