gizmobench
BrowseDaily

Seconds to Days Converter

A day here is exactly 86,400 seconds, because 24 hours of 60 minutes of 60 seconds is 24 × 60 × 60, so seconds to days is one division: days = seconds / 86,400. That makes 3,600 seconds 0.0416666666667 days, 100,000 seconds 1.15740740741 days and 1,000,000 seconds 11.5740740741 days. This page opens the converter already set to seconds and days, ahead of whatever pair you last used, prints the answer to twelve significant digits as you type, and lists the same span in milliseconds, minutes, hours, weeks and Julian years underneath. These are fixed scalar durations, with no date, time-zone or leap-second model. A supplied 86,401-second span can represent a UTC day with a positive leap second; supplied 82,800- and 90,000-second spans illustrate 23- and 25-hour days for one-hour clock changes. Those examples do not bound all civil-calendar changes. Duration Calculator accepts unambiguous local Gregorian endpoints in the device’s zone, distinguishes calendar fields from elapsed time and refuses skipped or repeated endpoint times; it has no named-zone or UTC-offset selector.

To0.0000115740740741
Category
Time
Base unit
second
Uncommon units

One day is fixed at 86,400 seconds, one week at seven days and one Julian year at 365.25 days. This is duration arithmetic, not a calendar or timezone calculation.

Results round to 12 significant digits using the listed unit definitions. Input must have a finite numeric magnitude and at most 512 significant digits. Type a single decimal or scientific number; a matching From unit suffix is accepted. Commas and grouped spaces separate thousands; decimal commas, fractions and compound measurements are refused.

1 s in every time unit

  • Millisecondms
    1,000
  • Minutemin
    0.0166666666667
  • Hourh
    0.000277777777778
  • Dayd
    0.0000115740740741
  • Weekwk
    0.00000165343915344
  • Year (Julian)yr
    3.1688087814e-8
Selectable complete conversion

Seconds to days, hours and minutes

Every figure is this page's own output for that number of seconds, at a fixed 86,400-second day. Values that land on a whole number of days, like 86,400 and 604,800 seconds, come back exact.

SecondsDaysHoursMinutes
1 s0.00001157407407410.0002777777777780.0166666666667
60 s0.0006944444444440.01666666666671
600 s0.006944444444440.16666666666710
3,600 s0.0416666666667160
43,200 s0.512720
86,400 s1241,440
100,000 s1.1574074074127.77777777781,666.66666667
172,800 s2482,880
259,200 s3724,320
500,000 s5.78703703704138.8888888898,333.33333333
604,800 s716810,080
1,000,000 s11.5740740741277.77777777816,666.6666667
2,592,000 s3072043,200
5,000,000 s57.87037037041,388.8888888983,333.3333333
10,000,000 s115.7407407412,777.77777778166,666.666667
31,536,000 s3658,760525,600
31,557,600 s365.258,766525,960
100,000,000 s1,157.4074074127,777.77777781,666,666.66667

Common questions

How many seconds are in a day?
86,400. A day of 24 hours, each of 60 minutes of 60 seconds, is 24 × 60 × 60 = 86,400 seconds, so one day is 86,400 s, two days are 172,800 s and a week is 604,800 s. Dividing by that figure is the whole conversion: 43,200 seconds comes back as 0.5 days, 259,200 seconds as 3 days and 2,592,000 seconds as 30 days.
Why can a real calendar day differ from 86,400 seconds?
These are fixed scalar durations, with no date, time-zone or leap-second model. A supplied 86,401-second span can represent a UTC day with a positive leap second; supplied 82,800- and 90,000-second spans illustrate 23- and 25-hour days for one-hour clock changes. Those examples do not bound all civil-calendar changes. Duration Calculator accepts unambiguous local Gregorian endpoints in the device’s zone, distinguishes calendar fields from elapsed time and refuses skipped or repeated endpoint times; it has no named-zone or UTC-offset selector. The supplied 86,401-, 82,800- and 90,000-second spans display as 1.00001157407, 0.958333333333 and 1.04166666667 fixed days respectively.
How do I turn a difference between two timestamps into days?
First establish that both supplied timestamps use the same Unix convention and unit, then subtract their scalar values. Unix timestamps do not count inserted leap seconds as separate Unix seconds. If the values are milliseconds, select Millisecond instead of Second. Epoch Converter can interpret supported seconds or milliseconds as instants; its automatic magnitude-based unit choice is a heuristic, so select an explicit unit when the source supplies one. Unit Converter only converts the supplied difference and does not parse endpoints or infer their epoch. Supplied differences of 1,234,567 seconds and 10,000,000 seconds display as 14.2889699074 days and 115.740740741 days. Correctly grouped 1,234,567 and 1234567 mean the same scalar.
Worked example: how many days is 500,000 seconds?
500,000 / 86,400 displays as 5.78703703704 fixed days. Derive the mixed duration from the original seconds: 5 × 86,400 leaves 68,000 s; 18 × 3,600 leaves 3,200 s; 53 × 60 leaves 20 s. That is exactly 5 fixed days, 18 hours, 53 minutes and 20 seconds. The common rows display 138.888888889 hours and 8,333.33333333 minutes. Splitting a rounded day readout can introduce a different remainder.
Can I convert days back to seconds here?
Yes. The swap button between the two boxes reverses the pair, so the page becomes days to seconds: 1 day gives 86,400, half a day gives 43,200 and 7 days give 604,800. Both unit menus remain available, so the same number will go from seconds to minutes, hours, weeks or years without leaving the page, and Copy result copies the figure exactly as printed, without the thousands separators.
What else does the page show under the answer?
The same number of seconds in every common time unit: milliseconds, minutes, hours, days, weeks and Julian years, each with its own Copy button. One million seconds reads as 1,000,000,000 ms, 16,666.6666667 min, 277.777777778 h, 11.5740740741 d, 1.65343915344 wk and 0.031688087814 yr. The Uncommon units switch in the row above adds 2 more, the nanosecond and the microsecond.
Is a year in that list 365 days?
No, it is the Julian year of 31,557,600 seconds, which is exactly 365.25 days. Using fixed 86,400-second days, 365 days is 31,536,000 seconds and 366 days is 31,622,400 seconds, and the converter cannot tell which one you mean because it holds factors rather than a calendar. Type 31,536,000 seconds and it returns 365 days exactly.
Why does the page open on seconds and days when I last converted something else?
This focused page opens on Second (s) to Day (d), while preserving the main converter’s saved unit pair. When storage is usable, a saved value and uncommon-unit preference can travel between pages. Its suffix must still match From. Valid deliberate scalar edits can save those fields after a short delay; invalid or incomplete drafts preserve the saved record. Unusable or conflicting records remain until you use Forget saved settings, which keeps the current conversion on screen.
Is anything I type sent anywhere?
Your input and converted values are calculated in the browser and are not uploaded by the converter. The definitions arrive with the page, so conversion needs no external data lookup and keeps working offline after the page has loaded. The core conversion needs no account. Copy result copies the displayed headline without digit-grouping commas; each visible conversion row has its own Copy button. Displayed and copied values round to twelve significant digits. If native copying fails, a complete selectable summary identifies the input, selected pair and conventions and includes every unit in the category, including uncommon units.

Results round to 12 significant digits using the listed unit conventions. Many factors are exact definitions; psi and parsec use rounded coefficients. Temperature includes scale offsets. Days and weeks are fixed-duration units, and unit conversion does not determine calendar dates, ambient pressure or a software label’s convention.