Seconds converter
Enter a duration in seconds and see it in minutes, hours and days at the same time: 90 seconds are 1.5 minutes and 0.025 hours, worked out with exact civil-time factors. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Seconds
- 3,600
- Result
- 60 minutes
- Minutes
- 60
- Hours
- 1
- Days
- 0.0416666667
A seconds converter turns a duration already counted in seconds into the equivalent magnitudes in minutes, hours, and days using the exact civil-time identities that one minute equals sixty seconds, one hour equals three thousand six hundred seconds, and one civil day equals eighty-six thousand four hundred seconds.
Why seconds convert at sixty, three thousand six hundred, and eighty-six thousand four hundred
A second is the SI base unit of time, and the civil minute, hour, and mean solar day used by clocks, ISO 8601 durations, payroll systems, school bells, and kitchen timers are exact integer multiples of that second. One minute contains sixty seconds; one hour contains sixty minutes and therefore three thousand six hundred seconds; one civil day contains twenty-four hours and therefore eighty-six thousand four hundred seconds.
Those three ratios are not approximations and are not calendar conventions that drift with leap days or month lengths; they are the definition of mean solar civil time used by timers that count seconds independently of a date. Converting a duration in seconds into minutes, hours, and days is therefore three exact divisions of the same input: minutes equals seconds divided by sixty, hours equals seconds divided by three thousand six hundred, and days equals seconds divided by eighty-six thousand four hundred.
Sixty seconds is exactly one minute; three thousand six hundred seconds is exactly one hour; eighty-six thousand four hundred seconds is exactly one day; ninety seconds is one point five minutes, zero point zero two five hours, and a small fraction of a day. Decimal seconds such as ninety point five keep the fractional leftover on every converted unit so a half second is not silently dropped. This landing answers the search seconds converter: a duration in seconds in, three converted durations out.
It is not a remainder breakdown that prints two days three hours four minutes leftover; every output is the full equivalent of the input in that unit. A humanize-duration phrase tool that starts from seconds and omits zero units is a related but different search. A general time-unit hub with a from-and-to dropdown does not match people who type seconds converter and want a one-field form.
Zero seconds maps to zero of every unit. Negative durations are rejected because a length of time cannot be negative in this contract. The solver never consults a clock, a timezone, or a calendar table, and it never treats a day as an eight-hour billed shift or a teaching hour of fifty minutes.
If your workplace defines a day as eight billed hours, apply that policy after this conversion, not instead of it.
Practical checks, related searches, and when not to use this
Use this converter when the quantity you already have is a second count and the quantities you need are minutes, hours, and days for planning, quoting, timers, or reporting. Typical searches include seconds converter, convert seconds to minutes hours days, how many minutes is three thousand six hundred seconds, and seconds to days calculator.
Sanity checks are easy: sixty seconds should return exactly one minute; three thousand six hundred seconds should return sixty minutes, one hour, and one twenty-fourth of a day; eighty-six thousand four hundred seconds should return one thousand four hundred forty minutes, twenty-four hours, and one day; zero seconds should return zero of every unit; ninety seconds should return one point five minutes. If you instead need a remainder phrase such as two days three hours four minutes, that is a humanize-duration landing, not this one.
Likewise, converting milliseconds into seconds is a sibling duration converter in a different unit and does not answer seconds-converter. A general time-unit converter that also speaks weeks, milliseconds, and microseconds does not match the seconds-converter search: people who type that query want a one-field form and three answers, not a unit dropdown. Stay inside the allowed range so the three divisions cannot overflow into a non-finite result the solver must reject.
Document the exact twenty-four-hour day and sixty-second minute in contracts so counterparties do not later argue that a working day of eight hours should have shortened the quote. Prefer this landing when the input is already in seconds and you need minutes, hours, and days together; keep clock arithmetic, time-zone offsets, and multi-unit time hubs on their own pages so search results stay specific.
What you can do with it
Elapsed Unix seconds to planning units
Turn an epoch delta, uptime counter, or job runtime stored in seconds into minutes, hours, and days for dashboards, postmortems, and capacity reports.
Media runtimes, races, and lab timers
Convert a video length, race clock, or instrument booking logged in seconds into hour-scale and day-scale figures for a schedule or a results table.
FAQ
What formula converts seconds into minutes, hours, and days?
Minutes = seconds / 60, hours = seconds / 3600, and days = seconds / 86400. This tool uses the exact civil-time minute, hour, and 24-hour day, not a billed hour or a working day of a different length.
What does 3600 seconds convert to?
3600 seconds is 60 minutes, 1 hour, and 0.041666666667 days (3600 / 86400). 86400 seconds is 1440 minutes, 24 hours, and 1 day. 90 seconds is 1.5 minutes, 0.025 hours, and 0.001041666667 days.
What happens on negative or non-numeric input?
Seconds must be a non-negative finite number; missing fields, NaN, Infinity, and negative values are rejected and are not billed.
Does this print a remainder string such as 2 days 3 hours?
No. Each output is the full equivalent of the input in that unit. A humanize-duration formatter that omits zero units and prints leftover parts belongs on its own landing.
Is the seconds converter free?
The browser tool is free and runs locally.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/conv/seconds-converter \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"seconds":3600}'const res = await fetch("https://api.kit.forhosting.com/conv/seconds-converter", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"seconds": 3600
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/seconds-converter",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"seconds": 3600
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/seconds-converter", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"seconds":3600}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"seconds":3600}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/seconds-converter", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"seconds": 3600
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.seconds_converter",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_abs | 1000000000000 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
People reach for this tool when a timer log, Unix epoch delta, API timeout, video runtime, race clock, SLA incident, heartbeat interval, or game tick is stored in seconds and they need all three larger units at once for a report, a calendar block, a spreadsheet, or a test assertion. Negative values and non-finite numbers fail with invalid_input instead of inventing a duration.
How to call the API and what comes back
The value must be non-negative and must stay within the published absolute limit of one trillion. Do not send a pair of clock times and expect a duration; this converter never subtracts timestamps and never reads a wall clock. Do not send a from-unit and to-unit pair either: the three target units are always minutes, hours, and days. Send a JSON body with one required finite number field named seconds. Aliases second, value, duration, secs, s, and n are accepted so SDK clients and form posts can use the name that fits the product. On success the response echoes rounded seconds, sets minutes, hours, and days to the three converted durations, copies minutes onto result for callers that expect a primary numeric field, sets converted_minutes, converted_hours, and converted_days to the same three magnitudes, unit to the token minutes, from_unit to seconds, seconds_per_minute to sixty, seconds_per_hour to three thousand six hundred, seconds_per_day to eighty-six thousand four hundred, formula to the three-division identity, message to a short English summary, and steps to an ordered array of substitution lines. Failed validation—missing fields, non-finite numbers, negative durations, bare plus or minus signs, non-numeric strings, values outside the absolute limit, or a non-finite converted result—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item. Prefer sending a JSON number; numeric strings that match a strict finite pattern are accepted, but unit suffixes such as three-thousand-six-hundred-s or thousand separators are not. Pair the twelve-decimal fields with your own display rounding if you only need whole minutes for a customer invoice; the API keeps twelve decimals so tests stay byte-stable across runtimes.
Practical checks, related searches, and when not to use this
Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit seconds or pass text.
Integration use cases
Timeouts, heartbeats, and SLA clocks
Map API timeouts, retry backoffs, and incident durations counted in seconds to minutes, hours, and days when an SLA or status page is written in larger units.