Encoders & Utilities

Unit Converter

Convert between common units (bytes, time, length).

Input Full form lands with the tool

Tool implementation in progress The form, validation, and result view for this tool are part of an upcoming release. The catalog entry is live today so the page can be indexed and bookmarked.

About this tool

Unit Converter handles the everyday conversions a developer or sysadmin runs into: data sizes (B, KB, MB, GB, TB, KiB, MiB, GiB, TiB), data-transfer rates (bps, Kbps, Mbps, Gbps and their byte-per-second cousins), time (seconds to days to years), length (mm to km, in to mi), temperature (°C ↔ °F ↔ K), and angles (degrees ↔ radians ↔ gradians). All conversions happen client-side at full IEEE-754 precision.

Each category has its own panel with a source value, a source unit, and a target unit — change any of them and the converted value updates instantly. For data and bandwidth, both decimal (SI: kB = 1000 B) and binary (IEC: KiB = 1024 B) are supported side-by-side, with a clear label on which is which. Time units include both standard (second = 1) and "everyday" (working day = 8 hours) interpretations.

When to use this tool

Reading docs that mix units. AWS quotes EBS throughput in MiB/s, Azure in MB/s, and Cloudflare in Mbps — convert once to compare.
Provisioning storage. A 500 GiB volume on a budget marked in TB — quick check it fits.
Reading legacy timestamps. Convert "3,600,000 milliseconds" to "1 hour" without thinking.
Quick scientific calculations. Temperature for a sous-vide recipe, RPM-to-rad/s for a hobby motor — small everyday conversions that do not need a full CAD calculator.

About binary vs decimal sizes

The IEC standardised "KiB" (1024 B) in 1999 to clear up the long-standing ambiguity of "KB". Most operating systems and many docs still use "KB" to mean 1024 B; ISPs, hard-drive vendors, and SI-conformant docs use it to mean 1000 B. The difference is small for kilobytes (2.4%) and large for terabytes (10%). When in doubt, our tool shows both — the row labelled "GiB" is binary, the row labelled "GB" is decimal.

Frequently asked questions

Why does my "1 TB" drive show as 931 GB?

Because manufacturers use decimal (1 TB = 1,000,000,000,000 bytes) but Windows and most tools display binary (1 GiB = 1,073,741,824 bytes — but labelled as "GB"). 10^12 / 2^30 ≈ 931. So a 1 TB drive really has the bytes you paid for; it just shows up as 931 in a display that secretly counts in binary while calling it decimal. The drive is not "missing" 7%.

Is the temperature conversion exact?

Yes for the formulas: °F = °C × 9/5 + 32, K = °C + 273.15. We compute in double precision and round on display, so converting back and forth gives the original value within 0.0001°. Note that Kelvin starts at absolute zero so cannot be negative; if you enter -300°C the result is "below absolute zero" rather than a negative Kelvin number.

Why are there two seconds-to-day rows?

Because "day" is ambiguous in context. The astronomical day is 86,400 seconds. A business day (working-time calculations) is 8 hours = 28,800 seconds. We show both because asking "how many work days is this?" gives a different answer than "how many calendar days?". The labels make it explicit.

Can I convert currency or other live-rate units?

No — only physically-fixed units. Currency rates change minute-by-minute and require an upstream feed; we do not run that infrastructure here. The conversions in this tool (kilometres to miles, bytes to bits, etc.) are constants defined by physical or industry standards, so they work offline and never need refreshing.