Microseconds to Human Readable
Paste any number of microseconds and instantly see the human-readable duration — from days down to individual microseconds — plus every common unit conversion.
Where microseconds show up
A microsecond is one millionth of a second — far too small to perceive, but meaningful for computers. When you run a database query, the database engine measures how long each step took in microseconds because that precision reveals whether a step took 50 µs or 5,000 µs — a 100× difference that a millisecond-level timer would round away.
In practice, values like 142,983 µs appear in PostgreSQL EXPLAIN ANALYZE output, Linux perf stat traces, and network packet capture files. A number that looks large — 3,600,000,000 µs — is just one hour. Paste it here and the conversion is instant. If your trace reports finer-grained nanosecond values instead, that page does the same conversion one level down.
Frequently asked questions
What is a microsecond?
A microsecond (µs) is one millionth of a second — 1,000 times smaller than a millisecond. The symbol µ is the Greek letter mu. If you cannot type µ, us is the common ASCII substitute used in code and configuration files.
Where do microsecond values appear?
Database query planners (PostgreSQL EXPLAIN ANALYZE, MySQL slow query log), Linux perf and strace output, network packet capture timestamps (pcap uses microsecond precision), Redis latency histograms, and many C/C++ profiling tools all report durations in microseconds.
How many microseconds are in a second?
1,000,000 microseconds. The chain is: 1 second = 1,000 milliseconds = 1,000,000 microseconds = 1,000,000,000 nanoseconds.
How do I convert microseconds to milliseconds in code?
Divide by 1,000. In Python: ms = us / 1000. In Go: time.Duration(us) * time.Microsecond gives a Duration you can print or compare. In C++: std::chrono::duration_cast<std::chrono::milliseconds>(dur) converts automatically.
What is the difference between microseconds and nanoseconds?
A nanosecond is 1,000 times smaller than a microsecond. Nanoseconds appear in CPU benchmarks and kernel traces where instruction-level timing matters; microseconds are more common in I/O latency and database measurements.