µm vs um: Is “um” the Same as the Micrometre Symbol?

A micrometre is one millionth of a metre, and its symbol is built from the micro prefix plus m for metre. On screen, however, you may meet three spellings: µm, μm, and the ASCII fallback um.

They may point to the same intended scale, yet they are not the same text. A unit parser sees three distinct strings, so the difference becomes practical whenever a value is searched, exchanged, validated, or parsed by software.

The three spellings you will encounter

Building the micrometre symbol

The SI prefix micro means 10⁻⁶, and BIPM presents its symbol as a mu-shaped µ. Like other measurement notation, the prefix is read as part of the unit expression: it attaches directly to the unit symbol rather than standing as a separate token.

The unit is a single token: write 25 µm, not 25 µ m. Micro stays attached to m, just as it stays attached to the unit symbol in microsecond or microfarad.

Why “micron” still appears

You may still encounter the older word micron in technical conversation and historical material. The 13th CGPM removed “micron” as a unit name in 1967; the mu-shaped symbol had become the SI prefix micro instead. In current SI terminology, the unit is the micrometre, formed from the prefix micro and the metre.

This history helps explain why older datasets can mix vocabulary and character conventions. A field labelled “microns” may still contain values written as µm, μm, or even um, so software should separate the unit meaning from the exact source spelling.

Why µm and μm both exist in data

Two Unicode code points can supply the mu-shaped prefix seen in real data: U+00B5 MICRO SIGN and U+03BC GREEK SMALL LETTER MU. The former came through older character sets; the latter is the Greek letter itself. Many fonts make the pair visually indistinguishable.

Unicode treats the relationship as compatibility rather than canonical equivalence. Compatibility normalization can map U+00B5 to U+03BC, while ordinary canonical normalization does not. The underlying distinction is covered in more detail in Micro Sign µ vs Greek Mu μ.

Is one mu encoding more correct?

There is no basis for calling one of these code points the uniquely “SI-correct” Unicode encoding. SI defines the prefix micro and its symbol, while Unicode defines U+00B5 MICRO SIGN and U+03BC GREEK SMALL LETTER MU. Unicode notes that both occur as micro signs, with U+03BC preferred in a Unicode context.

For newly designed Unicode-aware software, accepting both forms on input is usually more robust than insisting that every source use one code point. If you normalize internally, choose a documented policy and preserve the original text separately when exact source fidelity matters.

um is an ASCII approximation

A human reader will often understand 25 um immediately, especially in a field already labelled micrometres. The text itself, however, contains only ordinary Latin letters; there is no mu-shaped micro symbol to distinguish the prefix from any other use of u.

That matters to software. The letter u can be part of a variable, model number, username, or ordinary word. A strict unit parser has no universal rule saying that every u before m means micro. An application that accepts um should do so as an explicit alias, not by blindly replacing letters.

A blanket search-and-replace from um to μm is unsafe because the letters can occur in ordinary text. Restrict the conversion to fields that are already known to contain units, then validate the whole token rather than guessing from two adjacent letters.

The reverse conversion is lossy too. Replacing every mu-shaped prefix with u may make an ASCII export portable, but the export no longer carries the actual micro symbol. If round-tripping matters, record that fallback convention explicitly.

The final m is lowercase for a reason

The metre symbol at the end of micrometre is lowercase m. Turning it into uppercase M does not “capitalize the unit”; M is already reserved for the mega prefix, 10⁶.

Generic case conversion is risky in scientific text. The related m vs M guide shows how metre, milli, and mega depend on case and position.

What to use in practice

In a Unicode workflow, prefer a mu-shaped prefix to plain u, then follow the project’s chosen policy for U+00B5 versus U+03BC. Importers should recognize both characters rather than rejecting a measurement solely because it came from a different software stack.

What matters is the kind of representation you have: the intended symbol, an equivalent-looking Unicode encoding that can be handled deliberately, or an ASCII approximation whose meaning depends on context.