I got Roman numerals wrong on a client's website and did not notice for three months. The footer copyright line was generated from the current year, and my "clever" bit of code that spelled the year in Roman numerals produced MMXXIIII for 2024. Four I's in a row. It looked plausible enough that neither I nor the client caught it, until a sharp-eyed visitor emailed to point out that 2024 is MMXXIV, and that four I's in a row has not been standard notation for a very long time. The lesson stuck: Roman numerals have real rules, they are easy to get subtly wrong, and "looks about right" is not good enough.
TL;DR: The Roman Numeral Converter turns numbers into Roman numerals and decodes Roman numerals back into numbers, over the standard 1 to 3999 range. It always produces the canonical spelling, strictly validates numerals you type (rejecting forms like
IIIIand suggesting the correct one), and shows a symbol-by-symbol breakdown. It runs entirely in your browser - no account, no upload.
I built this tool for toolz.dev after that footer incident, because I wanted a converter that enforced the actual rules instead of just gluing symbols together. Unicode encodes the numerals as their own characters in the Number Forms block, which is worth knowing before you paste one into a database column. Encoding is only half the job; the harder and more useful half is telling you when a numeral you typed is malformed and what it should have been. This guide covers how Roman numerals work, the subtractive rule that catches everyone, and how to use the converter to encode, decode, and understand any numeral in the standard range.
What is a Roman numeral converter?
A Roman numeral converter translates between the Arabic numbers we use every day - 1, 2, 3 - and the letter-based numerals of ancient Rome, built from seven symbols: I, V, X, L, C, D, and M. It works both ways. Give it 2024 and it returns MMXXIV; give it MCMLXXXIV and it returns 1984. The tool on toolz.dev does this from a single box, detecting whether you typed a number or a numeral and converting accordingly, with a manual mode switch when you want to force a direction.
The seven symbols carry fixed values: I is 1, V is 5, X is 10, L is 50, C is 100, D is 500, and M is 1000. Numerals are built mostly by addition - you write symbols from largest to smallest and sum them, so XVII is 10 + 5 + 1 + 1 = 17. The complication, and the source of nearly every mistake, is subtractive notation, where a smaller symbol placed before a larger one is subtracted rather than added. IV is 4, not 6. CM is 900. That single rule is what separates a valid numeral from a plausible-looking wrong one.
Here are the seven symbols and the six subtractive pairs the standard allows, which together are the entire vocabulary the converter uses:
| Type | Symbols | Values |
|---|---|---|
| Base symbols | I, V, X, L, C, D, M | 1, 5, 10, 50, 100, 500, 1000 |
| Subtractive pairs | IV, IX, XL, XC, CD, CM | 4, 9, 40, 90, 400, 900 |
Why the subtractive rule catches everyone
The reason MMXXIIII looked fine to me is that additive Roman numerals are intuitive - pile up symbols, add them up. The subtractive rule breaks that intuition. Standard modern notation never repeats a symbol more than three times, so 4 is IV (five minus one), not IIII, and 40 is XL (fifty minus ten), not XXXX. Only six subtractive pairs are permitted, and only specific pairings: you can put I before V or X, X before L or C, and C before D or M - but not I before C, or X before M. IC for 99 is wrong; the correct form is XCIX.
This is precisely where a validating converter earns its place. When you type a numeral to decode, the tool does not just accumulate a number and hand it back. It parses the numeral, computes the value, then re-encodes that value into the canonical form and compares. A numeral is accepted only if it is exactly the standard spelling of its own value. So IIII, VV, IC, and XM are all caught and rejected, with a message suggesting the correct numeral - IV, X, XCIX, and so on. That round-trip check is the only reliable way to validate a Roman numeral, because there is no simple character-level rule that catches every malformed case, and it is what would have flagged my footer bug the instant the code ran.
How to use the Roman Numeral Converter
Step 1: Enter a number or a numeral
Type an Arabic number such as 2024 to encode it, or paste a numeral such as MMXXIV to decode it. In the default Auto mode, the tool looks at your input - all digits means "encode this number," and a string of Roman letters means "decode this numeral" - and picks the direction for you. If it ever guesses wrong, the mode buttons let you force "Number to Roman" or "Roman to Number."
Step 2: Read the instant result
The conversion appears as you type. Encoding gives you the canonical numeral. Decoding gives you the number, and also shows the normalized spelling of what you entered, so you can confirm your input was a valid standard numeral and not just something that happened to add up.
Step 3: Check the symbol breakdown
Below the result, the numeral is split into its additive parts. MCMXCIV shows as M + CM + XC + IV, each with its value. This makes the subtractive pairs visible and is the fastest way to understand why a numeral means what it means - you can see the 900 and the 90 and the 4 as distinct chunks rather than a wall of letters.
Step 4: Use a quick value or copy
Tap a quick-fill button for a common value like 4, 9, 40, or the current year to see the rules in action immediately, or copy your result to the clipboard with one click for pasting into a document, a design, or a copyright line.
The limits: no zero, no numbers above 3999
Two limits fall straight out of how the Roman system was built, and the converter enforces both with plain explanations rather than silent failure.
There is no Roman numeral for zero. The system was a tally notation for counting quantities, and it developed with no concept of zero as a number - you simply wrote nothing. The idea of zero as a value and a placeholder arrived later, through Indian and Arabic mathematics, and never made it back into Roman numerals. For the same reason there are no negative numbers and no fractions in standard use. So the converter starts at 1 and rejects 0, negatives, and decimals with a message explaining why.
The upper limit is 3999, written MMMCMXCIX. Because a symbol is not repeated more than three times, you cannot write 4000 as MMMM; you would need a symbol for 5000, and plain-ASCII Roman numerals do not have one. Historically, larger numbers used a vinculum - an overline drawn above a symbol to multiply its value by 1000, so an overlined V meant 5000. That notation has no reliable plain-text form, which is why standard converters, including this one, cap at 3999. Within that range every value has exactly one correct spelling, and the tool always produces it.
How to read a Roman numeral by hand
The converter does this for you, but understanding the underlying method makes the results click and helps you sanity-check anything you read out in the world. There is one rule, and it handles every valid numeral. Read the symbols left to right, and at each step compare the current symbol's value with the value of the symbol immediately after it. If the current symbol is greater than or equal to the next, add its value. If the current symbol is smaller than the next, subtract it.
Walk through MCMXCIV. M is 1000, and the next symbol C is smaller, so add 1000, running total 1000. C is 100 but the next symbol M is larger, so subtract 100, total 900. M is 1000 and the next symbol X is smaller, so add 1000, total 1900. X is 10 but the next C is larger, so subtract 10, total 1890. C is 100 and the next I is smaller, so add 100, total 1990. I is 1 but the next V is larger, so subtract 1, total 1989. V is 5 and there is nothing after it, so add 5, total 1994. That single compare-with-the-next rule produces 1994, and it works for every subtractive pair without any special cases.
Encoding by hand runs the other direction: subtract the largest value you can from your number, write its symbol, and repeat. For 1994 you take 1000 (M), then 900 (CM), then 90 (XC), then 4 (IV), landing on MCMXCIV. Always taking the largest available chunk is what guarantees the canonical form, and it is exactly the greedy method the converter uses internally. Doing it by hand a few times is the fastest way to internalize why the tool rejects a numeral like IC - that shortcut never appears when you build the numeral the correct way.
Common use cases
Years and dates. The most common real use. Film and TV copyright lines, book publication dates, building cornerstones, and monument inscriptions all spell the year in Roman numerals. Convert 2024 to MMXXIV for a footer, or decode the MCMLXXVII on an old title card to find it means 1977. For a full date, convert each part separately and join them with a separator, since there is no Roman notation for a whole date.
Design and typography. Roman numerals appear on clock and watch faces, in outline numbering (chapters, appendices, acts and scenes), and as decorative numerals in logos and print. Getting the canonical form right matters when it is going to be set in type and seen by everyone.
Education and puzzles. Teaching or learning the system, checking homework, or solving a puzzle that encodes a number as a numeral all benefit from a converter that shows the breakdown and enforces the rules, so the "why" is visible, not just the answer.
Verifying inherited numerals. When you encounter a numeral in the wild - on a plaque, in a document, in someone else's code - you often just want to know what it means and whether it is even valid. Paste it in; if it is malformed, the tool tells you and suggests the correct spelling.
Sports and events. Super Bowls, Olympiads, and monarchs' regnal numbers use Roman numerals. Decoding "Super Bowl LVIII" to 58 or encoding an event's edition number is a quick, exact job.
Roman numerals among the other number systems
Roman numerals are one of several ways to write a number in something other than everyday decimal, and the converter sits alongside the other numeric tools on toolz.dev. Where the number base converter moves a value between base 2, 8, 10, and 16 - the bases that matter for computing - the Roman converter moves between decimal and a non-positional, symbol-based system from antiquity. They are different kinds of "other notation": base conversion is positional and mathematical, Roman is additive and historical. If you are exploring how a number looks across systems, the binary translator shows text and numbers as raw bits, and the unit converter handles the everyday quantity conversions that Roman numerals were originally invented to tally. Each is a different answer to the same question: how else can I write this value?
Privacy: it all runs in your browser
There is nothing to upload here, and nothing is uploaded. Encoding, decoding, validation, and the breakdown all happen in client-side code in your browser, which is why the result updates on every keystroke instead of after a network round trip. You can confirm the tool is self-contained by disconnecting from the internet - it keeps working. Nothing you type is transmitted, logged, or stored. This is the same client-side principle behind every tool on toolz.dev, which I make the full case for in the data privacy in online tools article, and which underpins the broader coding tools guide approach to a private, browser-based toolkit.
FAQ
How do you write 2024 in Roman numerals?
2024 is MMXXIV: two M for 2000, two X for 20, and IV for 4. The IV uses subtractive notation, where placing I before V means five minus one. Enter 2024 into the converter and the breakdown shows it as M + M + X + X + IV, so each part is clear.
What are the seven Roman numeral symbols and their values?
There are seven symbols: I is 1, V is 5, X is 10, L is 50, C is 100, D is 500, and M is 1000. Every Roman numeral is built by combining these, generally writing larger values before smaller ones and adding them, with six specific subtractive pairs as the exception.
How does subtractive notation work in Roman numerals?
When a smaller symbol appears immediately before a larger one, its value is subtracted rather than added. Standard usage allows only six such pairs: IV (4), IX (9), XL (40), XC (90), CD (400), and CM (900). This is why 4 is written IV instead of IIII, and 90 is XC instead of LXXXX.
Why is there no Roman numeral for zero?
The Roman system is a tally-based notation for counting quantities, and it developed without a concept of zero as a number - you simply wrote nothing. Zero as a value and placeholder came later through Indian and Arabic mathematics and never entered Roman numerals. Because of this, the numerals start at 1, and the converter rejects 0 and negative values.
What is the largest number in standard Roman numerals?
Using only the standard letters, the largest value is 3999, written MMMCMXCIX. Since a symbol is not repeated more than three times, you cannot exceed 3999 with M alone. Larger numbers historically used an overline (a vinculum) to multiply a symbol by 1000, but that has no plain-text form, so this converter caps at 3999.
Is IIII ever a correct way to write 4?
Not in standard notation, where 4 is IV. However, IIII appears on many clock and watch faces as a stylistic choice, partly for visual balance opposite the VIII across the dial. This converter follows the standard rule, treats IIII as invalid, and suggests IV instead.
How do I write a date in Roman numerals?
Convert each part of the date separately and join them with a separator, because there is no Roman notation for a whole date. For 15 March 1992 you convert 15 to XV, 3 to III, and 1992 to MCMXCII, then write it as XV·III·MCMXCII or in your preferred field order. Periods, middle dots, and slashes are all common separators - pick one and stay consistent, since the numerals alone give no clue which field is which.
How does the tool know if I entered a number or a numeral?
In Auto mode it inspects the input: a value made only of digits is treated as an Arabic number and encoded, while a value made only of the letters I, V, X, L, C, D, and M is treated as a numeral and decoded. If it guesses wrong, the mode switch lets you force either direction.
