whattimeisit.blog
Units of time

How Many Hours Are in a Year?

A common calendar year has 8,760 hours; a leap year has 8,784. Here’s how those totals work, how many hours fall in each month, and why paid work hours are counted differently.

By Leo, editorUpdated November 10, 202610 min read4 sources
Blank calendar beside an analog clock
Illustration created for WhatTimeIsIt.blog.
Quick answer

A common year has 365 days, so 365 × 24 = 8,760 hours. A leap year has 366 days, so 366 × 24 = 8,784 hours; the Gregorian calendar adds February 29 under its leap-year rules, as explained by the U.S. Naval Observatory.

  • ICommon year: 8,760 hours
  • IILeap year: 8,784 hours
  • IIIA 40-hour, 52-week work year: 2,080 hours
  • IVA 30-day month: 720 hours
  • VA 31-day month: 744 hours
I

How many hours are in a common year?

A common year has 365 calendar days. Each day has 24 hours, so the calculation is 365 × 24 = 8,760 hours. That is the straightforward answer when you mean a regular calendar year rather than a leap year.

You can also check it by starting with weeks: 365 days make 52 full weeks plus 1 day. The full weeks contain 52 × 7 × 24 = 8,736 hours, and the remaining day adds 24, for the same total of 8,760. This check is useful when you are comparing a year with a weekly schedule or converting a yearly span into smaller units.

The figure describes the calendar’s count of days and hours. It does not automatically tell you how many hours you personally worked, were awake, or were paid for. Those totals depend on the schedule or the exact start and end times you are measuring. To work out a particular span between two dates, use a date calculator; for a span expressed in hours and minutes, an hours calculator can help keep the arithmetic clear.

The familiar 24-hour day is the unit behind the calculation. For more on the year’s day count, see how many days are in a year, or compare it with how many weeks are in a year.

II

Why a leap year has 8,784 hours

A Gregorian leap year has 366 days because it includes February 29. Multiply the added day by 24 hours: 24 × 366 = 8,784 hours. A leap year therefore has exactly 24 more calendar hours than a common year.

The Gregorian rule is more specific than “every four years.” A year divisible by four is generally a leap year, but a century year is a leap year only if it is also divisible by 400. The U.S. Naval Observatory notes that 2000 was a leap year while 1900 was not. These exceptions keep the calendar more closely aligned with the seasons over time. You can read the full rule in the U.S. Naval Observatory’s calendar guide or review the basics in our guide to what a leap year is.

To calculate a leap year’s hours yourself, first confirm that the year is a leap year, then multiply 366 by 24. For example, 366 × 20 = 7,320 and 366 × 4 = 1,464; added together, that is 8,784. The same method works for any year length you already know: multiply the number of days by 24.

Do not add a leap day twice. February 29 is already included in the 366-day total, so 8,784 is the complete yearly count, not a base figure that needs another 24 hours added to it.

III

Calendar hours versus the exact duration of a year

The totals 8,760 and 8,784 answer a calendar question: how many 24-hour days are counted in a common or leap year? They are not a claim that Earth’s trip around the Sun takes exactly that many whole days. The U.S. Naval Observatory explains that a calendar year does not contain an integral number of days, which is why calendar rules need adjustments such as leap years.

For most everyday planning, the calendar total is the right one. For a technical calculation, distinguish a count of calendar days from an exact elapsed-time measurement. A span from one timestamp to another depends on the exact boundaries and time scale being used. For instance, clocks in places that observe daylight saving time move forward or back at the transition, so a local calendar date around a transition may not contain the same elapsed clock time as a date without one. See our guide to daylight saving time for more on clock changes.

UTC can also include leap-second adjustments. The National Institute of Standards and Technology (NIST) explains that leap seconds are used to keep UTC synchronized with astronomical time, based on Earth’s irregular rotation. That is a separate adjustment from a leap day: leap years follow calendar rules, while leap seconds are applied as needed.

So if you are asking for a quick calendar conversion, use 8,760 or 8,784. If you are calculating the elapsed duration between two precise timestamps, use the timestamps and relevant time standard rather than assuming every year has an identical number of seconds.

IV

How many hours are in each month?

Months do not all contain the same number of days, so they do not all have the same number of hours. A 30-day month has 30 × 24 = 720 hours; a 31-day month has 744. February has 672 hours in a common year and 696 in a leap year.

