When the number is right but the format is wrong
Most conversion mistakes are not maths mistakes. They come from mixing up seconds and milliseconds, assuming a color format a design tool does not use, or forgetting that temperature has an offset. These three converters take care of the translation and let you copy the result straight into your work.
The three converters
- Unit Converter covers length (metres, kilometres, centimetres, millimetres, miles, yards, feet, inches), weight (kilograms, grams, milligrams, metric tons, pounds, ounces) and temperature (Celsius, Fahrenheit, Kelvin). Type in any field and the others update as you go. It uses exact international definitions, such as 0.0254 metres per inch.
- Color Converter accepts HEX, RGB, RGBA, HSL, HSLA and OKLCH, detects the format you paste and shows all six outputs. A built-in picker and an 11-step palette generator (Tailwind scale, shades, tints and tones) help you explore variations.
- Unix Time Converter turns timestamps into dates and dates back into timestamps, in any time zone, with ISO 8601 or local formatting. It reads seconds and milliseconds automatically and shows the current Unix time live.
Mistakes worth avoiding
Seconds versus milliseconds. A 10-digit timestamp is in seconds and a 13-digit one is in milliseconds. JavaScript's Date.now() returns milliseconds while many backends expect seconds, which is how dates end up in 1970 or thousands of years away.
Color spaces. OKLCH is designed so that equal changes in lightness look equally different to the eye, which HSL does not guarantee. That makes it a good fit for modern design tokens, while HEX and RGBA remain the safe choice for older tools.
Temperature. Celsius, Fahrenheit and Kelvin do not share a zero point, so a simple multiplication gives the wrong answer. Let the converter apply the offset.