Written by Sarah Mitchell · Reviewed by Alex Chen · July 22, 2026
Convert your salary between hourly, daily, weekly, bi-weekly, monthly, and yearly rates.
Standard full-time: 40 hours.
Enter an amount and click Convert.
Salary offers arrive in different shapes: an hourly rate here, a monthly figure there, a yearly number in the job ad. This converter's job is to express any one of those as all six at once — hourly, daily, weekly, bi-weekly, monthly, and yearly — using assumptions you can see and change.
You choose the period that matches the number you already have, type the amount in, and press Convert. The whole table fills in. The one setting that matters is Hours per Week, which defaults to 40 and drives every other row; the amount box itself accepts decimals, so precise figures like 28.846 work fine.
Everything hangs off a single hub: the weekly amount. Once the converter knows your weekly pay, every other row is one simple operation:
If the number you entered is the hourly rate, the hub works in reverse: the weekly figure becomes hourly times hours per week, and every other row derives from that. The fifty-two-week year is the engine's second fixed assumption, alongside the five-day week. On a standard forty-hour schedule that works out to roughly 173.33 hours in an average month — forty hours times fifty-two weeks, divided by twelve.
One label is worth noticing: the Daily row says "(8h)", but the calculation is actually weekly divided by 5. At the default forty hours that's identical to eight times the hourly rate; change the hours-per-week setting and the daily figure still splits the week into five equal parts.
Notice there is no "days per week" box. Five working days is fixed inside the calculation, so the daily and weekly rows always hold that ratio — handy for most office schedules, slightly off for compressed weeks or six-day shifts.
Say a contract offers $60,000 a year. Choose "Per Year", leave the hours at 40, and press Convert. The table fills in like this:
Now run the check the other way: type 28.85 as the hourly rate and the converter lands on $60,008 for the year — eight dollars past the original figure, purely because the hourly row was rounded to cents before being multiplied back up.
The hours setting comes alive with a part-time example. Enter 22 as the hourly rate, set the week to 30 hours, and Convert yields $660 weekly, $1,320 bi-weekly, $2,860 monthly, and $34,320 yearly. Compare that with the same $22 at the default forty hours — $880 weekly and $45,760 a year — and you can see exactly what ten fewer hours cost in annual terms.
Four weeks would only add up to 48 weeks across the year. The converter uses 52 divided by 12 — about 4.33 — so twelve monthly figures cover all fifty-two weeks rather than shortchanging a month.
This table is gross pay. Your real check subtracts income tax, insurance, and other deductions, and many employers split the annual amount across a fixed set of 26 paydays regardless of the exact weekly figure shown here.
It is weekly pay divided by 5. At forty hours that matches eight hours a day; set the week to thirty-two hours and the daily figure still splits the week into five equal slices, so the "(8h)" label becomes a simplification.
Yes. The hours-per-week field accepts any value from 1 to 168 in half-hour steps, and every derived row follows the new weekly total — useful for part-time comparisons.
Only with adjustments. Enter your real billable hours and remember the yearly row counts fifty-two weeks; if you take unpaid weeks off, your true annual figure is lower than the table suggests.
The hourly row is rounded to cents. A penny of rounding, multiplied across 2,080 hours, turns into a few dollars of difference in the yearly total.
No — the dollar sign is just formatting. The arithmetic is identical for any currency, but nothing here handles exchange rates; convert your figure into the currency you care about before you start.
It's at its best for quick comparisons: turning an hourly offer into an annual figure to weigh against a salary, translating a freelance project rate into a rough yearly income, or communicating a range in the format a candidate asked for. Because the assumptions are visible and editable, it's also a decent tool for exploring "what if I worked fewer hours?" scenarios.
It won't tell you what you'll actually take home, what a role is worth once benefits are counted, or how overtime changes your effective rate. Those questions need your local tax rules and your real schedule, not a conversion table. For plain pay-period math, this gets you there in one click.