time

Duration Converter

convert between nanoseconds, microseconds, milliseconds, seconds, and larger time units including months and years

Ready

Input Value

Input Unit

Decimal Places

About Duration Converter

Duration Converter maps tiny timing units through human-scale calendar units so performance traces and job schedules stay understandable.

Use cases

Translate profiler output from microseconds to milliseconds and seconds.
Convert task runtimes into minutes, hours, and days for SLO and batch planning.
Approximate long windows in month/year units when calendar precision is not required.
Normalize mixed unit timings before sharing incident reports.

Examples

Convert API latency from milliseconds into larger units.

Input

Input Value: 2500
Input Unit: ms

Output

s: 2.5
min: 0.041667
h: 0.000694

Convert long-running batch windows from hours to day/week units.

Input

Input Value: 36
Input Unit: h

Output

day: 1.5
week: 0.214286

Approximate release planning windows in month/year units.

Input

Input Value: 90
Input Unit: day

Output

month: 3
year: 0.246575

Duration Unit Reference

Format	How Many Seconds	What It Means	Scale Example
ns	0.000000001	Nanosecond	CPU-level operations and low-level timing
us	0.000001	Microsecond	Fast in-memory calls or syscall-level work
ms	0.001	Millisecond	Typical API/database latency targets
s	1	Second	A garden snail can move roughly around 1 cm in about one second
min	60	Minute	Cron jobs or polling intervals
h	3,600	Hour	Deploy windows and ETL batch slices
day	86,400	Day	Daily aggregates and retention policies
week	604,800	Week	Weekly reporting and maintenance cadences
month	2,592,000	Approximate month (30 days)	High-level planning windows
year	31,536,000	Approximate year (365 days)	Annual capacity or retention estimates

FAQ

When should I use ms vs us?

Use ms for user-facing latency and service SLO communication. Use us for hot-path profiling where millisecond precision hides important details.

Why include day and week in an engineering converter?

Operational planning often moves from low-level timings to maintenance windows and reporting cycles. Keeping both in one tool avoids manual math errors.

Are month and year conversions calendar-accurate?

No. This converter treats month as 30 days and year as 365 days for consistent engineering math. Use calendar-aware tooling when exact date boundaries matter.