Convert a date to Roman numeral format for tattoos and engravings
Turn a calendar date into a clean Roman numeral date without wondering whether the day and month were swapped or whether an impossible date slipped through.
Run — free
Enter the date in the unambiguous YYYY-MM-DD form, choose day-month-year or month-day-year output, and receive a copyable result with each component converted separately. The converter checks Gregorian month lengths and leap years before producing anything, making it useful when a date will be committed to metal, stone, print, jewelry, or skin.
Enter an exact date before choosing its display order
Start with the calendar date in YYYY-MM-DD form. This input convention is deliberately different from the displayed result: it prevents a value such as 04-07-2026 from being interpreted as either April seventh or July fourth. After entering the year, month, and day, choose day-month-year when you want the day first, or month-day-year when you want the month first. The converter does not guess based on your location. It validates the actual Gregorian date, including the number of days in each month and the full leap-year rule. February 29 is accepted in a leap year such as 2024, but rejected in a common year such as 2025. A year must fall from 0001 through 3999 because conventional Roman notation has no universally accepted plain-text form for zero, negative years, or very large values. This strict input step is especially valuable when the finished text will be difficult or expensive to change.
Read the Roman numeral result component by component
The day, month, and year are converted independently and then joined with hyphens. For example, day-month-year means the first Roman group is the day, the second is the month, and the final group is the year. Month-day-year reverses only the first two groups. The result uses standard subtractive Roman numeral forms: four is IV rather than IIII, nine is IX, forty is XL, ninety is XC, four hundred is CD, and nine hundred is CM. Keeping the components separate matters because a date is not treated as one large number. It also makes the output easier to proofread against the original calendar date. Before using the text in a permanent design, compare each group in order and confirm that the selected layout matches the convention your audience expects. The returned object includes the source date and selected order alongside the copyable Roman date so that this review does not depend on memory.
Prepare the result for an engraving, tattoo, or keepsake
Once the conversion is correct, copy the Roman date into your design draft and decide how it should be separated visually. The capability returns hyphens because they remain clear in plain text, but a designer may replace them with centered dots, spaces, slashes, line breaks, or decorative marks without changing the numerals themselves. Preserve the three component boundaries and do not casually remove letters: Roman notation is positional within each group, so a small edit can change the number. Ask the engraver, jeweler, printer, or tattoo artist to review the final artwork at its actual size, since narrow spacing can make pairs such as IV and VI harder to distinguish. Keep the original YYYY-MM-DD date beside the draft during approval, and verify the selected order one final time. This tool supplies a deterministic notation conversion, not artistic or historical certification; specialized inscriptions may follow house styles that use additive forms or other conventions. API use costs $0.002 per request, while the browser version can be used directly on the page.
What you can do with it
Plan a commemorative tattoo
Convert a birth, wedding, or memorial date into a clear Roman numeral draft before reviewing placement and typography with an artist.
Prepare jewelry or engraving copy
Generate a compact date for a ring, watch, plaque, pendant, or keepsake while retaining the original date and chosen order for proofreading.
Standardize dates in a design workflow
Use the deterministic API output to format approved calendar dates consistently across invitations, prints, packaging, or personalized products.
FAQ
What date format should I enter?
Enter the source date as YYYY-MM-DD, such as 2026-07-25. Choose the separate order option to control whether the result begins with the day or month.
Does the converter reject impossible dates?
Yes. It checks month lengths and Gregorian leap-year rules, so dates such as April 31 or February 29 in a non-leap year return an input error.
Which Roman numeral style is used?
It uses conventional subtractive notation, including IV, IX, XL, XC, CD, and CM. It does not produce additive clock-face variants such as IIII.
Why are years limited to 3999?
Plain conventional Roman numerals represent 1 through 3999 consistently. Larger values require overlines or other extensions that are not reliably expressed or interpreted in ordinary text.
Can I replace the hyphens with dots or spaces?
Yes. The hyphens mark the three date components. You may change only the separators during design, provided the Roman numeral groups and their order remain unchanged.
What does an API conversion cost?
Each API request costs $0.002. The same deterministic converter is also available free in the browser on this page.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/misc2/roman-numeral-date-convert \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"date":"2026-07-25"}'const res = await fetch("https://api.kit.forhosting.com/misc2/roman-numeral-date-convert", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"date": "2026-07-25"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/misc2/roman-numeral-date-convert",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"date": "2026-07-25"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/misc2/roman-numeral-date-convert", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"date":"2026-07-25"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"date":"2026-07-25"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/misc2/roman-numeral-date-convert", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"date": "2026-07-25"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "misc2.roman_numeral_date_convert",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |