DUR

Duration Converter

Convert durations across time units

Units, Time & Number

🔒 100% client-side — your data never leaves this page

Maintained by ToolsKit Editorial Team•Updated: May 19, 2026•Reviewed: May 19, 2026

Editorial Policy/Privacy/Report issue

English version/Chinese version

Page mode

Input

Quick CTA

Enter seconds or a duration string first to convert between numeric and human-readable formats immediately; examples stay in Deep.

ValueUnit

Output

Converted duration values will appear here

🔒 100% client-side • duration conversion only

Next step workflow

Convert timestamps next Compare date spans Shift times across timezones

Page reading mode

Deep expands pitfalls, recipes, snippets, FAQ, and related tools when you need troubleshooting or deeper follow-through.

About this tool

Convert durations from numeric values or human strings like 1d 2h 30m into multiple units at once: milliseconds, seconds, minutes, hours, days, and weeks. The tool also outputs a compact human representation and ISO 8601 duration format for API contracts and scheduling payloads. It is useful in backend timeout tuning, analytics interval normalization, and automation window planning. Everything runs client-side.

Direct Answers

Q01

Why convert durations into several units?

Because humans and systems often describe the same interval in different units and formats.

Q02

Should human duration strings be treated loosely?

Only if the parser clearly understands them; ambiguous strings are a common source of mistakes.

Compare & Decision

Milliseconds vs human duration text

Milliseconds

Use it for systems, APIs, and machine-readable config.

Human duration text

Use it for docs, UI labels, and human review.

Note: Machines prefer raw units, while humans prefer structured time phrases.

Human duration text vs raw milliseconds

Human duration text

Use it in docs and handoff notes for readability.

Raw milliseconds

Use it in config files and APIs that require deterministic machine units.

Note: Keep both forms side-by-side when teams collaborate across roles.

Human-readable duration vs machine-unit duration

Human-readable

Use for docs, product copy, and stakeholder communication.

Machine units (ms/s)

Use for configuration, APIs, and deterministic program behavior.

Note: Use machine units for source-of-truth and render human text at the edges.

Approximate conversion vs contract-grade conversion rules

Quick output

Use for one-off internal checks with low blast radius.

Validated workflow

Use for production pipelines, audits, or customer-facing output.

Note: Duration converter should be treated as a workflow step, not an isolated click.

Single-pass processing vs staged verification

Single pass

Use when turnaround time is more important than traceability.

Stage + verify

Use when reproducibility and post-incident replay are required.

Note: A staged path usually prevents silent data-quality regressions.

Failure Input Library

Milliseconds interpreted as seconds in API payload

Bad input: {"timeout": 30000} interpreted as 30,000 seconds by downstream service.

Failure: Jobs stall for hours instead of timing out in 30 seconds.

Fix: Annotate units explicitly and enforce schema validation for duration fields.

Rounding policy inconsistency across services

Bad input: One service rounds 1.5m to 90s while another truncates to 60s.

Failure: Retry and cache behaviors diverge unexpectedly.

Fix: Standardize rounding rules and convert once at system boundaries.

Implicit rounding changes breach calculation

Bad input: Different dashboards round fractional hours in opposite directions.

Failure: Teams dispute whether incidents breached target windows.

Fix: Define one rounding convention and apply it in all converters/reports.

Input contract is not normalized before processing

Bad input: Month-to-day assumptions differ across teams.

Failure: Output looks valid but downstream systems reject or misread it.

Fix: Normalize input format and add a preflight validation step before export.

Compatibility assumptions are left implicit

Bad input: DST boundary is ignored for timezone-sensitive windows.

Failure: Different environments produce inconsistent results from the same source data.

Fix: Document compatibility mode and verify with at least one independent consumer.

Scenario Recipes

Normalize a time interval for docs or code

Goal: Translate between milliseconds and human-readable duration strings.

Enter a numeric duration or a human string.
Review the equivalent values across units.
Copy the representation that fits your docs, config, or code.

Result: You can stop doing repeated time math in your head or in scratch pads.

