Time Unit Converter
Convert time between seconds, milliseconds, microseconds, nanoseconds, picoseconds, and femtoseconds for digital and RF applications.
SI prefixes · 1 s = 10³ ms = 10⁶ µs = 10⁹ ns … 10¹⁵ fsAPI slug time-units
Linked values
Type in any field — the others follow.
Reference values
Select a row to load it| Femtoseconds | Picoseconds | Nanoseconds | Microseconds | Milliseconds | Time |
|---|---|---|---|---|---|
| fs | 0.001ps | 1.000e−6ns | 1.000e−9µs | 1.000e−12ms | 1.000e−15s |
| fs | 1.000ps | 0.001ns | 1.000e−6µs | 1.000e−9ms | 1.000e−12s |
| fs | 1000.000ps | 1.000ns | 0.001µs | 1.000e−6ms | 1.000e−9s |
| fs | 10000.000ps | 10.000ns | 0.010µs | 1.000e−5ms | 1.000e−8s |
| fs | 100000.000ps | 100.000ns | 0.100µs | 1.000e−4ms | 1.000e−7s |
| fs | 1.000e6ps | 1000.000ns | 1.000µs | 0.001ms | 1.000e−6s |
| fs | 1.000e9ps | 1.000e6ns | 1000.000µs | 1.000ms | 0.001s |
| fs | 1.000e12ps | 1.000e9ns | 1.000e6µs | 1000.000ms | 1.000s |
Formula
| Symbol | Quantity | Your value |
|---|
Assumptions
4 items
- 01The input is in seconds and every other unit is a decimal SI multiple of it: 1 s = 10³ ms = 10⁶ µs = 10⁹ ns = 10¹² ps = 10¹⁵ fs, exactly.
- 02Minutes, hours and other non-decimal units are not included.
- 03A duration is converted as given; no frequency (1/t) or electrical length is derived from it.
- 04Time is entered from 0 s upward with no upper limit; the field refuses a negative value.
Worked example
Oscillator jitter for an ADC clock
A clock oscillator datasheet gives 0.35 ps RMS phase jitter. The ADC datasheet draws its SNR-versus-jitter curves in femtoseconds, and the timing budget is kept in nanoseconds.
| Step | Expression | Result |
|---|---|---|
| Seconds | 0.35 ps ÷ 10¹² | 3.5×10⁻¹³ s |
| Femtoseconds | 3.5×10⁻¹³ s × 10¹⁵ | 350 fs |
| Nanoseconds | 3.5×10⁻¹³ s × 10⁹ | 0.00035 ns |
How it works
This calculator converts between seconds, milliseconds, microseconds, nanoseconds, picoseconds, and femtoseconds for electronics engineers, embedded developers, and RF designers working with timing-critical systems. Per SI Brochure (BIPM), the second is defined by cesium-133 hyperfine transition: exactly 9,192,631,770 periods. Electronics timing spans 18 orders of magnitude: femtoseconds (10^-15 s) for optical pulses, picoseconds for high-speed serial (PCIe 5.0 UI = 31.25 ps), nanoseconds for DRAM timing (tCL = 14-22 ns), microseconds for ADC conversion (SAR ADC: 1-10 us), and milliseconds for human interface (response time < 100 ms per ISO 9241). Signal propagation on PCB is 6.67 ps/mm in FR-4, making timing margins critical at GHz frequencies.
Practical tips
- PCB propagation delay per IPC-2141: microstrip on FR-4 = 6.0-6.8 ps/mm (varies with trace geometry), stripline = 7.0 ps/mm. Use actual stackup parameters for timing closure
- Oscilloscope selection: 10 ns/div for GHz signals, 100 ns/div for 100 MHz, 1 us/div for MCU timing, 1 ms/div for audio/PWM. Bandwidth should be > 5x signal frequency for < 3% amplitude error
- JEDEC memory timing: DDR4-3200 has tCK = 625 ps (clock period), tRCD = 13.75 ns (row-to-column delay), tRP = 13.75 ns (precharge). Convert all to same unit before timing analysis
Common mistakes
- Confusing ns (10^-9 s) with us (10^-6 s) - they differ by 1000x. A 10 ns propagation delay is 1000x faster than 10 us. DDR timing is ns, ADC conversion is us
- Ignoring propagation delay in high-speed PCB design - signals travel ~6 ps/mm on FR-4. A 100 mm trace adds 600 ps delay, exceeding timing margin for signals > 500 MHz
- Using floating-point for firmware timing without considering precision - at 100 MHz (10 ns period), float32 only provides 24-bit mantissa = 6 us resolution, inadequate for ns-level timing
Frequently asked questions
4 questions
What is propagation delay?
Propagation delay (tpd) is time for signal to travel from input to output. Per semiconductor datasheets: CMOS gate tpd = 0.1-10 ns depending on technology node (14 nm CMOS: ~10 ps, discrete 74HC: ~10 ns). PCB trace: ~170 ps/inch in FR-4 (6.7 ps/mm). Coax cable: 1.0-1.5 ns/foot depending on velocity factor.
What timing resolution do microcontrollers provide?
Timer resolution = 1/f_clock. At 48 MHz: 20.83 ns/tick. At 200 MHz: 5 ns/tick. Hardware capture provides single-cycle resolution. Software polling adds 3-10 cycles overhead = 60-200 ns at 48 MHz. For sub-ns timing, use dedicated timer ICs (TDC) with 10-100 ps resolution per datasheet specs.
Why are picoseconds important in RF design?
At 5 GHz: period = 200 ps, so 10 ps jitter = 5% of cycle = significant phase noise. Per IEEE 802.11ax: EVM requires < 2% = 4 ps timing precision. PCB trace mismatch of 1 mm = 6.7 ps skew. DDR5 at 4800 MT/s has 104 ps UI - trace matching must be within ~20 ps (3 mm) for reliable operation.
What is jitter and why does it matter?
Jitter is timing variation from ideal position, specified as RMS (1-sigma) or peak-to-peak per JEDEC JESD65C. Sources: PLL (1-10 ps RMS), clock buffer (0.5-2 ps), power supply (1-5 ps per mV ripple). Impact: ADC SNR degrades as SNR_jitter = -20×log10(2×pi×f_in×t_jitter). At 100 MHz input with 1 ps jitter: SNR_jitter = 64 dB limit.