Date Format Converter

The date format converter takes one calendar date and rewrites it in every layout you are likely to need: ISO 8601, American month-first, European day-first, dotted German style, long written forms, RFC 2822 for email headers, compact YYYYMMDD, ordinal day-of-year, and the ISO week date. Paste a date in almost any common form, or pick one from the calendar field, and the tool prints the whole set at once so you can copy the exact string a form, spreadsheet, or API expects.

Why one date has so many spellings

A calendar date is a single fact, but writing it down forces three separate choices: the order of the parts, the separator between them, and whether numbers or names carry the month. The United States writes month first, most of Europe and much of the world writes day first, and the international standard writes year first. Separators vary between slashes, hyphens, and periods. Month names may be spelled out, abbreviated to three letters, or replaced by a number. Multiply those choices together and the same day can appear in dozens of valid-looking strings, which is exactly how data gets misread when it moves between systems.

The ambiguity problem

Any numeric date where both the day and the month are twelve or lower can be read two ways. A string like 03/04 might mean March 4 or April 3, and nothing inside the string itself resolves the question. When you paste a date of that shape, this converter refuses to guess. It shows both readings side by side, labels which convention produces each one, and asks you to pick the intended date from the calendar field before printing the full format list. That extra step is deliberate: a silent wrong guess is far more expensive than one confirmation click.

Dates where the day exceeds twelve are unambiguous, so those convert straight through. A value such as 25/12 can only be day-first, because there is no twenty-fifth month.

What each output format is for

ISO 8601 (YYYY-MM-DD) is the format to store and exchange. It sorts correctly as plain text, never suffers from order ambiguity, and is what nearly every database, API, and configuration file expects. Reach for it as the default unless something specific demands otherwise.

The American and European numeric forms exist for human-facing documents, printed forms, and legacy systems that validate against a fixed pattern. The padded variants matter when a field requires a fixed width, such as older mainframe imports or fixed-column text files.

Long written forms remove all ambiguity for readers, which makes them the right choice for contracts, invitations, and anything a person will read once and act on. Spelling the month out costs a few characters and eliminates an entire class of misreading.

RFC 2822 is the date format used in email headers and HTTP responses. If you are debugging a mail server, writing a Last-Modified header, or building a feed, this is the string to copy. The dedicated RFC 2822 converter handles the full timestamp version with time and offset.

Compact YYYYMMDD shows up in filenames, batch identifiers, and log rotation schemes because it sorts chronologically and contains no separators to escape. Ordinal day-of-year appears in aviation, manufacturing lot codes, and scientific data sets; the day of year converter covers that format on its own, and Julian date codes handle the five-digit YYDDD variant.

The ISO week date names the year, the ISO week number, and the weekday as a single string. Payroll, manufacturing, and retail planning often run on week numbers rather than months. The week number tool explores that calendar in more detail.

What the parser accepts

You can paste year-first dates with hyphens, slashes, or dots; two-part numeric dates with a two- or four-digit year; a compact eight-digit string; and written forms with a full or abbreviated month name in either order. Two-digit years are expanded using the common windowing rule, where values below seventy are treated as this century and the rest as the previous one. That rule is a convention rather than a law, so spell out four-digit years whenever the source allows it.

Impossible dates are rejected rather than rolled forward. A February thirty-first will not silently become March third, because a converter that quietly invents a different day is worse than one that says no.

Practical habits that prevent format bugs

Store dates in ISO form and convert only at the edges, when displaying to a person or handing data to a system with its own requirement. Keep one canonical representation in your database and treat every other spelling as presentation. When importing a spreadsheet from an unfamiliar source, check a date where the day exceeds twelve before trusting the whole column; that single row reveals the file's convention immediately.

Label your columns and form fields with the expected pattern rather than assuming the reader shares your locale. A hint reading YYYY-MM-DD next to an input costs nothing and prevents support tickets. If a partner sends dates in a locale-specific numeric form, ask them to switch to ISO or to spelled-out months rather than building a guesser into your import pipeline.

Related conversions

If your source is a number rather than a written date, the converters hub collects the epoch and serial tools: Unix timestamps, Excel serial numbers, and Windows FILETIME values. For dates written in another calendar system entirely, see the Hebrew, Islamic, or Japanese era converters. To measure the distance between two dates rather than reformat one, use days between dates.

Time zones and this tool

This page converts a calendar date, not an instant. A date with no time attached has no time zone, which is why the same string is valid everywhere. As soon as you attach a clock time, the zone matters and the same instant can fall on different dates in different places. When that distinction is the point, work with the time zone converter or the ISO 8601 converter, both of which handle offsets explicitly rather than treating the date as a bare label.