Yearly wage calculator
25 an hour for 40 hours a week comes to 52,000 a year before tax. Enter your rate and your usual weekly hours to see the annual figure over 52 weeks, plus weekly and monthly pay. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Hourly rate
- 25
- Weekly hours
- 40
- Weeks per year
- 52
- Weekly pay
- 1,000
- Monthly pay
- 4,333.33
- Yearly wage
- 52,000
Gross yearly wage is the first number people compare when a job, contract, or side gig is quoted by the hour and a budget, loan, or listing is quoted by the year. This yearly wage calculator multiplies a positive hourly rate by the hours worked each week and by fifty-two weeks to return the annual salary, plus the implied weekly pay and a nominal monthly figure. Job seekers use it to translate an hourly listing into yearly income. Contractors and part-time staff use it to see what a schedule actually pays over a full calendar year. A non-positive hourly rate is rejected as invalid input rather than producing a zero or signed salary.
What yearly wage means and how the fifty-two-week product is formed
When someone asks for yearly wage they usually want gross annual pay from an hourly rate and a weekly schedule, not take-home pay after tax and not a conversion among daily, biweekly, and monthly payroll calendars. The model does not invent overtime multipliers, paid-leave credits, employer benefits, or local labor-law adjustments. It does not convert currency and it does not withhold tax.
A twenty-five unit hourly rate at forty hours per week is a yearly wage of fifty-two thousand. An eighteen-point-five rate at thirty-two hours is thirty thousand seven hundred eighty-four. Zero weekly hours is allowed and yields a yearly wage of zero, which is how an unused schedule is represented without a second formula.
Fractional hours such as thirty-seven point five are valid. Money fields in the response are rounded half-up to two decimal places so they match ordinary currency.
Where a yearly wage calculator earns its keep
People who type yearly wage into a search box already know they are annualizing an hourly rate, not converting among payroll periods and not computing overtime premium. They want the annual salary from hours on a typical week times fifty-two, without rebuilding the same product in a spreadsheet cell that drifts when someone forgets whether the year has fifty or fifty-two working weeks. Candidates compare an hourly listing with a salaried peer offer and need a number they can paste into a budget or a loan pre-check.
Contractors bound yearly income from a fixed billable rate under a part-time or full-time week before they accept a retainer. HR tutors and personal-finance courses need an oracle that rejects a non-positive hourly rate instead of silently emitting a zero a grader might treat as success. Failed validation does not consume balance.
Pair this capability with a salary-to-hourly or overtime tool when you need those layers; keep this surface focused on the fifty-two-week gross yearly wage that people mean when they search that phrase.
What you can do with it
Compare an hourly offer with a salaried listing
Enter the hourly rate and weekly hours from the posting to publish the fifty-two-week annual salary next to a salaried peer offer.
Bound contractor income from a weekly schedule
Translate a billable hourly rate and the hours you expect to work each week into a gross yearly wage before you accept a retainer.
Payroll and personal-finance worksheets
Give students a deterministic yearly wage from rate and hours so a grader can pin fifty-two thousand without a drifting spreadsheet.
FAQ
How is yearly wage calculated from an hourly rate?
A twenty-five unit rate at forty hours per week is fifty-two thousand for the year.
Why must the hourly rate be a positive number?
A zero or negative rate is not a meaningful gross wage in this model. Enter a finite rate strictly greater than zero.
Does the calculator use fifty or fifty-two weeks?
It always uses fifty-two weeks, the standard payroll year. It does not ask how many weeks you take unpaid. Forty hours times fifty-two is the familiar two-thousand-eighty hour year.
Is this take-home pay after tax?
No. The result is gross yearly wage before tax, overtime, benefits, or currency conversion. Pair it with a dedicated tax tool if you need net pay.
How much is 25 an hour per year at 40 hours a week?
It is 52,000 a year before tax: 25 times 40 hours gives 1,000 a week, and 52 weeks of that make the annual total. The monthly figure is that total divided by 12, about 4,333.33.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/fin/yearly-wage \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"hourly_rate":25,"weekly_hours":40}'const res = await fetch("https://api.kit.forhosting.com/fin/yearly-wage", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"hourly_rate": 25,
"weekly_hours": 40
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/fin/yearly-wage",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"hourly_rate": 25,
"weekly_hours": 40
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/fin/yearly-wage", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"hourly_rate":25,"weekly_hours":40}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"hourly_rate":25,"weekly_hours":40}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/fin/yearly-wage", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"hourly_rate": 25,
"weekly_hours": 40
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "fin.yearly_wage",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_hourly_rate | 1000000000 |
max_weekly_hours | 168 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Payroll tutors and personal-finance writers use the same closed form for worksheets that must not drift between a classroom demo and a later API check. Successful calls are billed at $0.002; invalid input is not charged.
What yearly wage means and how the fifty-two-week product is formed
The identity this calculator uses is the payroll convention of a fifty-two-week year: yearly_wage equals hourly_rate times weekly_hours times fifty-two. That is the same closed form behind the familiar two-thousand-eighty hours figure for a forty-hour week, because forty times fifty-two is two thousand eighty. From the same inputs the response also reports weekly_pay as the product of rate and weekly hours, and monthly_pay as yearly wage divided by twelve so you can compare against listings that quote a monthly figure. A zero or negative hourly rate is not a complimentary line and is not a credit: it is rejected as invalid_input because the product contract requires a positive hourly rate. The formula string restates yearly_wage equals hourly_rate times weekly_hours times fifty-two so a reviewer can print the identity next to the number without reconstructing it from a spreadsheet that may have used fifty weeks by accident.
Input contract, response shape, and error behaviour
Currency marks, thousands separators, and trailing unit labels are not parsed. Example: hourly rate twenty-five and weekly hours forty yields weekly pay of one thousand, yearly wage of fifty-two thousand, and a nominal monthly figure of four thousand three hundred thirty-three point three three. Prefer bare numbers over formatted strings. Pair the result with a dedicated tax or overtime tool if you need those layers. POST a JSON body with two required finite numbers in the same currency. hourly_rate is the gross pay per hour and must be a finite number strictly greater than zero; aliases rate, hourly, wage, pay_rate, hour_rate, and hourly_wage are accepted so a spreadsheet export does not need a rename step. A missing, zero, negative, or non-finite hourly rate fails with invalid_input naming hourly_rate and is not billed. weekly_hours is hours worked in a typical week and must be a finite number greater than or equal to zero and at most one hundred sixty-eight, the hours in a calendar week; aliases hours, hours_per_week, week_hours, and hrs_week are accepted. Negative weekly hours, hours above the limit, missing weekly hours, and non-finite values fail with invalid_input naming weekly_hours. Each field may arrive as a JSON number or as a numeric string that matches a strict finite decimal pattern. On success the body echoes rounded hourly_rate and weekly_hours, reports weeks_per_year as fifty-two, returns weekly_pay as their product, yearly_wage and amount as the same fifty-two-week annual figure, monthly_pay as that annual figure divided by twelve, and a formula string you can print next to the numbers. This endpoint does not apply overtime, tax, unpaid-leave week counts, or currency conversion, and it does not emit a pay stub. Pricing for a successful item is a flat $0.002.
Where a yearly wage calculator earns its keep
Keep requests small, pin yearly_wage in tests, and you get a reproducible annual salary for offer letters, budget worksheets, and lightweight compensation notebooks without standing up a full payroll system. The same closed form is what recruiters quote when they say an hourly package annualizes to a given salary, so locking it in an API keeps the conversation honest.
Technical questions
What does the yearly wage calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.