Build Your Own Unit Converter: The One-Base-Unit Trick That Handles Anything
Every unit converter, from kilometres to game currencies to lab reagents, runs on the same tiny idea: define one reference unit as 1 and express everything else against it. Here's how the factor method works and how to define your own units for workflows no off-the-shelf tool covers.
Sooner or later you hit a conversion no website has a page for. A tabletop game where 3 gold equals a silver and 10 silver a copper. A workshop that measures stock in “sheets” that are really 1.2 metres. A lab protocol with a reagent dilution nobody standardised. A fantasy map with its own leagues. General converters can’t help, because these units only exist in your world. The good news is that every unit converter — including the ones that handle kilometres and pounds — runs on a single, almost embarrassingly simple idea. Once you see it, you can build a converter for anything in about thirty seconds. That idea is the “one base unit” trick, and it’s exactly what the custom unit converter is built around.
Pick one unit, call it 1
Here’s the whole method. Choose any unit in your system to be the reference — the base — and assign it the value 1. Then express every other unit as a single number: how many base units fit inside one of it. That’s the entire model. A metre is the base at 1; a foot is 0.3048 because 0.3048 metres fit in one foot; a yard is 0.9144; a furlong is 201.168. You never define the relationship between a foot and a yard directly. You only ever relate each unit back to the base, and the base does the rest.
In the tool you type these one per line, in the form name=value_in_base:
meter=1
foot=0.3048
inch=0.0254
yard=0.9144
furlong=201.168
That’s a complete, working length converter. The base doesn’t have to be a “real” unit either — it just has to be consistent. For a game currency you might set copper=1, silver=10, gold=30, and never think in decimals at all.
The conversion is one line of arithmetic
With everything defined against a common base, converting between any two units — even two you never directly related — takes one step. To convert a value, first turn it into base units, then turn base units into the target:
base value = value × from_factor
result = base value ÷ to_factor
Or, collapsed: value × (from_factor ÷ to_factor). Say you have 2 furlongs and want yards. Two furlongs is 2 × 201.168 = 402.336 metres of base, and dividing by the yard factor of 0.9144 gives 440 yards. You defined furlongs against metres and yards against metres, and the base silently bridged them. This is why you only ever need N definitions to convert between all N units, not N² individual pairings — the base is the hub every unit spokes out from.
Why this beats hunting for a dedicated tool
The reason the base-unit method is worth understanding rather than just using is that it dissolves a whole class of “is there a converter for X?” problems. There’s no such thing as a unit it can’t handle, because it doesn’t know or care what the units mean. Metres, gold pieces, reagent drops, “standard pallets,” rendering units in a game engine — they’re all just numbers relative to a base. The moment you can state “one of these equals this many of those,” you can define it, and the tool converts in both directions immediately. No off-the-shelf converter will ever cover your shop floor’s idiosyncratic stock units; a two-line definition does.
Three quick worlds you can define in seconds
To make the flexibility concrete, here are three unit systems that no mainstream converter covers, each a handful of lines. A tabletop economy: copper=1, silver=10, gold=30, platinum=300 — now “how many silver is 4 platinum?” is instant. A woodshop that buys in odd stock sizes: mm=1, sheet=1200, half-sheet=600, offcut=150, so a cut list in millimetres tells you how many sheets to order. A recipe scaled to an unusual vessel: set ml=1, scoop=15, ladle=90, pot=2400, and batch quantities stop needing mental gymnastics. In every case you never defined gold-to-silver or sheet-to-offcut directly — you related each to the base, and the tool derives every pairing for free.
Practical notes: precision, base choice and persistence
A few things make custom converters behave well in practice. Choose your base to minimise ugly decimals — if most of your conversions are whole-number multiples of the smallest unit, make the smallest unit the base and everything else becomes a clean integer. Keep precision in mind: the tool carries results to eight significant figures, which is plenty for physical measurements, but if you’re chaining conversions through a base with a tiny factor, define that factor carefully so rounding doesn’t creep in. And because these definitions only exist for you, the tool saves them locally in your browser — there’s no server, no account, and nothing is uploaded. Your unit set is there when you come back, and you can share it with a colleague simply by copying the textarea’s contents and pasting it into theirs.
A converter you’ll actually reuse
The trick to converting anything isn’t finding the right website; it’s realising that all conversion is the same operation dressed in different labels. Define one reference unit as 1, describe every other unit as a multiple of it, and a single division moves a value between any two of them. Whether you’re balancing a game economy, standardising workshop stock, or just tired of not having a page for your niche measurement, open the custom unit converter, type your units one per line, and you’ve built exactly the tool you needed — one no general converter was ever going to provide.
Try the tools from this guide
-
Custom Unit Converter (Build Your Own)
Define your own units of measurement and save them — perfect for niche workflows.
-
Paper Size Converter (A4 / Letter / B-Series / JIS)
Convert between ISO A/B/C, US Letter / Legal / Tabloid and Japanese JIS paper sizes in mm and inches.
-
Battery Life Runtime Calculator (mAh)
Calculate how long a battery lasts at a given current draw — mAh to hours, Wh, and screen-on time.