Skip to content
Allin

ISO 8601 Date Formatter

Turn any date, time and UTC offset into ISO 8601, RFC 3339, week/ordinal date, RFC 2822, HTTP date and Unix timestamps.

Open ISO 8601 Date Formatter and you get an answer straight away, with no account to create. Its place is under JSON, XML & formats; SQL Formatter and XML Formatter / Validator answer the questions closest to this one.

How to use it

  1. Open the tool — no signup or install needed.
  2. Enter your input or adjust the available options.
  3. Get your result instantly, then copy or download it.

Frequently asked questions

What does ISO 8601 Date Formatter do?

Turn any date, time and UTC offset into ISO 8601, RFC 3339, week/ordinal date, RFC 2822, HTTP date and Unix timestamps.

When would I actually use this?

Making a machine-generated blob readable, finding the character where a parse fails, and shrinking a file before it ships.

What is the most common mistake?

Assuming valid means correct. A document can parse cleanly and still have the wrong shape for whatever will read it — validation checks the syntax, not the schema.

Is there a tool for the next step?

XML Formatter / Validator is the closest one after this: Pretty-print, minify and check whether XML is well-formed, all in your browser.

What else is worth having open alongside it?

YAML Formatter / Validator and Paper Size Reference (A4, Letter, ISO 216) — they come up in the same task often enough to be worth a second tab.

Where do the figures come from?

Parsing and serialisation follow each format's specification. Key order and whitespace are not semantically meaningful in JSON or YAML, so a reformatted document is equivalent even when the bytes differ.

Further reading

All guides
ExplainerWriting a Date as ISO 8601, and Why It Is the Only Unambiguous Format01/02/2026 is 1 February in most of Europe and 2 January in the United States, and nothing in the string says which. ISO 8601 fixes that, sorts as text, and stops being ISO 8601 in four specific places that RFC 3339 rejects.ExplainerReading and Writing Military Time0800 is not “eight o'clock” and not “08:00” — it is “zero eight hundred”, with a zone letter on the end. The four digits, the spoken form, midnight at 0000, the argument about 2400, and the reason 12-hour notation cannot settle noon.ExplainerXML to JSON: Attributes, Repetition, and the Single-Element Array TrapTwo documents that differ only in how many children exist produce two different JSON shapes, and no converter can tell them apart without a schema. Plus what this one really does with attributes, mixed content and whitespace — and the one thing it still cannot record.ExplainerYAML Looks Friendly and BitesYAML is JSON plus a type-inference layer, and the inference is the dangerous part. The same file run through a YAML 1.2 parser and a YAML 1.1 parser: no is a string in one and false in the other, 01234 is 1234 in one and 668 in the other, and 12:30:00 is a number in one of them.GuideWhat a Minifier Can Remove, and What It Must NotMinification has to preserve meaning, and the interesting part is the whitespace that carries meaning: the descendant combinator, the spaces inside calc(), the gap between two inline elements. Measured here on real files, including how much brotli was going to save you anyway.GuideBeautify or Minify: What Each Is For, and What It Does to the WeightFour real stylesheets run through the minifier, measured raw and after gzip. Stripping every space saved 48, 103, 104 and 147 compressed bytes; stripping comments saved 57, 1 358, 2 420 and 1 042. Plus the five inputs this minifier breaks.