Unit, data format, and text converters

Two different kinds of conversion live here. One is measurement — units, currency, height, timezones, data sizes — where you want a number in different terms. The other is data format, where the same information has to be re-expressed as JSON, CSV, XML, YAML, or Markdown so another program will accept it. Both are instant and neither needs an account.

Which one do you need?

The tools above overlap in places. This is the quickest way to pick the right one.

You need length, weight, temperature, area, or speed
Unit ConverterOne page for the everyday measurement conversions instead of a separate tool each.
You need a rate between world currencies
Currency ConverterUses live reference rates rather than a stale built-in table.
You are scheduling across regions
Timezone ConverterHandles the daylight-saving offsets that make manual arithmetic wrong twice a year.
You want API data in a spreadsheet
JSON to CSVFlattens the structure into rows and columns Excel and Sheets will open.
You are feeding spreadsheet data into code
CSV to JSONThe reverse trip, with your header row becoming the object keys.
You are moving between config formats
YAML to JSONSame data, different syntax — useful when a tool accepts only one of them.
You have a Unix timestamp in a log or database
Timestamp ConverterTurns 1735689600 into a date you can read, and back again.
You need binary, hex, octal, decimal, or text
Binary ConverterAll five at once, exact at any size, with the arithmetic shown.

Frequently asked questions

Are the currency rates live?

They come from a live reference feed rather than a fixed table, so they track the market closely. They are indicative mid-market rates — a bank or card issuer will apply its own spread, so what you actually pay will differ slightly.

What is the difference between JSON, CSV, XML, and YAML?

They are four ways of writing down the same kind of structured data. CSV is a flat table and is what spreadsheets read. JSON is the default for web APIs and handles nesting. XML is older, more verbose, and still common in enterprise systems. YAML is designed to be comfortable for humans to edit and is used mostly for configuration files.

Will converting nested JSON to CSV lose information?

It can. CSV has no way to express nesting, so deeply structured objects and arrays have to be flattened or dropped. Flat, uniform records convert cleanly; complex nested documents do not fully survive the trip.

Does converting happen on your servers?

The format converters run in your browser, so your data stays on your device. Currency and translation lookups have to call an external rate or language service, since the values are not something a browser can know on its own.

Other categories