Work Hours Converter

Convert work time between HH:MM, decimal hours, work days, work weeks, planning months, work years, and FTE using standard planning assumptions.

Work

Work hours converter

Convert between decimal hours, HH:MM timesheet entries, work days, work weeks, planning months, work years, and FTE using a standard 8-hour day and 40-hour week.

Entry mode

Quick presets

Result

00:00

Equivalent to 0 hours, 0 standard work days, and 0 40-hour work weeks.

UnitEquivalent
Hours0 h
HH:MM00:00
Minutes0 min
Work days (8h)0 days
Work weeks (40h)0 weeks
Work months (173.33h)0 months
Work years (2,080h)0 years
FTE0 FTE

Overtime context

If this is a single-week total, it sits 40 hours below the common 40-hour overtime threshold.

Planning assumptions

The month, year, and FTE outputs are planning conversions built from an 8-hour day, 40-hour week, and 2,080-hour work year. Employer policy can differ.

Also in Time & Duration

Timesheet Conversion

Work hours converter: HH:MM, decimal hours, work days, weeks, months, years, and FTE explained

A work hours converter translates timesheet-style entries into broader workload units. It is useful when a shift length written as HH:MM needs to become decimal hours, when weekly hours need to be compared against a 40-hour baseline, or when planning capacity in work days, work weeks, or FTE.

What the page assumes

The converter uses a standard planning model of an 8-hour work day, a 40-hour work week, and a 2,080-hour work year. Those assumptions are widely used for scheduling, staffing, and budget planning because they translate one week of full-time work into five 8-hour days and fifty-two 40-hour weeks into one work year.

That does not mean every employer, country, or contract uses the same definitions. Compressed schedules, paid leave treatment, union agreements, and local law can change what counts as a work day, work month, or full-time equivalent in practice.

How conversion works

The page converts the starting value into hours first. If you enter HH:MM, it turns the timesheet entry into decimal hours by dividing the minute portion by 60. If you start from work days, weeks, months, years, or FTE, it multiplies by the relevant planning factor to return to hours before showing the other equivalents.

Because everything flows through hours, the output table stays internally consistent. That lets you compare a 37:30 weekly schedule, 4.69 work days, 0.94 work weeks, 0.22 work months, and 0.018 FTE as different views of the same underlying amount of work.

Decimal hours = hours + (minutes ÷ 60)

Converts a timesheet-style HH:MM entry into the decimal form used in many payroll and reporting systems.

Work year = 40 h/week × 52 weeks = 2,080 h

Planning relationship used by the page for work-year and FTE outputs.

How to interpret overtime and FTE context

A 40-hour baseline is useful because overtime rules, staffing plans, and budget models are often discussed against that threshold. The page therefore shows how far a converted weekly total sits above or below a 40-hour week, but that should be treated as context rather than as a legal determination.

The FTE output is also a planning ratio, not a payroll classification. It tells you what fraction of a 2,080-hour planning year the selected workload represents. That is useful for staffing, forecasting, and comparing schedules that use different time-entry conventions.

Frequently asked questions

What is 37:30 in decimal hours?

37:30 means 37 hours and 30 minutes, which equals 37.5 decimal hours because 30 minutes is 0.5 of one hour.

How many hours are in one FTE?

This page uses a planning assumption of 2,080 hours per work year, which comes from 40 hours per week across 52 weeks. Some organizations use a different annual baseline.

Does being above 40 hours automatically mean legal overtime?

Not necessarily. The 40-hour comparison is a useful planning reference, but legal overtime treatment depends on country, contract, worker classification, and employer policy.

Related

More from nearby categories

These related calculators come from the same leaf category, nearby sibling categories, or the same top-level topic.