Time Difference Calculator – Hours and Minutes Between Two Times

Your span on the clock face of a day

The coloured stretch is your span, placed inside one 24-hour day — the gold end is the finish. Cross midnight and the span wraps around the right-hand edge and comes back in on the left.

How it works, in 3 steps

The arithmetic behind it

Deep dives

The break ladder: same shift, three pay packets

The default shift — 9:15 AM to 5:45 PM — is 8h 30m, 510 minutes, 30,600 seconds, 8.50 decimal hours, before any break. Only the unpaid break changes below, so each row isolates exactly what the break costs.

The first thing the ladder teaches is that the total span and the pay time are different numbers that happen to coincide when there is no break. With no break set, the pay time is the full 8h 30m and 8.50 decimal hours. Take 30 minutes off for lunch and the span is still 8h 30m — you were, after all, away from home for that long — but the pay time drops to exactly 8h 0m, or 8.00 decimal hours. Take a full hour and the pay time is 7h 30m, or 7.50 hours. The arithmetic is subtraction followed by division: 510 − 30 = 480 minutes, and 480 ÷ 60 = 8.00; 510 − 60 = 450 minutes, and 450 ÷ 60 = 7.50. The reason the page prints both styles is that payroll does not speak in hours and minutes — it speaks in decimals — and the conversion is the single most common timesheet error there is: 8.50 is eight and a half hours, not “eight hours fifty”.

The second lesson is about what the break does not do. It does not change the start, the finish, the total minutes or the total seconds; it only changes the two pay rows. That separation is deliberate, because the two questions — “how long was I there?” and “how long am I paid for?” — have different answers whenever a break is unpaid, and collapsing them into one figure is how payslips get argued about. If your break is paid, leave it at zero: a paid break is part of the span and part of the pay, and the page’s pay time then correctly equals the span.

Decimal hours: the conversion table to keep

Payroll’s decimal system is just minutes divided by 60, but the quarter-hour landmarks are worth memorising because they recur on every timesheet. Fifteen minutes is 0.25 hours, thirty minutes is 0.50, forty-five is 0.75, and ninety minutes is 1.50 — the same division every time, with no special cases. The default shift’s 510 minutes divide to exactly 8.50, which is why the default is such a clean example: 8 hours plus 30 minutes is 8 + 30/60 = 8.50, not 8.30 and not 8.5-something-else. The confusion to avoid is reading a decimal as clock digits: 8.50 hours is 8 hours 30 minutes, while 8.30 hours would be 8 hours 18 minutes (0.30 × 60 = 18). If a payslip ever shows a decimal that does not convert back to whole minutes, something has been rounded — and the next section explains how much rounding to expect.

When seconds change the answer, and when they do not

Seconds are optional on this page — leave them at zero and nothing changes — but they are not decorative. Move the start thirty seconds later, to 9:15:30 AM, and the same shift to 5:45 PM becomes 8h 29m 30s: 509.5 minutes, 30,570 seconds, 8.49 decimal hours. Thirty seconds removed thirty seconds from the span, exactly as it should, and the decimal moved from 8.50 to 8.49 because 509.5 ÷ 60 is 8.4916…, displayed to two decimals. For most shifts that precision is noise — nobody’s pay depends on thirty seconds — but for timed events, races, laboratory work or any span where the second is the unit that matters, the page carries it faithfully instead of rounding it away at the input. The rule of thumb is simple: if the thing you are timing is measured in seconds, type the seconds; if it is measured in hours, leave them at zero and the answer is identical either way.

One honest wrinkle belongs here, and the page’s own deep dive states it: employers often round. Many workplaces round punches to the nearest 5 minutes, tenth of an hour (6 minutes) or quarter hour, and US practice has long allowed neutral rounding of that kind — it has to round up as often as it rounds down. So the figure here is the exact span, down to the second, and your employer’s rounded version may sit a few minutes either side of it. If a payslip looks wrong by more than a rounding step, the exact figure from this page is the one to take to the conversation; if it differs by less than a rounding step, the difference is the rounding, not an error.

Night shifts and multi-day spans, without the nonsense answer

The two features that turn clock arithmetic into real-world arithmetic are the “next day” box and the dates switch, and the page’s own worked examples show both. The night shift — 10:30 PM to 6:15 AM — is 1,350 minutes after midnight to 375 minutes after midnight, and without the next-day box that subtraction goes negative, a nonsense answer. Tick the box and the finish counts as tomorrow: 375 + 1,440 (a full day of minutes) = 1,815, and 1,815 − 1,350 = 465 minutes, or 7h 45m. The multi-day version works the same way with whole days at 1,440 minutes each: 9:00 AM on 20 October to 5:00 PM on 23 October is 3 full days (4,320 minutes) plus the 480 minutes from 9:00 AM to 5:00 PM — 4,800 minutes, exactly 80.00 hours. In both cases the method is the same: convert everything to a position on a timeline first, then subtract. That is also why the twelves can never leak into the answer — by the time any arithmetic happens, 12:00 AM has already become 0 seconds since midnight and 12:00 PM has become 43,200, and there are no twelves left to confuse.

Split shifts and the 40-hour week, added up properly

