Converter

Duration Converter

Convert engineering durations across milliseconds, seconds, minutes, hours, days, weeks, months, and years.

Input durationChoose a source unit
Milliseconds90000
Seconds90
Minutes1.5
Hours0.025
Days0.001
Weeks0.0001
Months0
Years0
Human-readable secondsQuick reference
1 hour3,600 seconds
1 day86,400 seconds
1 week604,800 seconds
1 month2,592,000 seconds (30 days)
1 year31,536,000 seconds (365 days)

Use this tool when

These are the practical situations where this workflow usually earns its keep.

You need to normalize one duration across engineering-friendly units.

You want a browser-local pass before writing the correct unit back into config, docs, or a review note.

You need a smaller, cleaner review surface during TTL planning, scheduler review, and config explanation.

Daily workflow acceleration

Duration Converter helps when teams need to normalize one duration across engineering-friendly units without opening a heavier system or rebuilding the same transformation manually every time.

Review and handoff clarity

A focused output is useful when the next step is writing the correct unit back into config, docs, or a review note and the current raw input would otherwise slow down the reviewer or teammate.

Lower-friction local handling

For TTL planning, scheduler review, and config explanation, keeping the task in the browser is helpful because the source material often does not need to leave the user’s machine just to answer this one question.

Common mistakes to avoid

These are the checks that usually keep the output useful instead of misleading.

A converted duration is only useful if the consuming system expects the same base unit you plan to use.

Assuming every epoch is in seconds when many systems emit milliseconds or finer precision.

Reading a localized display and forgetting which time zone the underlying value actually represents.

Learn how to use this tool

Convert durations across milliseconds, seconds, minutes, hours, days, weeks, months, and years. This guide focuses on how teams use it for TTL planning, scheduler review, and config explanation when the real job is to normalize one duration across engineering-friendly units.

Read the guide

Tell us what is missing

If this flow helped only partly, leave feedback so we can understand the missing step or edge case.

Leave feedback

Request the next tool

Use the wishlist to suggest the next utility, workflow, or improvement that would complete this job to be done.

Open wishlist

Related tools

These tools often appear right before or right after this workflow.