Article — Hours to Seconds Converter
Hours to seconds: an exact 3,600 conversion
One hour equals exactly 3,600 seconds. The number comes from two consecutive 60s: 60 minutes per hour, 60 seconds per minute. Both factors are fixed by the International Bureau of Weights and Measures, so the hour-to-second conversion contains no rounding at all.
To convert hours to seconds: multiply by 3,600. To go the other way: divide by 3,600. The converter above handles both directions and supports decimal hours, which is useful when working with timeouts, video lengths, work shifts, scientific timing and Unix timestamps.
How many seconds in an hour
3,600 exactly. The hour is one of the non-SI units that the BIPM has formally accepted for use with the International System of Units. Its value is defined as 60 minutes, each of which is defined as 60 seconds. The product is 3,600 seconds — not an experimental quantity, just an arithmetic consequence of two exact definitions.
The second itself is one of the seven SI base units. Since 1967 the second has been defined as the duration of 9,192,631,770 periods of the radiation corresponding to the transition between two hyperfine levels of the ground state of the caesium-133 atom. Modern atomic clocks reach accuracies of one second over a hundred million years.
The hours-to-seconds formula
The formula is short:
seconds = hours × 3,600 1 h → 3,600 shours = seconds ÷ 3,600 7,200 s → 2 h0.5 h = 1,800 s2.5 h = 9,000 sBoth directions are exact. The conversion holds for any value of hours, positive or zero, with no measurement error. It is one of the simplest and most reliable unit conversions in metrology.
Why an hour is 3,600 seconds
The hour-to-second relationship is the product of the 24-hour day and the 60-minute hour, both of which trace back to ancient astronomy. The Egyptians divided daylight and night into 12 hours each by tracking decan stars, giving the 24-hour day. The Babylonians divided each hour into 60 minutes and each minute into 60 seconds because base-60 arithmetic has many integer divisors and made daily life calculations easy.
When the metric system was formalised after the French Revolution, decimal time competed briefly with sexagesimal time. Revolutionary France introduced a 10-hour day with 100 decimal minutes per hour and 100 decimal seconds per minute, making a "metric hour" of 10,000 metric seconds. The reform lasted from 1793 to 1795 and was abandoned because retraining the population was unworkable. The 3,600-second hour stayed.
Unix time, the basis for almost every server clock on the internet, counts elapsed seconds since 1 January 1970 at 00:00:00 UTC. As of mid-2026 the value sits near 1.78 billion. The Year 2038 problem — the moment Unix time overflows a 32-bit signed integer at 2,147,483,647 seconds (19 January 2038, 03:14:07 UTC) — is a hours-to-seconds question scaled up to 68 years.
Hours to seconds for software timeouts
Most software systems express timeouts in seconds, not hours. Common settings: HTTP cache lifetimes (3,600 s = 1 h is the default in many CDN configurations), session cookies (1,800 s = 30 min or 86,400 s = 24 h), OAuth refresh tokens (often 3,600 s), and DNS time-to-live (commonly 3,600 s for stable records or 60-300 s for actively rotating ones).
Scheduler jobs accept seconds too. A cron-equivalent rule like "run every 2 hours" maps to 7,200 seconds. A nightly backup window of 4 hours equals 14,400 seconds. Knowing the exact conversion is useful when interpreting log entries that record durations in seconds and need to be compared against human-readable hour-scale settings.
Decimal hours versus HH:MM:SS
Two notations dominate. Decimal hours (1.5 h) express duration as a base-10 number. HH:MM:SS (1:30:00) splits the same duration into hours, minutes and seconds. The two are interchangeable but easy to mix up.
1.5 hours is 1 hour 30 minutes, not 1 hour 50 minutes. The decimal portion (0.5) represents half an hour, which is 30 minutes. The conversion: decimal part of hours × 60 = minutes part. For 2.25 h, the decimal 0.25 becomes 15 minutes, so 2.25 h = 2:15:00.
This is the most common hours-to-seconds error. The decimal 0.5 represents half an hour = 30 minutes, not 50. Multiply the decimal portion by 60, never read it as minutes directly. For seconds, 1.5 h × 3,600 = 5,400 s.
Hours to seconds in media and video
Video editing software stores durations in seconds (or in frame counts which themselves derive from seconds and the frame rate). The hours-to-seconds conversion matters when planning timelines, fades and transitions.
- YouTube short — up to 60 s (0.017 h)
- Sitcom episode — 22 min = 1,320 s (0.37 h)
- Drama episode — 60 min = 3,600 s (1 h)
- Feature film — 2 h = 7,200 s
- Marvel epic — 3 h = 10,800 s
- Mahler symphony — 90 min = 5,400 s
Shift work and large time spans
A standard 8-hour work day is 28,800 seconds. A 12-hour nursing shift is 43,200 seconds. A full week of 40 hours is 144,000 seconds. A month (730 hours on average) is 2.628 million seconds. A 99.9% SLA over one month tolerates 0.73 hours of downtime, or 2,628 seconds — about 44 minutes.
For astronomy and physics, larger spans matter: a year is 31.5 million seconds (8,766 hours including the leap-day average). The half-life of technetium-99m, used in medical imaging, is 6 hours = 21,600 seconds. The orbital period of the International Space Station is about 92 minutes = 5,520 seconds.
When reading server logs or duration fields, anything above 86,400 is likely days expressed in seconds. 604,800 is one week. 2,592,000 is 30 days. Recognising these constants speeds up debugging.
Hours-to-seconds mistakes to avoid
Treating 1.5 h as 1:50:00. It is 1:30:00. The decimal portion of a decimal-hour value multiplies by 60 minutes, not by 100.
Confusing the hour with the day. 24 h is one full day = 86,400 s. A 24-hour timeout is therefore 86,400 seconds in a config file, not 24.
Mixing time zones with duration. A duration of 3 hours is always 10,800 seconds. A clock-time of "from 14:00 to 17:00" can be 3 hours, 4 hours or 2 hours depending on daylight saving transitions. Durations are always exact; calendar arithmetic is not.
Forgetting leap seconds. Civil time occasionally adds a leap second to keep UTC aligned with Earth's rotation. For ordinary hours-to-seconds conversion this never matters; for navigation, telecommunications and stock-exchange timestamps it does.