Time unit converter
90 seconds are 1.5 minutes, 0.025 hours or 90,000 milliseconds. Convert a duration between seconds, minutes, hours, days, weeks, milliseconds and microseconds, see it in all seven units at once, with a day fixed at 86,400 seconds. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Duration magnitude to convert
- 90
- Input time unit
- s
- Output time unit
- min
- Result
- 1.5
- Seconds
- 90
- Minutes
- 1.5
- Hours
- 0.025
Duration conversion between everyday time scales is a daily chore in media pipelines, SLA dashboards, homework, sports timing, and backend timeout configs. People search for a time unit converter when they need seconds next to minutes, hours next to days, or milliseconds next to microseconds, not a general multi-unit toolbox that also handles length and temperature, and not a calendar date or time-zone tool. This capability accepts one finite amount plus from and to unit labels among seconds, minutes, hours, days, weeks, milliseconds, and microseconds, bridges every conversion through the second so results stay consistent, and returns the target value together with the same duration expressed in all seven units. Unrecognized unit names are rejected with a clear validation error instead of silently guessing a nearby symbol.
How the time unit converter maps durations through seconds
Start from the second as the SI base unit of time and express every other supported unit as an exact fixed factor into seconds. One minute is exactly sixty seconds and one hour is exactly three thousand six hundred seconds, so the familiar clock ratios stay algebraic rather than approximate. One civil day is defined here as eighty-six thousand four hundred seconds, the conventional mean solar day used for everyday duration arithmetic, and one week is seven of those days, or six hundred four thousand eight hundred seconds.
One millisecond is one thousandth of a second and one microsecond is one millionth of a second, so sub-second steps are pure powers of ten. This calculator never mixes those paths ad hoc. It multiplies the input amount by the factor of the source unit to reach seconds, then divides by the factor of the target unit to produce the result.
Because every path shares the same intermediate second, converting ninety seconds to minutes and then back, or comparing two hours to milliseconds and weeks, stays numerically consistent within ordinary floating-point precision. The tool does not convert months or years, which have variable calendar length, does not apply leap seconds, does not convert nanoseconds or business days, does not shift wall-clock timestamps across time zones, and does not call Date or the system clock.
It answers only the algebraic duration unit conversion people mean when they type time unit converter into a search bar and expect seconds, minutes, hours, days, weeks, milliseconds, and microseconds.
What you enter and what you get back
Send three fields: amount, a finite number for the duration magnitude; from, a string naming the input unit; and to, a string naming the output unit. Both unit fields accept short keys and everyday words in any common casing, including second or seconds or sec or s, minute or minutes or min, hour or hours or hr or h, day or days or d, week or weeks or wk or w, millisecond or milliseconds or ms, and microsecond or microseconds or us or µs.
When a unit string is unknown the error message includes Unrecognized unit and lists the seven supported families so clients can fix the label rather than guessing. Classic checks include ninety seconds becoming one point five minutes, one hour becoming three thousand six hundred seconds, one day becoming twenty-four hours, one week becoming seven days, one second becoming one thousand milliseconds, and one millisecond becoming one thousand microseconds.
Where dedicated time unit conversion shows up in real work
Secondary-school science and math courses constantly assign problems that give a duration on one scale and ask for another, often mixing stopwatch seconds with hours and days in the same worksheet. Backend and DevOps teams normalize timeout and SLA fields between milliseconds in code and seconds or minutes in dashboards before comparing service budgets. Media and broadcasting pipelines step between frame-level milliseconds and human-readable minutes and hours when planning runtimes and ad slots.
Fitness and sports apps display lap times in minutes and seconds while storage stays in milliseconds, so a single conversion pass keeps storage uniform while the UI localizes. If you later need calendar date differences, time-zone shifts, Unix epoch conversion, or general multi-category unit conversion, treat those as separate search intents and landings rather than overloading this time unit converter page.
What you can do with it
Timeout and SLA field normalization
Convert service timeouts and SLO budgets among ms, s, and min so code configs and ops dashboards use one ground truth.
Media runtime and schedule planning
Turn episode or ad durations from seconds into minutes and hours for run sheets without spreadsheet drift.
Homework and lab answer keys
Convert textbook durations among seconds, minutes, hours, days, and weeks with one deterministic key for grading.
FAQ
Which time units does this converter support?
Seconds (s), minutes (min), hours (h), days (d), weeks (w), milliseconds (ms), and microseconds (us).
What happens if I send an unrecognized unit?
The error message includes Unrecognized unit and lists the supported families so you can correct the label.
How long is a day or a week here?
One day is exactly 86400 seconds and one week is exactly seven days (604800 seconds). That matches civil duration arithmetic, not leap-second calendars or variable months.
Does it convert months, years, or time zones?
No. Months and years have variable length, and wall-clock or time-zone conversion is a different intent. Use dedicated date and timezone tools for those problems.
What does it cost?
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/time \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"amount":90,"from":"s","to":"min"}'const res = await fetch("https://api.kit.forhosting.com/conv/time", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"amount": 90,
"from": "s",
"to": "min"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/time",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"amount": 90,
"from": "s",
"to": "min"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/time", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"amount":90,"from":"s","to":"min"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"amount":90,"from":"s","to":"min"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/time", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"amount": 90,
"from": "s",
"to": "min"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.time",
"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.
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
What you send and what you get back from the API and browser form
Missing fields, non-numeric amount strings, NaN, Infinity, and unrecognized unit labels fail with invalid_input and are not charged. On success the response echoes the cleaned amount, normalized from and to keys, the primary result in the target unit, the same duration as seconds, minutes, hours, days, weeks, milliseconds, and microseconds with twelve significant digits of stable precision, the second factors used, the formula string, and method second_bridge. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where dedicated time unit conversion shows up in real work
Data pipelines that ingest mixed IoT or log payloads with ms, s, and h tags can call this capability once per reading instead of reimplementing the factors in every service. Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.