Live HMS-versus-decimal board — so 2:15 never pretends to be the same paste as 2.15 hours.
Educational HMS ≠ decimal sketch. Not a punch-clock timesheet, calendar day count, or wall-clock span.
By Ahmet C. Toplutaş·Site owner & editor · Time & duration tools
Last updated May 21, 2026 · Reviewed May 21, 2026 · Planning estimates only - not tax, medical, or investment advice
01
Duration math looks simple until you paste the answer. 2:15:20 and 2.2556 hours are the same seconds — different paste contracts. A portal that wants HH:MM will misread a decimal; a spreadsheet that wants hours will misread a colon string.
This page’s framing is HMS ≠ decimal. Add or subtract two durations, then read the twin board: canonical HMS after carry versus decimal hours (and total minutes). The seconds underneath are one clock; the paste targets are two.
That is a different job from the hours calculator (clock vs paid: start/end shifts, breaks, overnight) and from the day counter (inclusive ≠ exclusive calendar spans). Here we stay on duration arithmetic — not punch-clock payroll and not how many midnights fall between two dates.
Decision framing: “Am I pasting a colon duration — or a decimal hour float?”
02
The unique affordance is the twin readout: canonical HH:MM:SS (signed when needed) versus decimal hours, with total minutes as a bridge. Flip Meeting stack → Carry paste. Both can land on similar totals while carry notes and narratives diverge — HMS ≠ decimal made visible, not a vs-8h payroll strip and not an inclusive/exclusive day dual-count.
Keep the operation fixed. Change only whether you enter 1h30 or 0h90. The board should normalize to the same HMS while the carry chip tells you raw minutes overflowed — that is the product.
03
Entering 90 minutes is valid raw input. Internally everything becomes seconds; the display carries into hours and minutes. Carry-heavy narrative flags when either duration’s minutes or seconds sit at 60+. That habit prevents “90” in a minutes field from being treated as a clock minute digit on a wall face.
Signed-gap narrative appears when subtraction crosses zero. The board keeps the minus on both HMS and decimal hours — silent absolute values hide overtime shortfalls and buffer mistakes.
Load Carry paste (90m + 75m). Read HMS, decimal, and the carry note — same seconds, honest normalize.
04
Long totals also expand into a days · hours · minutes · seconds ladder, with remainder HMS under the day boundary. That is for multi-day podcast queues and event run-of-show stacks — still duration math, not a calendar inclusive count.
When the ladder’s day component is zero, remainder HMS matches the twin board’s canonical string (aside from sign formatting). Use the ladder when you need to say “one day and four hours” out loud; use decimal hours when a timesheet column wants a float.
05
Each duration converts to seconds (hours×3600 + minutes×60 + seconds). Add or subtract. Rebuild HMS from absolute seconds with an optional sign. Decimal hours are totalSeconds ÷ 3600.
Seconds are truncated to whole seconds for HMS display. This is educational duration math — not leap-second astronomy and not a wall-clock difference across midnight.
06
After HMS ≠ decimal, hand off for punch-clock hours, calendar day counts, wall-clock differences, or date arithmetic.
07
Scenario A — Meeting stack. 1h30 + 45m30. Twin board shows canonical HMS and decimal hours for the same seconds — choose the paste form your agenda tool wants.
Switch to Overtime gap without changing the framing. Subtract shows leftover duration — still HMS ≠ decimal, not a shift start/end punch.
Scenario B — Carry paste. 90m + 75m. Carry-heavy chip; HMS normalizes. Proves raw minute overflow is allowed input, not a clock digit.
Scenario C — Signed gap. 2h − 3h15. Negative HMS and decimal — the shortfall stays visible.
Scenario D — Multi-day ladder. Stack large hour totals and read days on the ladder. Still duration arithmetic — hand calendar inclusivity to the day counter.
08
09
10
Stop here for duration add/subtract literacy across HMS and decimal paste targets. Hand off for punch-clock hours, calendar days, wall-clock spans, or date math.
11
Canonical duration after carry is HH:MM:SS (or a day ladder). Decimal hours (2.2556 h) are a different paste target. Mixing them is how a timesheet gets 2.25 when you meant 2:15 — HMS ≠ decimal.
Hours owns clock-vs-paid: start/end shifts, unpaid breaks, overnight. This page owns duration arithmetic — add or subtract two HMS values — not a punch-clock span.
Day counter owns inclusive ≠ exclusive for calendar dates. Here we stay on hours, minutes, and seconds as durations — not how many midnights fall between two dates.
Entering 90 minutes is valid raw input; the board normalizes to 1:30:00. Carry-heavy narrative flags when inputs exceed 59 in minutes or seconds before normalize.
Subtracting a larger duration from a smaller one yields a negative total. The board keeps the sign on HMS and decimal hours so you see the gap — not a silent absolute value.
No. It adds or subtracts durations. For wall-clock A to wall-clock B (including time zones), use the time difference or time zone tools.
No. Inputs hydrate from the URL on load; Share / Copy link writes query params when you choose to share.
LIVE DURATION · HMS ≠ DECIMAL
HMS ≠ decimal ↓Scene presets
Operation
h
m
s
h
m
s
Minutes/seconds may exceed 59 — the board carries them into HMS.
HMS ≠ DECIMAL BOARD
Canonical HMS
2:15:30
After carry · A + B
Decimal hours
2.2583 h
135.5 min
UNIT LADDER
days
0
hours
2
min
15
sec
30
Remainder HMS (under day): 2:15:30
A: Inputs already in carry-safe ranges · B: Inputs already in carry-safe ranges
Updates as you type. Share writes the URL; typing does not. Duration math — not a punch-clock span or calendar day count.
HMS ≠ decimal
2:15:30
HMS and decimal aligned to the same seconds · 2.2583 h
Copy the link to save or share your results.