Date mode just got a small but genuinely useful upgrade: a dedicated dropdown for choosing between the international Day.Month.Year order and a US-style Month.Day.Year order — no more re-entering values in the wrong fields to fake the reorder. Here's exactly what changed and how to use it.
What changed in Date mode
Quick answerThe Roman Numeral Converter's Date mode now includes a Date order dropdown, sitting right above the separator-style picker. It has two options: Day.Month.Year (the existing default, e.g. 19.VII.MMXXVI) and Month.Day.Year — US style (e.g. VII.19.MMXXVI). You enter the day, month, and year exactly as before; the dropdown only controls the order they're combined in.
Up to now, Date mode built a single fixed sequence — day, then month, then year — matching the international convention used across most of the world. That was fine for the majority of users, but it left US-style daters with one workaround: manually swap which number went into the day field and which went into the month field, then double-check the output actually matched the date they meant. It worked, but it was easy to get backwards, especially with the day and month fields sitting right next to each other in the form.
The new dropdown replaces that manual swap. Selecting Month.Day.Year (US style) reorders the numerals automatically — the day field still means "day" and the month field still means "month," the tool just changes which one is printed first.
How to use the new Date order dropdown
Quick answerOpen the Date tab, enter the day, month, and year as usual, then look for the Date order select box just above the separator-style picker. Leave it on Day.Month.Year for the international default, or switch it to Month.Day.Year for the US-style reading — the hint text under the dropdown even spells out a live example as you change the selection.
Take July 19, 2026 as an example — a date already used as one of the tool's own presets. With the day field set to 19, the month field set to 7, and the year field set to 2026:
Same date, two Date-order dropdown settings
| Dropdown setting | Result | Reads as |
|---|
| Day.Month.Year (default) | 19.VII.MMXXVI | 19th day, 7th month, 2026 — international order |
| Month.Day.Year (US style) | VII.XIX.MMXXVI | 7th month, 19th day, 2026 — "July 19, 2026" |
Nothing else about Date mode changes when you flip the dropdown. The five separator styles — dot, slash, dash, space, and stacked vertical — still apply on top of whichever order you picked, so a US-style date can still be previewed as VII·XIX·MMXXVI, VII/XIX/MMXXVI, or stacked across three lines, exactly like the Day.Month.Year default already could.
Why this matters more than it sounds
Quick answerRoman numerals carry no built-in unit labels, so a date string's meaning depends entirely on an order convention the reader has to already know. A dedicated Month.Day.Year option means US-style users can now produce and verify the exact numeral order they'd naturally expect, directly in the tool, instead of translating it in their head or risking a manual field-swap mistake.
This is exactly the kind of thing that matters most when a numeral date is about to become permanent — engraved on a ring, tattooed on a forearm, or carved into a cornerstone. A day-first numeral read by someone expecting month-first can land on the wrong calendar date entirely, and because both values are usually small numbers (1 through 12 for the month, 1 through 31 for the day), the mistake often isn't obvious just by looking at the result.
Having the order set explicitly by a labeled dropdown — rather than inferred from which field a number happened to be typed into — removes a step where a US-style user could previously get the reorder backwards. It's a small interface change, but it closes a real, easy-to-hit gap for anyone who thinks in month-first dates.
Try the new Date order dropdown yourself
Enter a date once, then flip between Day.Month.Year and Month.Day.Year (US style) instantly — plus five separator styles to preview side by side. Free, in your browser.
Try the free Roman Numeral Converter →
Frequently asked questions
What's new in the Roman Numeral Converter's Date mode?
Date mode now has a "Date order" dropdown with two options: Day.Month.Year (the existing international default, e.g. 19.VII.MMXXVI) and Month.Day.Year (US style, e.g. VII.19.MMXXVI). Both options sit above the separator-style picker, so the order and the punctuation style are chosen independently.
Do I still have to swap the day and month fields myself for US order?
No. Previously getting a US-style Month.Day.Year numeral meant manually entering the month value into the day field and the day value into the month field. Now the Date order dropdown does the reordering automatically — enter the day, month, and year normally, then pick Month.Day.Year from the dropdown to see the numerals in that order.
Does switching to Month.Day.Year change which separator styles are available?
No. The separator-style picker (dot, slash, dash, space, or stacked) is independent of the date-order setting. Choosing Month.Day.Year just reorders which numeral comes first; you can still preview that reordered date in any of the five separator styles.
How would July 19, 2026 look with the new Month.Day.Year option?
With Day.Month.Year (the default), July 19, 2026 reads 19.VII.MMXXVI (day, month, year). Switching the dropdown to Month.Day.Year reorders the same three numerals to VII.XIX.MMXXVI — month 7, day 19, year 2026 — matching how a US reader would say "July 19th, 2026."
Why add a Month.Day.Year option instead of just always using Day.Month.Year?
Because Roman numerals give no built-in signal for which numeral is the day and which is the month, a reader's assumed order changes how a date is understood. US readers commonly expect month-first dates, so a dedicated toggle lets US-style users produce and verify the exact numeral order they expect, instead of mentally reordering the international default or swapping input fields by hand.
Related guides
A note on this guide: The July 19, 2026 example above is illustrative only, matching a date already used as a preset in the tool — it is not a record of any real event. This article is for general reference; verify any date conversion yourself before using it for something permanent like a tattoo or engraving.