How this instrument works
A second is one of seven SI base units, and since 1967 it has been tied to nothing physical at all: it is 9 192 631 770 periods of radiation from a specific hyperfine transition in caesium-133. An hour, by contrast, holds no SI status whatsoever. BIPM merely lists it among units accepted for use alongside SI, defined as 60 minutes of 60 seconds each — so 1 h = 3600 s holds by agreement, never by measurement.
That 3600 traces back through two ancient habits stacked on top of each other. Egyptian astronomers split daylight and darkness into twelve parts apiece; Greek and Islamic astronomers, calculating in Babylonian base-60 fractions, then subdivided each part twice over. Medieval Latin named those subdivisions pars minuta prima and pars minuta secunda — first small part, second small part — which is why we say minute and second today. Equal-length hours only became normal once escapement clocks arrived; earlier hours stretched through summer and shrank through winter.
Seconds dominate wherever a machine keeps score: build logs, uptime counters, Unix epoch arithmetic, DNS record lifetimes, video timecode, lap timing, kiln firing schedules and infusion pumps all count in whole seconds. People, though, plan in hours. Bridging those two habits is this page's whole purpose, and its one subtlety is decimal: 1 ÷ 3600 = 0.0002777… repeating without end, because 3600 carries factors of three that no decimal expansion can clear.
- Type your interval into Seconds (s) — 7200 is preloaded as a starting point.
- Read Hours (h) directly beneath; that figure recomputes as you type.
- Multiply anything after your decimal point by 60 to recover leftover minutes.
- Going backwards? Multiply hours by 3600 and enter that count in Seconds (s).
Worked example — a 7200-second build log
Your continuous-integration server reports that last night's job ran for 7200 seconds, and a weekly summary wants that figure in hours. Type 7200 into Seconds (s); Hours (h) reads 2. Arithmetic stays clean here because 7200 is simply twice 3600, one of a handful of intervals landing on a whole number.
Most durations prove less obliging. A 7250-second run returns 2.013889 hours; multiply that trailing 0.013889 by 60 and you get 0.8333 minutes, or 50 seconds, so an honest reading is 2 h 0 min 50 s. Timesheet disputes usually begin with somebody treating a decimal tail as minutes without doing that step.
Questions
Is one hour exactly 3600 seconds?
Yes, by definition rather than by measurement. An hour is defined as 60 minutes and a minute as 60 seconds, giving 3600 exactly, with no uncertainty to propagate. BIPM classifies minute, hour and day as non-SI units accepted for use with SI precisely because these ratios sit fixed and universal. One exception lives in civil timekeeping: a UTC hour containing a leap second runs to 3601 seconds on a clock face.
Why does 0.000277777777778 end in an 8?
Because it is 1⁄3600 rounded, and rounding off a run of sevens pushes that final digit up. 3600 factors into 2⁴ × 3² × 5², and those threes guarantee its reciprocal repeats forever in base ten: 0.000277777… So any stored decimal is a truncation of an exact fraction. Twelve significant figures holds error near one part in a trillion, far smaller than anything a stopwatch, log file or payroll system can resolve.
How do I turn decimal hours into hours and minutes?
Keep your whole number as hours, then multiply what remains by 60. So 2.75 h means 2 hours plus 0.75 × 60 = 45 minutes. A common slip is reading 2.75 as two hours and seventy-five minutes, or dividing by 100 out of habit from percentages; both inflate your total. Repeat that trick once more, multiplying any leftover fraction of a minute by 60, and seconds drop out.
Do leap seconds affect this conversion?
Not for elapsed time, which is what this sheet handles. A count of seconds ticked off by a monotonic clock, a stopwatch or TAI converts at a flat 3600 with no exceptions at all. Leap seconds only complicate a reverse trip: subtracting two UTC wall-clock timestamps can silently swallow an inserted second. CGPM resolved in 2022 to retire leap-second insertion no later than 2035, which removes that ambiguity for good.
What do familiar intervals look like in seconds?
An eight-hour shift is 28 800 seconds, a day is 86 400, a week is 604 800, and a 365-day year is 31 536 000. A 90-minute football match runs 5400 seconds, or 1.5 hours. These double as sanity checks: if a log claims some job ran 400 000 seconds, that is about 111 hours, and somebody ought to go looking.
Does this handle fractional seconds?
Yes. Seconds (s) steps in thousandths, so 0.5 or 12.345 are accepted and scale identically — 12.345 s becomes 0.003429 h. Machine logs often carry millisecond or microsecond resolution, and dividing by 3600 cares nothing about where a decimal point sits. Hours simply turn into an awkward unit below about a minute, where seconds or milliseconds read far better.