Convert SLO windows into machine-ready timeout values

Goal: Translate human-readable durations into seconds or milliseconds for API and job configs.

Collect target windows such as retry delay, timeout, and retention duration.
Convert values into the exact unit required by each system.
Document both human and machine forms in runbooks to avoid unit drift.

Result: Configuration becomes clearer and less error-prone across product, ops, and engineering teams.

SLA policy normalization across teams

Goal: Align mixed unit inputs into comparable duration standards.

Convert all SLA targets to canonical minutes and hours first.
Separate working-time SLAs from calendar-time SLAs explicitly.
Document rounding rules for dashboard and alert threshold consistency.

Result: SLA reporting stays comparable across products and regions.

Duration converter preflight for SLA breach window calculation alignment

Goal: Reduce avoidable rework by validating assumptions before publishing output.

Run a representative sample through the tool and capture output shape.
Cross-check edge cases that commonly break downstream parsing.
Publish only after sample and edge-case results are both stable.

Result: Teams can ship faster with fewer back-and-forth fixes.

Duration converter incident replay for billing cycle duration reconciliation

Goal: Turn production anomalies into repeatable diagnostic steps.

Reproduce the problematic input set in an isolated test window.
Compare expected and actual output with explicit acceptance criteria.
Record a stable remediation checklist for future on-call use.

Result: Recovery time decreases because operators follow a tested path.

Quick Decision Matrix

Programmatic config and interoperability contracts

Recommend: Keep canonical machine units with explicit field naming.

Avoid: Avoid free-text duration strings as contract primitives.

User-facing dashboards and SLA explanations

Recommend: Render human-readable durations derived from canonical units.

Avoid: Avoid exposing raw millisecond numbers without contextual formatting.

Need consistent duration math for SLAs and runbooks

Recommend: Normalize units early and publish shared rounding conventions.

Avoid: Avoid mixing unit conversion and business-time assumptions silently.

Internal one-off debugging or ad-hoc data checks

Recommend: Use quick mode with lightweight validation.

Avoid: Avoid treating ad-hoc output as production truth.

Production release, compliance evidence, or external delivery

Recommend: Use staged workflow with explicit verification records.

Avoid: Avoid single-pass output without replayable validation logs.

Failure Clinic (Common Pitfalls)

Using ambiguous shorthand

Cause: A loose string can be interpreted differently across tools or people.

Fix: Prefer explicit unit labels and validate the parsed result.

Mixing seconds and milliseconds in adjacent services

Cause: Different SDKs expect different units, and silent mismatch often causes premature timeout or huge delays.

Fix: Annotate every duration field with explicit units and validate with one end-to-end smoke test.

Production Snippets

Human duration sample

txt

1d 2h 30m 15s

Use It In Practice

Duration Converter is most reliable with real inputs and scenario-driven decisions, especially around "Programmatic config and interoperability contracts".

Use Cases

When Programmatic config and interoperability contracts, prioritize Keep canonical machine units with explicit field naming..
When User-facing dashboards and SLA explanations, prioritize Render human-readable durations derived from canonical units..
Compare Milliseconds vs Human duration text for Milliseconds vs human duration text before implementation.

Quick Steps

Enter a numeric duration or a human string.
Review the equivalent values across units.
Copy the representation that fits your docs, config, or code.

Avoid Common Mistakes

Common failure: Jobs stall for hours instead of timing out in 30 seconds.
Common failure: Retry and cache behaviors diverge unexpectedly.

Frequently Asked Questions

Can I parse strings like 1d 2h 30m?

Yes. Human mode supports combined tokens such as w, d, h, m, s, and ms.

Does this output ISO 8601 duration?

Yes. ISO 8601 output is included for API and data interchange workflows.

Can I convert weeks to milliseconds?

Yes. All supported units are cross-converted from a single normalized base.

Does it support negative durations?

This version is focused on non-negative durations for operational safety.

Why use compact output?

Compact output is easier to read in logs, configs, and CLI summaries.

Is parsing server-side?

No. Parsing and conversion are fully local in your browser.