Convert Unix timestamps to readable dates and move data between CSV and JSON, with proper RFC 4180 quoting and nested-object flattening.
4 tools in this category.
Convert between timestamps and dates in every common representation — and see how the input was interpreted.
Convert Unix epoch values at any precision, with hex output and a year-2038 overflow check.
Convert CSV, TSV or any delimited text to JSON with correct handling of quotes, commas and embedded newlines.
Convert JSON to spreadsheet-ready CSV, flattening nested objects into dot-notation columns.
Four converters covering the two translations that come up constantly: epoch time to something a human can read, and data between CSV and JSON. The Timestamp Converter and Unix Time Converter handle both directions, including the seconds-versus-milliseconds ambiguity that produces dates in 1970 when a millisecond value is read as seconds, and dates in the year 55000 when the reverse happens.
CSV is deceptively hard, and most conversion bugs come from underestimating it. A field containing a comma must be quoted; a quote inside a quoted field must be doubled; a field may legally contain a newline, which means you cannot split a CSV file on line breaks and expect rows. These converters follow RFC 4180 on both sides, so a description field with commas and quotation marks in it survives the round trip instead of silently shifting every subsequent column.
Going from JSON to CSV forces a structural decision, because JSON nests and CSV does not. Nested objects are flattened into dotted column names, so `{"user":{"name":"Ada"}}` becomes a `user.name` column. Arrays of differing length across rows are the case with no clean answer — CSV has no way to express them — so if your data is genuinely irregular, a format that preserves structure is a better destination than a spreadsheet.