Time Unit Converter

Quick Reference

Common second-to-hour conversions at a glance — from 30 seconds up to one full week. The Duration column shows the equivalent h:mm:ss breakdown.

Days to Hours Reference

Common day-to-hour conversions for project planning and scheduling.

The Unit Relationships

All time unit conversions flow from two fixed ratios: 60 seconds per minute and 60 minutes per hour. Everything else multiplies out — 3,600 seconds per hour, 86,400 seconds per day, 604,800 seconds per week. To convert any unit to any other, convert to seconds first as an intermediate, then divide by the target unit's factor.

For the duration breakdown from a raw second count: days = floor(s ÷ 86400), remaining hours = floor((s mod 86400) ÷ 3600), minutes = floor((s mod 3600) ÷ 60), seconds = s mod 60. For example, 5,000 seconds = 1 hour, 23 minutes, and 20 seconds (1:23:20). This format is used universally in video players, timecodes, stopwatches, and duration displays.

Decimal vs. Compound Units

Time values are often expressed as decimals in technical contexts — 1.5 hours, 2.75 minutes — because spreadsheets, APIs, and billing systems prefer continuous numbers over compound formats. The conversion is direct: 1.5 hours = 90 minutes = 5,400 seconds. 0.25 hours = 15 minutes = 900 seconds. Multiplying decimal hours by 60 gives decimal minutes; multiplying again gives seconds.

The reverse — converting seconds or minutes back to a compound duration — requires integer division and modulo rather than simple multiplication, which is why a calculator is more practical than mental arithmetic for larger values.

Practical Benchmarks

Values worth knowing by heart: 60 seconds = 1 minute. 3,600 seconds = 1 hour. 86,400 seconds = 1 day. 1,440 minutes = 1 day. 10,080 minutes = 1 week. 168 hours = 1 week. 8,760 hours = 1 year (non-leap). These come up constantly in programming — cache TTLs, session timeouts, rate limit windows, and cron intervals are all typically specified in seconds or minutes.

Working Hours vs. Total Hours

Total hours in a period (all 24 h/day) differs significantly from available working hours. A 30-day calendar month has 720 total hours but only roughly 160–176 working hours (20–22 business days × 8 h). A 7-day week has 168 total hours but only 40 standard working hours. When scheduling projects, be explicit about whether you mean calendar hours or working hours to avoid capacity overestimates.

Why 60?

The base-60 (sexagesimal) system for time comes from ancient Babylon, adopted around 2000 BCE. The Babylonians chose base 60 because it is highly composite — divisible by 1, 2, 3, 4, 5, 6, 10, 12, 15, 20, and 30 — making it easy to split an hour into halves, thirds, quarters, fifths, and sixths without fractions. This practical divisibility kept the system alive through Greek and Arabic astronomy into the modern world, where it remains the global standard for measuring time.

Frequently Asked Questions

Related Tools

• Time to Decimal — Convert h:mm to decimal hours for billing and payroll
• Days Between Dates — Count the days between two dates
• Work Hours Calculator — Calculate total hours between clock-in and clock-out
• Military Time Converter — Convert between 12-hour and 24-hour formats