This table shows the month totals for 2026, a common year. To get each number, multiply the days in the month by 24. The calendar rules and month lengths are described by the U.S. Naval Observatory; the hour totals below are direct arithmetic from those day counts.

Month-hour totals calculated from Gregorian calendar month lengths; source for calendar rules: U.S. Naval Observatory.
Month in 2026DaysHours
January31744
February28672
March31744
April30720
May31744
June30720
July31744
August31744
September30720
October31744
November30720
December31744

For February in a leap year, replace 28 days with 29: 29 × 24 = 696 hours. The other month totals stay the same. This table counts the hours represented by calendar days; it is not a work-hours table and does not subtract weekends, holidays, or time off.

V

What is the average number of hours in a month?

There is no single fixed number of hours in every calendar month. If you need an average across a whole year, divide the year’s total hours by 12. For a common year, 8,760 ÷ 12 = 730 hours per month on average. For a leap year, 8,784 ÷ 12 = 732 hours per month on average.

These are mathematical averages, not the actual duration of each named month. In a common year, February has 672 hours, while a 31-day month has 744. The difference is why multiplying a monthly average by a particular month’s dates may not give the correct calendar total for that month.

Average-month figures can still be handy for rough comparisons or annual planning. Just be clear about what you are estimating. If you are converting a monthly target into a yearly one, multiplying by 12 is reasonable when the target is defined as the same amount each month. If you are counting actual time between a particular month’s start and end, use that month’s day count instead.

For smaller conversions, remember the same units: 1 day is 24 hours, and 1 hour is 60 minutes. NIST describes the second as a defined unit of time based on a cesium-atom frequency; the NIST introduction to the second explains the modern definition. If your calculation mixes hours and minutes, write each quantity in one unit before adding or dividing.

VI

How many work hours are in a year?

A common full-time planning estimate is 2,080 work hours per year, calculated as 40 hours per week × 52 weeks. This is a schedule-based figure, not the number of hours in a calendar year. It also assumes 52 paid or scheduled weeks with no adjustment for holidays, vacation, sick leave, unpaid time off, overtime, or a different weekly schedule.

Use the figure that matches the question you are answering. For a simple annual estimate, 2,080 is convenient. To estimate scheduled hours after time away, subtract the applicable hours for that time off. For example, if you have a five-day schedule with 8-hour days, one full week off represents 5 × 8 = 40 scheduled hours. Your actual work arrangement and paid-leave rules determine whether those hours count as paid time.

Do not assume that every employee’s annual hours equal 2,080. A part-time schedule, compressed week, rotating shift, seasonal role, or overtime changes the total. In the United States, the Department of Labor says covered nonexempt employees generally must receive overtime pay at least one and one-half times their regular rate for hours worked over 40 in a workweek; the Department of Labor’s FLSA overview also explains that coverage and requirements matter.

For a real total, record the dates and hours worked rather than relying on a yearly shortcut. A business-days calculator can help count workdays, while a time-card calculator can help total shifts. For the steps behind a manual calculation, see how to calculate hours worked.

VII

How to convert an annual salary to an hourly estimate

To estimate an hourly equivalent from an annual salary, divide the annual amount by the number of annual work hours you choose. Using the 2,080-hour assumption for a 40-hour week across 52 weeks, an illustrative $62,400 salary works out as $62,400 ÷ 2,080 = $30 per hour.

Here is the arithmetic in smaller steps: 2,080 × 30 = 62,400, so dividing $62,400 by 2,080 gives 30. This is an estimate that spreads the stated annual salary evenly across those assumed hours. It is not a pay stub calculation and does not account for deductions, benefits, bonuses, unpaid leave, overtime, or differences between paid hours and hours actually worked.

The chosen divisor makes a difference. If your schedule is not 40 hours per week for 52 weeks, replace 2,080 with your estimated annual hours. For example, a schedule with fewer weekly hours will generally produce a smaller annual-hour total; dividing the same salary by fewer hours produces a higher hourly equivalent. Be consistent about what you include in both the salary and the hours.

This calculation is useful for rough comparisons, but it does not determine a legally required wage or overtime rate. Pay rules can depend on location, job duties, and employment classification. The U.S. Department of Labor’s FLSA information describes federal requirements for covered workers, including overtime rules for covered nonexempt employees. For your own situation, check the applicable rules and pay documents rather than treating this arithmetic example as a legal conclusion.

VIII

How to calculate hours for your own date range

