7 hours 30 minutes is 7.50 decimal hours, since 30 minutes divided by 60 equals 0.50.
Results computed in your browser.
Every conversion this calculator does comes down to one division, minutes over 60. The table below is that division worked out for every common interval, so you can check a number by eye without opening the calculator at all.
| Minutes | Decimal | Minutes | Decimal |
|---|---|---|---|
| 5 | 0.08 | 35 | 0.58 |
| 10 | 0.17 | 40 | 0.67 |
| 15 | 0.25 | 45 | 0.75 |
| 20 | 0.33 | 50 | 0.83 |
| 25 | 0.42 | 55 | 0.92 |
| 30 | 0.50 | 60 | 1.00 |
Most of these numbers repeat forever in their exact form, ten minutes is really 0.1666 continuing, which is why the tool and this table both stop at two decimal places. That rounding costs a few seconds over one shift and stays negligible even added up across a year of timesheets.
Pay is rate times hours, and that multiplication only behaves in decimals. Typing 7:30 straight into a field expecting 7.5 hours is the single most common timesheet error there is, and it silently shortchanges whoever gets paid from it. Converting first, to 7.50, makes $20 times 7.5 come out to the $150 it should be.
Forward: a shift of 8 hours 40 minutes is 8 plus (40 divided by 60), which is 8.67 decimal hours. Backward: a payroll line reading 6.25 hours is 6 whole hours plus 0.25 times 60, or 6 hours 15 minutes. There is a third way to see the same number too: 6.25 hours is also 375 total minutes, which is closer to what a digital time clock actually stores before it ever gets formatted for a human to read.
Reformatting to decimal is purely cosmetic where pay rules are concerned. Writing 45 hours as 45.00 doesn't erase the fact that 5 of those hours cross the FLSA's 40-hour overtime line; convert first, then apply the regular/overtime split on the resulting number. And if you're converting back and forth more than once, round only at the very last step; rounding after every conversion compounds small errors that a single final rounding avoids.
Say a week of punches adds up to 38 hours 50 minutes. Type 38:50 into the converter and it returns 38.83 hours, and 2,330 total minutes as the cross-check. At $18.50 an hour, 38.83 times 18.50 comes to $718.36. Here is the fine print worth knowing: the exact figure, 38 and five-sixths hours times $18.50, is $718.42. Six cents of that pay evaporated when the hours were rounded to two decimals before the multiplication instead of after. Six cents is nothing on one check. It is also why payroll software carries full precision internally and rounds only the final dollar figure, and why you should too if you are auditing a stub by hand.
This converter reports your time as entered. An employer's time clock may have already rounded the punches. Federal regulation 29 CFR 785.48(b) accepts recording start and stop times to the nearest 5 minutes, tenth of an hour, or quarter hour, on the condition that the practice averages out and does not shortchange anyone over time. Quarter-hour rounding is where the well-known 7-minute split comes from: clock in at 8:07 and the record reads 8:00, clock in at 8:08 and it reads 8:15. If your converted decimal never quite matches your pay stub, rounded punches are the first place to look, not this arithmetic.
The reverse direction gets less attention but causes just as many double-takes. A payroll line of 6.85 hours converts to 6:51, since 0.85 times 60 is 51 minutes, and the tool confirms it as 411 total minutes. Nobody clocks a shift that lands on 51 minutes by accident; a figure like that is usually the sum of several rounded punches, which is your cue to pull the individual days rather than assume a typo.
A lot of the traffic to this page is one person staring at one payroll field, unsure whether it wants 7:30 or 7.5. There is no universal answer, but the patterns are strong. Payroll entry grids almost always take decimals. Time-clock displays almost always show hours and minutes. The trouble lives at the border, where a number read off one screen gets typed into the other.
| Where you're typing | What it usually expects |
|---|---|
| ADP hour fields (RUN, Workforce Now) | Decimal hours, so 7:30 goes in as 7.5 |
| Gusto payroll entry | Decimal hours |
| Paychex Flex | Decimal hours |
| QuickBooks Time | Either; an admin picks H:MM or decimal display in company settings |
| UKG (formerly Kronos) timecards | Configurable; many sites display hundredths of an hour |
| An Excel or Sheets cell | 7:30 is read as a clock time, not as 7.5 hours |
Setups vary by employer, so a quick test beats any chart: type a colon. A field built for decimals will reject 7:30 or mangle it, and a field built for H:MM will take it cleanly. Thirty seconds on a throwaway entry settles the question for good.
This tool reports hundredths, two decimal places, because that is what nearly every payroll field accepts. Some timekeeping systems keep only tenths. In a tenths system, 8:20 shows up as 8.3, and 8.3 hours reads back as 8 hours 18 minutes; two minutes of your shift just moved. That is not a malfunction. Rounding to the nearest tenth of an hour is one of the three methods 29 CFR 785.48 names as acceptable, on the usual condition that it averages out rather than always cutting the same direction. Thousandths run the other way: 8.333 for 8:20 only earns its extra digit when you are auditing, where it keeps a week of small roundings from stacking into a visible gap.
The minutes table at the top of the page handles the fraction. This one handles whole shifts, for the lengths that actually appear on schedules.
| Shift (H:MM) | Decimal | Total minutes |
|---|---|---|
| 4:15 | 4.25 | 255 |
| 5:30 | 5.50 | 330 |
| 6:45 | 6.75 | 405 |
| 7:20 | 7.33 | 440 |
| 7:30 | 7.50 | 450 |
| 7:45 | 7.75 | 465 |
| 8:10 | 8.17 | 490 |
| 8:15 | 8.25 | 495 |
| 8:20 | 8.33 | 500 |
| 8:40 | 8.67 | 520 |
| 9:30 | 9.50 | 570 |
| 10:45 | 10.75 | 645 |
| 12:00 | 12.00 | 720 |
A quieter version of the 7.30 mistake happens inside spreadsheets. Someone keeps a weekly hours column, enters most days as decimals, 7.5 and 8.25 and so on, then enters one day as 7:30 because that is how the time clock displayed it. Excel stores that 7:30 as 0.3125, a fraction of a 24-hour day, and the column total quietly drops by about seven hours with no error message anywhere. If a weekly sum ever looks impossibly low, scan the column for a stray colon before you question anything else. One format per column; convert at the door.
Payroll clerks are not the only people doing this division. Law firms bill in tenths of an hour, six-minute blocks, and round up: a 25-minute client call spans five of those blocks once you round, so it invoices as 0.5. PTO accrual runs on decimals too, since 120 hours of annual leave spread over 26 biweekly paychecks comes to 4.62 hours per check, a figure that simply has no clean H:MM form. Freelancers hit it at invoice time, when a month of logged sessions totaling 14 hours 50 minutes has to become 14.83 before it can meet an hourly rate. Different jobs, same division by 60.
The tool always shows a second line, the total in raw minutes, and that line is not decoration. It is the cross-check. If you convert 7:45 and get 7.75, the "Also" line reading 465 minutes confirms it, because 7 times 60 plus 45 is 465. A wrong entry breaks that agreement immediately: type 7.45 by mistake and the minutes line reads 447, a number that matches no shift on your schedule. Whenever a converted figure is headed for a paycheck, glance at the minutes line before you copy anything. Two seconds, and it catches the exact class of typo that two-decimal numbers make invisible.
Sources: DOL Fact Sheet 22, Hours Worked under the FLSA, 29 CFR 785.48, Use of time clocks.
Last updated July 18, 2026.
Because most payroll fields only accept two decimals anyway. Ten minutes is really 0.1666 repeating; rounding to 0.17 is accurate enough for a pay calculation and matches what a timesheet field expects.
Yes, indirectly. Divide your minute total by 60 to get whole hours and a remainder, enter that as H:MM, and the tool will give you the decimal. Or just divide the raw minutes by 60 yourself; that is exactly what this tool does.
No. Decimal hours are a format, not a pay rule. Whether 5 of your 45 hours count as overtime depends on the FLSA's 40-hour threshold, which applies the same way whether the total is written as 45.00 or 45 hours.
Round once, at the very end. Converting H:MM to decimal and back repeatedly, rounding at each step, compounds small errors. Keep full precision through your calculations and round only the number you actually report.
Probably not. A system that keeps tenths of an hour displays 8:20 as 8.3, which reads back as 8 hours 18 minutes. Tenth-hour rounding is permitted under 29 CFR 785.48 as long as it averages out over time instead of always cutting against you.
Add the H:MM values first and convert once if you can. Converting daily means rounding daily, and five small roundings can drift a minute or two by Friday. One conversion at the end rounds once.
No. 0.75 hours is 45 minutes, since 0.75 times 60 is 45. Seventy-five minutes converts the other direction, to 1.25 hours.
Excel and Google Sheets store clock times as fractions of a 24-hour day, and 7.5 divided by 24 is 0.3125. Multiply the cell by 24 and format it as a number to get 7.5 decimal hours.