Time Unit Converter
Convert time values across multiple units by entering a single number.
You can instantly convert between milliseconds, seconds, minutes, hours, days, and weeks, with all results updating automatically.
This tool is useful for estimating durations, checking time calculations, and converting values found in logs, configuration files, or documentation.
By selecting the source unit, all other units are recalculated in real time, allowing quick comparison without manual math.
All calculations are performed directly in your browser.
No input values are sent to any server, making this converter fast, simple, and safe for everyday development and reference use.
Can't read that. Write it like 1h30m, 90m, 01:30:00 or PT1H30M
Converted values
Updated automaticallyNotation:
Uptime (SLA) and allowed downtime
Allowed downtime for an uptime percentage. Month = 30 days, year = 365 days.
Enter a number from 0 to 100.
Find the uptime from downtime
Error budget and burn rate
From an SLO and the current error rate, get how fast the error budget is being used and when it runs out, plus the multi-window alert thresholds from the Google SRE Workbook.
Multi-window alerts
Alert only when both the long and the short window are above the burn rate. This avoids pages for short blips and still catches fast burns.
| Long window | Short window | Burn rate | Budget used | Error rate | Action |
|---|
GuideHow to use & features
- Select the source unit and enter a value to update all other units automatically.
- Extremely large or small numbers are shown in scientific notation for readability.
- Copy any converted value directly into your notes or scripts.
SamplesSample input & output
Convert seconds to minutes
7,200 seconds
120 minutes (2 hours)
FAQFAQ
Which units can it convert?
Six units: milliseconds, seconds, minutes, hours, days and weeks. Enter a value in one unit and the other five are converted at the same time.How many milliseconds are in a day or a week?
One day is 86,400,000 ms (24 × 60 × 60 × 1000) and one week is 604,800,000 ms. Useful when a timeout or expiry must be given in milliseconds.How do I avoid mixing up milliseconds and seconds?
Units differ by system: `setTimeout` uses milliseconds, while a Redis TTL or a JWT `exp` uses seconds. Enter the duration you want and compare both values to avoid a digit slip.Can I enter decimals?
Yes, for questions like "how many minutes is 1.5 hours". Results are rounded to six decimal places.Is my input sent anywhere?
No. All conversion happens in your browser.
Use casesCommon use cases
Converting timeout and TTL settings
Move between human-friendly units (minutes, days) and the unit a config expects (seconds, milliseconds) for API timeouts, cache expiry and session lifetimes.Making elapsed times in logs readable
Turn a log value like "took 187,400 ms" into seconds or minutes to judge quickly whether it is slow or acceptable.Estimating job intervals and retention
Convert periods such as "keep logs for 90 days" or "run every 15 minutes" into other units for batch design and capacity estimates.Checking hand calculations
See every unit side by side when you want to confirm a manual conversion.
NotesNotes & limitations
Months and years are not supported
Their length is not constant, so they are out of scope. If you need a rough figure such as "30 days ≈ one month", calculate it in days.A day is always 24 hours
Daylight saving time and leap seconds are not considered. This converts lengths of time; it does not compute the difference between two dates.Fractions are rounded to six decimals
Very large or very small values can show floating-point error. Do not use it for precise billing or money calculations.It does not convert dates and UNIX time
For converting dates such as 2023-11-14 to and from UNIX time, use the UNIX Time Converter tool. This tool only handles durations.
AboutAbout this tool
Time Unit Converter
Timeouts, cache TTLs, retry delays, monitoring intervals, animation durations, and job schedules often use different units. This converter helps translate milliseconds, seconds, minutes, hours, and days so settings are easier to review before they reach production.
Common use cases
- Check timeouts: Convert
30000msto30 secondsor5 minutesto300000ms. - Review cache TTLs: Translate Redis, CDN, API, or browser cache values into readable durations.
- Verify polling intervals: Confirm retry delays, cron-related intervals, and monitoring windows.
Unit mistakes are common
Some libraries expect milliseconds while others expect seconds. Before pasting a value into configuration, check the documentation and convert the number into the exact unit the system expects.
Articles for this tool
How to Convert Milliseconds, Seconds, Minutes, and Hours for Timeouts and TTLs
Convert time units for API timeouts, cache TTLs, retry delays, polling intervals, and monitoring settings without mixing up milliseconds and seconds.
UTC to JST Reference: The 9-Hour Offset, Cheat Sheet & Timezone Pitfalls
Add 9 hours to UTC to get JST (UTC 00:00 = JST 09:00). A cheat sheet, what Z and +09:00 mean in ISO 8601, and why GitHub Actions cron always runs in UTC.