For a simple whole calendar year, first decide whether it has 365 or 366 days, then multiply by 24. For a custom date range, identify the exact start and end points, count the elapsed days, and convert to hours. If the endpoints include times of day, include those too; a span from midnight to noon is 12 hours, not a full day.

  1. Choose the meaning of “year.” It might mean a named calendar year, 12 months from a start date, a work year, or an exact elapsed interval.
  2. Set the boundaries. Write down the start and end date, and include a time and time zone when precision matters.
  3. Count and convert. Multiply full 24-hour days by 24, then add any remaining hours and minutes.
  4. Check calendar adjustments. Consider leap day and, for local timestamps, daylight saving changes.

For a named year, a date calculator can help check date spans. When you are adding a known duration to a starting time, try the add-time calculator. If the start and end are in different places, first establish what the local times mean: a time zone converter can translate between zones.

One common mistake is treating “52 weeks” as the exact length of every calendar year. Fifty-two weeks contain 364 days, so a 365-day year has one additional day and a leap year has two. Another is confusing calendar hours with paid work hours. Choose the quantity that matches your purpose before doing the multiplication, and state your assumptions when sharing the result.

IX

Common mistakes when counting yearly hours

The first mistake is using 8,760 for every year. That is correct for a common year, but a leap year has one more day and therefore 24 more hours. The second is assuming every month has 30 days. Month totals vary, so use the month-by-month table when the question concerns a specific calendar month.

A third mistake is using the annual calendar total as a work-hours total. A year can contain 8,760 or 8,784 calendar hours, while a 40-hour schedule repeated for 52 weeks gives 2,080 scheduled hours before adjustments. These quantities answer different questions. If you are estimating pay, label the result as an hourly equivalent and state the divisor you used.

It is also easy to count the endpoints incorrectly in a date range. If you count both a starting date and an ending date as full days, but your actual interval ends at the start of the second date, your total will be too high. For precise elapsed time, include the exact times and time zones. UTC is a useful reference for comparing timestamps, but UTC itself can include leap-second adjustments; NIST’s leap-second FAQ explains that distinction.

Finally, write out the calculation instead of relying on a remembered average. “365 × 24 = 8,760” makes the assumption visible, while “about 730 hours per month” is explicitly an annual average. That small difference in wording helps prevent a correct estimate from being mistaken for an exact count of a particular month, shift schedule, or time interval.

?

Questions people ask

Is a year 8,760 or 8,784 hours?

Both totals are correct: 8,760 hours is 365 days × 24 hours, and 8,784 hours is 366 days × 24. The second total applies to a leap year with February 29 under Gregorian calendar rules. The U.S. Naval Observatory describes those leap-year rules.

How many hours are in a leap year?

A leap year has 366 days, so 366 × 24 = 8,784 hours. The added day is February 29. The Gregorian leap-year rule includes century-year exceptions, as explained by the U.S. Naval Observatory.

How many work hours are in a year if you work 40 hours a week?

Using 52 weeks as the planning assumption, 40 × 52 = 2,080 work hours. The total can differ if your schedule, overtime, leave, or paid weeks differ. It is a work-schedule estimate, not the number of calendar hours in a year.

How many hours are in an average month?

Divide the year’s hours by 12: a common year averages 730 hours per month (8,760 ÷ 12), and a leap year averages 732 (8,784 ÷ 12). Actual calendar months vary because they have different numbers of days.

How do I convert an annual salary to an hourly rate?

Divide the annual salary by your assumed annual work hours. For example, $62,400 ÷ 2,080 hours = $30 per hour, using a 40-hour week for 52 weeks. This is an illustrative equivalent, not a calculation of deductions or a determination of legally required pay. For covered nonexempt employees, the U.S. Department of Labor describes federal overtime requirements.

Does daylight saving time change how many hours are in a year?

For the basic calendar calculation, use 24 hours per counted day: 365 days gives 8,760 hours and 366 gives 8,784. But when measuring elapsed time between local timestamps, daylight saving clock changes can affect the result. UTC can also have leap-second adjustments; see NIST’s explanation of leap seconds.

§

Edited by Leo, editor of WhatTimeIsIt.blog

Calculations on this page run in your browser using the IANA time zone database and standard calendar rules. Facts are checked against the government agency, standards body or official source linked in the text. Last reviewed November 10, 2026. See the editorial policy or report an error to hello@whattimeisit.blog.