Tools mentioned in this article
Open the browser-based tool while you read and try the workflow immediately.
Time settings fail quietly when the unit is wrong
Configuration values such as 30000, 60, or 3600 are ambiguous unless you know the expected unit. A timeout might be milliseconds, a cache TTL might be seconds, and a monitoring interval might be minutes.


The Time Unit Converter converts milliseconds, seconds, minutes, hours, and days so you can review settings before they become bugs.
Example: Making config values reviewable
Say an API client config contains these values:
const apiClient = {
timeout: 30000,
retryDelay: 1500,
cacheTtl: 86400,
};
The raw numbers are hard to judge, but aligning the units makes them reviewable.
| Setting | Raw value | Reads as |
|---|---|---|
timeout |
30000ms |
30 seconds |
retryDelay |
1500ms |
1.5 seconds |
cacheTtl |
86400s |
24 hours |
Converted like this, the team can discuss whether the API timeout is reasonable, whether the retry delay is too short, and whether the cache should live until the next day.
Common conversions
30000ms is 30 seconds. 5 minutes is 300 seconds or 300000 milliseconds. 3600 seconds is one hour. Writing these values in human-readable form during review makes configuration mistakes easier to spot.
Combine duration and clock time
When you need to know when a timestamp expires, combine duration conversion with the Unix Timestamp Converter or UTC and JST Time Zone Converter. This helps translate TTLs and token expiration values into real calendar times.
Common mix-ups
Units are not consistent. Some Node.js APIs and the browser’s setTimeout use milliseconds, Redis EX uses seconds, and a monitoring service’s settings screen may use minutes. A bare 60 could be 60 milliseconds, 60 seconds or 60 minutes, so putting the unit in a comment or setting name makes it much easier to read later.
API_TIMEOUT_MS=30000
CACHE_TTL_SECONDS=3600
JOB_INTERVAL_MINUTES=5
Put the unit in the environment variable name and review the value after converting it to real time with the tool. Even someone who only sees the config file will understand the intent.
Quick conversion reference
Here are the conversions that come up most often when reviewing settings. Use it as a check when mental arithmetic leaves you unsure.
| Time | Seconds | Milliseconds |
|---|---|---|
| 1 second | 1 | 1,000 |
| 1 minute | 60 | 60,000 |
| 5 minutes | 300 | 300,000 |
| 1 hour | 3,600 | 3,600,000 |
| 1 day | 86,400 | 86,400,000 |
If you see 86400 and recognize “one day” at once, you can judge on the spot whether a cache TTL is longer than intended. 300 (5 minutes) and 3600 (1 hour) also appear often in monitoring intervals and token lifetimes.
The tool’s conversion range and how results are shown
The units are milliseconds, seconds, minutes, hours, days and weeks. Months and years aren’t included because their length isn’t fixed. Enter one value and unit, and the values in every unit appear at once.
| Input | Result shown (excerpt) |
|---|---|
| 90 minutes | 5400000 ms / 5400 s / 1.5 h / 0.0625 days / 0.008929 weeks |
| 1.5 hours | 90 min / 5400 s / 0.0625 days |
| 0.1 seconds | 100 ms / 0.001667 min / 2.777778e-5 h |
Decimals are rounded to six places, so values that don’t divide evenly are shown short. A very small value (below 0.0001) or one of a billion or more is shown in exponent form such as 2.777778e-5. When you see an exponent, that unit is “orders of magnitude off”. Reading the value in a unit of a similar magnitude helps you avoid misreading a setting.
You can also enter a duration as text. It reads unit-based forms such as 1h30m, 1d 2h and 250ms, a clock form like 01:30:00 (hours:minutes:seconds), and ISO 8601 such as PT1H30M, converts it to milliseconds and then to every unit. Below the results you get a readable notation and the ISO 8601 notation, such as 1h 30m / PT1H30M. A bare number with no unit (90) is not read because it could be minutes or seconds, and years and months (P1Y, P1M) are not read because their length isn’t fixed.
Summary
Milliseconds and seconds are easy to confuse. Convert values before pasting them into configuration, and always check the unit expected by the library, API, or cloud service.
Frequently Asked Questions
Is a value like 30000 milliseconds or seconds?
It depends on the context. Some Node.js APIs and the browser’s setTimeout use milliseconds, so 30000 is 30 seconds—while Redis’s EX is in seconds. The same “timeout” differs by library or service, so check the unit in the docs and convert it to a human-readable unit with the Time Unit Converter.
How can I prevent mixing up units?
Include the unit in the setting or environment-variable name. API_TIMEOUT_MS, CACHE_TTL_SECONDS, and JOB_INTERVAL_MINUTES convey intent even to someone who only sees the value. A value like 60 is especially risky since it could be 60 ms, 60 s, or 60 min.
I want to know when a TTL actually expires.
To turn a TTL in seconds into a real date/time, combine it with the Unix Timestamp Converter or the UTC and JST Converter to see the concrete expiration time.
Is there a trick for remembering common second counts?
Memorizing the frequent values speeds up judgment. 300 is 5 minutes, 3600 is 1 hour, 86400 is 1 day and 604800 is 1 week. They appear often in monitoring intervals, token lifetimes and cache TTLs, so using them as a baseline and thinking in multiples makes it easy to get a rough idea.
