Skip to content
Time helper

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.

Guide: How 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.

Samples: Sample input & output

Convert seconds to minutes

Input

7,200 seconds

Output

120 minutes (2 hours)

FAQ: Frequently asked questions

  • Do you support milliseconds and smaller units?

    Yes. Conversions include seconds, milliseconds, microseconds, and nanoseconds.
  • How accurate are the conversions?

    Calculations rely on JavaScript number precision; extremely large values may be rounded.
  • Can I copy individual results?

    Use the copy control next to each line to grab the unit you need.

Use cases: Common use cases

  • Converting durations

    Switch between seconds, minutes, hours, and days to reason about rate limits or TTLs.

  • Interpreting logs

    Turn millisecond or nanosecond values into readable units to grasp latency and timing.

  • Double-checking inputs

    Verify numeric inputs correspond to the intended duration before saving configurations.

Notes: Notes & limitations

  • Work stays in your browser

    Inputs and outputs remain local. Closing the tab or clearing cache will remove any temporary state.

  • Validate critical data

    Results are helper outputs—double-check them before sending to production systems or sharing externally.

  • Large payloads depend on your device

    Very large text or files can feel slow in some browsers. Use a desktop environment for heavy workloads.

Converted values

Updated automatically

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 30000ms to 30 seconds or 5 minutes to 300000ms.
  • 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

Recent Articles

Use Case
2026-08-07

curl Options Cheat Sheet: What -X, -H and -d Actually Do

A reference for the curl options you meet in real API work: why -d already implies POST, how -d differs from --data-raw, the @ prefix that silently reads a file, single vs double quotes, and why -k and -L deserve more caution than they usually get.

Introduction
2026-08-06

Converting Between JSON Schema and Zod: How required Maps to .optional()

Inside a two-way converter that turns JSON Schema into a Zod schema and Zod code back into JSON Schema. Covers the inverted defaults between required and .optional(), the constraint mapping table, and how the Zod side is parsed without executing any code.

Use Case
2026-08-06

SQL Clause Order Reference: Why WHERE Can't See Your SELECT Alias

The order you write SQL clauses is not the order the database runs them. A reference for the logical execution order (FROM → WHERE → GROUP BY → HAVING → SELECT → ORDER BY → LIMIT), why aliases fail in WHERE, when to use WHERE vs HAVING, and the MySQL/PostgreSQL differences that bite.

Use Case
2026-08-06

Unified Diff Format Reference: Reading @@ Hunks in git diff Output

How to read the unified diff format git produces: what the four numbers in @@ -12,7 +12,9 @@ mean, why a one-character edit shows as a whole-line replacement, the whitespace and line-ending traps, \ No newline at end of file, combined @@@ diffs on merges, and rename detection via similarity index.

Use Case
2026-08-06

UTC to JST Reference: The 9-Hour Offset, Cheat Sheet & Timezone Pitfalls

Convert between UTC and JST (Japan Standard Time) with a cheat sheet. Covers what Z and +09:00 mean in ISO 8601, when JavaScript date parsing silently shifts by 9 hours, MySQL/PostgreSQL timezone behavior, and why GitHub Actions cron always runs in UTC.

Use Case
2026-08-04

CREATE TABLE Reference: MySQL vs PostgreSQL vs SQLite Types & Constraints

A cross-database CREATE TABLE (DDL) reference with cheat sheets for data types, auto-increment keys (AUTO_INCREMENT / IDENTITY / rowid), foreign key ON DELETE behavior, and the CHECK constraint that MySQL silently ignores.

Ad

Ad