Hours to Decimal Calculator

What this calculator does

This calculator converts hours and minutes (the way a clock or schedule shows time) to decimal hours (the way payroll software stores time), and back the other way. It’s the tool to reach for when your timesheet says you worked 7:30 and the payroll portal wants 7.50, or when your pay stub shows 8.25 and you want to know how many minutes that actually represents.

How to calculate decimal hours

The formula is:

decimal hours = hours + (minutes ÷ 60)

Two steps: divide the minutes by 60 to get a fraction, then add to the whole-number hours. Going the other way:

hours    = ⌊decimal⌋
minutes  = (decimal − hours) × 60

Take the whole-number part as the hours, multiply the fractional part by 60 to get the minutes. The calculator above shows both directions step by step.

Worked examples

A shift from 9 AM to 4:30 PM is 7 hours 30 minutes. In decimal: 7 + 30/60 = 7.50 hours. At $20 per hour that’s $150 gross pay without further conversion.

Two more for reference:

• 8h 15m = 8.25 decimal hours (because 15 / 60 = 0.25).
• 5h 45m = 5.75 decimal hours (because 45 / 60 = 0.75).
• 9h 20m ≈ 9.33 decimal hours (because 20 / 60 ≈ 0.3333…).

The third example shows where rounding starts to matter. 9h 20m is exactly 9 + 1/3 hours — a repeating decimal. Payroll systems typically round to two decimal places, so it prints as 9.33, but internally most systems carry four or more places to avoid accumulated rounding errors across a pay period.

Why payroll uses decimal hours

Multiplying time by money is much cleaner in decimal. 7.50 × $20 = $150 is a one-step calculation; 7:30 × $20 requires you to convert the :30 to 0.5 first. So accounting, payroll, scheduling exports, and HR systems standardise on decimal hours — sometimes called industrial time.

The reverse direction matters when you receive a payroll export and need to read it as wall-clock time. A timesheet entry of 4.25 is 4 hours 15 minutes, not 4 hours 25 minutes — the .25 is a fraction of an hour, not a count of minutes. This confusion catches people out routinely and can lead to misreporting hours by 15–45 minutes per shift.

Quarter-hour reference table

Most timesheets are filled in to the nearest quarter hour, which gives four common decimal values:

These four are worth memorising. Add the eighths (:07 / :08 ≈ .125, :22 / :23 ≈ .375, :37 / :38 ≈ .625, :52 / :53 ≈ .875) if your workplace rounds to the nearest 5 or 6 minutes. The calculator’s quick-reference panel shows all eight.

Decimal hours vs decimal minutes — the big gotcha

A common mistake is mixing up decimal hours with decimal minutes. They sound similar and look similar but mean different things:

• Decimal hours: a fraction of an hour. 7.50 = 7 and a half hours = 7 hours 30 minutes.
• Decimal minutes: a fraction of a minute. 7.50 = 7 and a half minutes = 7 minutes 30 seconds.

Almost all payroll systems use decimal hours. A few legacy manufacturing or timecard systems display decimal minutes — typically when they’re tracking machine-cycle time rather than payable labour time. If a number in a payroll export feels too small by a factor of 60, you’re almost certainly looking at decimal minutes by mistake. This calculator does decimal hours only.

Common mistakes to avoid

Treating 7.30 as 7 hours 30 minutes. It isn’t. 7.30 decimal hours means 7 hours 18 minutes (because 0.30 × 60 = 18). 7 hours 30 minutes is 7.50 in decimal. The decimal point is not the colon.

Forgetting to clamp minutes to 0–59. If you type 75 in the minutes field, that’s 1 hour 15 minutes worth of time, and a clean payroll system will refuse to accept it. The calculator above clamps the minutes field to 59 to surface this immediately.

Rounding too aggressively. Two decimal places (e.g. 7.33) loses about 0.36 seconds per hour relative to the exact value. Across a 40-hour week, that’s roughly 14 seconds. If you’re computing gross pay at the dollar level, two decimal places is fine. If you’re auditing totals across hundreds of employees, carry four.

Privacy

This calculator runs as a division and an addition in JavaScript on your device. There are no fetch calls, no analytics on the values you enter, no server-side logging.