Not every working day is one unbroken span. A day split by a long unpaid gap is two spans, and the page handles it by running each span separately and adding the results — which is exactly what this section does, with both halves verified on the page.

Take a day that runs 9:15 AM to 12:00 PM, then 1:00 PM to 5:45 PM, with the hour between unpaid and uncounted. The morning span is 2h 45m — 165 minutes, 9,900 seconds, 2.75 decimal hours — and the afternoon span is 4h 45m — 285 minutes, 17,100 seconds, 4.75 decimal hours. Add them: 165 + 285 = 450 minutes, which is 7h 30m and 7.50 decimal hours for the day. Note that the naive approach — running 9:15 AM to 5:45 PM as one span and subtracting the hour — gives the same 7h 30m here, because the gap is exactly the break the page would subtract. The two-span method earns its place when the gap is not a break at all: a second job, a call-out, a gap spent elsewhere, where treating it as “break” would mislabel the day even though the minutes agree. Minutes do not carry labels; your records should.

The weekly version of the same addition is where decimal hours stop being a curiosity and start being money. Five default shifts with a 30-minute unpaid break each pay 8.00 hours a day, which is exactly 40.00 hours for the week — the round number is no coincidence, since 5 × 8.00 = 40.00, and it is why the 30-minute lunch on an 8h 30m span is the most common shift pattern in office work: it is the pattern that makes the week come out even. Five shifts with no break pay 5 × 8.50 = 42.50 hours, which is 2.50 hours over 40 — the overtime line in many workplaces, and the reason the break row matters to the weekly total far more than it matters to any single day. Run each day separately, add the decimal hours, and compare with the weekly threshold your contract sets: the page gives you the daily figures exactly, and the weekly figure is their sum, nothing more mysterious than that.

A worked rounding example makes the employer’s side concrete. Suppose a shift runs 8h 37m — 517 minutes — and the workplace rounds to the nearest quarter hour. The neighbouring quarter-hour marks are 510 minutes (8.50 hours) and 525 minutes (8.75 hours); 517 sits 7 minutes from the lower mark and 8 from the upper, so neutral rounding gives 8.50 hours, seven minutes less than the exact span. The next day, a shift of 8h 38m — 518 minutes — sits 8 minutes from the lower mark and 7 from the upper, so it rounds up to 8.75 hours, seven minutes more than exact. Over many shifts those ups and downs roughly cancel, which is the whole justification for neutral rounding — but on any single payslip, a difference of up to half a rounding step in either direction is expected, and only a difference larger than a full step is evidence of an error rather than a rounding rule.

One more addition deserves a warning, because it is where split-shift arithmetic most often goes wrong: midnight. A split day that crosses midnight — an evening span plus an after-midnight span — must have the “next day” box applied to the second span’s own subtraction, not to the day as a whole. Run the evening span with its own finish, run the after-midnight span as its own overnight span, and add the two totals. Adding clock times across midnight without converting each span to a timeline position first is how a 2-hour evening plus a 3-hour night becomes a negative number or a 19-hour day, and the page’s method — convert to seconds since midnight, add a day where the finish belongs to tomorrow, then subtract — is the only order of operations that never produces either.

Across midnight, across months: the borrow-and-carry routine

The arithmetic is subtraction with borrowing. The skill is knowing what to borrow from.

Within one day, subtract the earlier time from the later one, borrowing an hour (60 minutes) when the minutes run short. From 22:30 to 06:45 the next day, first add 24 hours to the later time — 06:45 becomes 30:45 — then subtract: 30:45 − 22:30 = 8 hours 15 minutes, or 8.25 decimal hours. Across dates, the same idea extends: count whole days first, then the leftover hours and minutes, and let the calendar do the month lengths for you rather than assuming every month has 30 days.

Two habits prevent the common errors. First, always state whether both endpoints are included: the difference between 09:00 Monday and 09:00 Tuesday is 24 hours of elapsed time but only one working day if the endpoints are shifts, and the two answers serve different questions. Second, convert to a single unit before subtracting — minutes since midnight, or decimal hours — whenever the times are awkward. Decimal conversion is exact (15 minutes = 0.25 hours, 45 minutes = 0.75 hours) and avoids the trap of writing 8 hours 30 minutes as 8.30 hours, which understates the span by 18 minutes.

Time zones inside a difference: convert first, subtract second

Subtracting wall-clock times in different zones gives a nonsense answer. Convert both to one reference, then subtract.

A 09:00 call in New York and a 14:00 call in London on the same day are the same moment, not five hours apart — London is five hours ahead, so 14:00 London is 09:00 New York. The routine is: convert both times to UTC (or to one of the two zones), then subtract. The same routine handles date-line crossings: a Monday evening departure from Tokyo can arrive in Los Angeles on Monday morning, and only the UTC conversion keeps the elapsed time positive and sane.

Daylight saving is where the routine earns its keep. On the spring-forward day, 01:00 to 03:00 local time spans one hour of elapsed time, not two, because 02:00 never happened; on the fall-back day the same wall-clock span is three hours, because 01:00 happened twice. A difference calculator that uses fixed offsets will get both days wrong. This page’s companion time-zone logic uses the actual offset for the exact date, which is why a difference that crosses a changeover must be calculated from real zone data, not from a remembered “five hours” rule.

Time difference questions, answered

Related calculators