Hours to Decimal Calculator

Payroll math is one operation: hours worked multiplied by the hourly rate. That multiplication only works cleanly if "hours worked" is a single base-10 number. An employee paid $20/hour who worked 7 hours and 30 minutes earns $20 × 7.5 = $150.

Try to run that same multiplication against "7:30" directly and it falls apart, because 30 isn't 30% of an hour, it's 50% — the calculation silently produces a wrong number unless the minutes are converted first.

That's the entire reason every payroll system, spreadsheet formula, and invoicing tool standardizes on decimal hours before doing any rate math, rather than trying to multiply against clock time directly.

The confusion shows up constantly because two very similar-looking numbers mean completely different things. 7:30 written as clock time means 7 hours and 30 minutes. 7.30 written as decimal time means 7 hours and 0.30 of an hour, which is 7 hours and 18 minutes (0.30 × 60 = 18) — twelve minutes less than what the clock-time notation shows.

Someone who reads a timesheet entry of "7.30" and assumes it means seven-thirty on a clock will misreport the actual time worked. This is a genuinely common transcription error on manually filled timesheets, and it runs in both directions: employees round clock time into decimal-looking numbers without doing the conversion, and reviewers read decimal numbers as if they were clock time.

Spreadsheets add a second layer to this, because Excel and Google Sheets can store a cell as either a time value (which displays as HH:MM and is internally a fraction of a 24-hour day) or a plain decimal number, and the two aren't interchangeable without an explicit conversion formula.

A cell formatted as time that shows "7:30" is stored internally as 0.3125 (7.5 ÷ 24), not 7.5 — which is why payroll templates that mix time-formatted cells with decimal-formatted cells produce totals that are off by a factor of 24 if a formula reads the wrong cell type.

Converting to a plain decimal-hours number up front, the way this calculator does, sidesteps that entire class of spreadsheet error.

For a quick reference without running the calculator, here's every minute value from 5 to 60 converted to decimal hours (minutes ÷ 60, rounded to two decimal places): 5 min = 0.08, 10 min = 0.17, 15 min = 0.25, 20 min = 0.33, 25 min = 0.42, 30 min = 0.50, 35 min = 0.58, 40 min = 0.67, 45 min = 0.75, 50 min = 0.83, 55 min = 0.92, 60 min = 1.00.

The quarter-hour values — 15, 30, and 45 minutes — are the three worth memorizing, because they're both the most common clock-in/clock-out increments and the only ones that convert to a clean two-decimal number without rounding: 15 minutes is exactly 0.25, 30 minutes is exactly 0.50, and 45 minutes is exactly 0.75.

Every other minute value produces a repeating or long decimal that gets truncated for display (20 minutes is really 0.3333…, shown as 0.33), which is a minor rounding difference most payroll systems accept, but it's worth knowing it's happening rather than assuming every decimal-hours figure is mathematically exact to the fraction of a cent.

At scale that rounding matters more than it looks. An employee clocking in and out to the minute across a 2,000-hour work year accumulates small conversion roundings that mostly cancel out, but a payroll system that always rounds the same direction (always down, say) will systematically underpay over a year even though each individual discrepancy looks trivial. That's part of why the federal rounding rule described below requires rounding practices to average out over time rather than consistently favoring the employer.

Payroll processors like ADP call this same conversion "minutes to hundredths" rather than "minutes to decimal," and it's worth knowing that's the same table under a different name, not a separate system. "Hundredths" refers to the decimal being expressed to two places (7.50, not 7.5000), not to some alternate base-100 conversion — the underlying math is still minutes divided by 60.

The naming difference matters mainly when searching for a payroll provider's own reference chart: looking for "decimal hours" and "hundredths of an hour" both lead to the identical 60-value table.

This calculator gives an exact decimal conversion — it doesn't apply any rounding on its own. Rounding is a separate policy choice employers layer on top, and U.S. federal law does put a real boundary around it.

Under 29 CFR 785.48(b), the Department of Labor's regulation on timekeeping, employers may round employee clock times to the nearest 5 minutes, nearest tenth of an hour, or nearest quarter hour, but only if the practice "will not result, over a period of time, in failure to compensate the employees properly for all the time they have actually worked." In plain terms: rounding has to average out, not consistently shave time off what an employee is owed.

The regulation exists because time clocks have used 5-minute, tenth-hour, and quarter-hour recording as an industry practice for decades, and the DOL chose to accept that established practice rather than require to-the-second precision, as long as it doesn't drift in the employer's favor.

The most commonly cited application of that rule, used by payroll providers and employment-law guidance, is the "7-minute rule" for quarter-hour rounding: minutes 1 through 7 round down to the nearest quarter hour, and minutes 8 through 14 round up to the next one.

Worked 7 hours and 7 minutes, and quarter-hour rounding brings that down to 7.00; worked 7 hours and 8 minutes, and it rounds up to 7.25.

That specific 7/8-minute split isn't spelled out word-for-word in the regulation's text — the regulation only requires that rounding average out fairly — but it's the standard way payroll systems implement quarter-hour rounding in a way that satisfies it, since 7 minutes rounds toward the nearer quarter-hour mark and 8 minutes doesn't.

California has since added a wrinkle worth knowing if your business operates there: state courts have upheld neutral rounding under the same averaging-out logic, but California's Labor Commissioner and subsequent case law have pushed employers toward recording time to the actual minute wherever practical, given the state's stricter wage-and-hour enforcement. If your payroll operates in California, treat any rounding policy as something to confirm with a wage-and-hour attorney rather than assuming the federal standard alone covers you.

Payroll isn't the only place this conversion matters. Legal and consulting billing runs on the same minutes-to-decimal math but standardizes on a different increment: tenths of an hour instead of quarters.

Six minutes is exactly one-tenth of an hour (6 ÷ 60 = 0.1), so attorneys and consultants who bill in six-minute units are using the same formula this calculator runs, just rounded to the nearest 0.1 instead of the nearest 0.25. A phone call that runs 22 minutes gets billed as 0.4 hours (four six-minute units), not the unrounded 0.37 the raw conversion would produce.

This six-minute billing increment is widely documented industry practice in legal and professional-services billing software, though unlike payroll rounding it isn't governed by a single federal regulation — it's a client-invoicing convention rather than a wage-and-hour rule, so individual firms and state bar guidance set the specifics.

Time-tracking software works the same way under the hood.

Apps like Toggl or Harvest record a session's duration internally down to the second, but when it comes time to generate an invoice or export a report, that duration gets converted to decimal hours for the same reason payroll does: multiplying an hourly rate by a decimal number is a single clean operation, while multiplying it by "2 hours 47 minutes" isn't.

A freelancer billing $75/hour for 2 hours and 47 minutes of work needs that time expressed as 2.78 decimal hours (47 ÷ 60 = 0.7833, rounded to 2.78) before the invoice total, $75 × 2.78 = $208.50, can be calculated at all.

Aviation logbooks are a less obvious example of the same pattern. Flight time is traditionally recorded using a Hobbs meter, which measures engine run time directly in decimal tenths of an hour rather than minutes, so a pilot's logbook entry of "2.3" means 2 hours and 18 minutes of recorded flight time, not 2 hours and 30 minutes.

Anyone converting a Hobbs reading into a more familiar hours-and-minutes format is running this calculator's reverse conversion: take the decimal portion, multiply by 60, and get the minutes back.