Why this one is not a chat prompt
A single conversion is a question you can ask almost anywhere. A column of two hundred dimensions out of a bill of materials is not. It is a data-handling job, and doing it by conversation has three failure modes that no amount of careful prompting fixes.
The first is that the data has to leave your machine. A bill of materials is often the most commercially sensitive document a project has, and pasting it into a hosted service is a disclosure regardless of what the terms say. Here the list never leaves the browser tab: the arithmetic runs in the page, there is no request to a server, and nothing is written to storage. Close the tab and it is gone.
The second is that a long list gets quietly shortened. Conversational tools summarize when the input is long, and a summary of two hundred dimensions is not a conversion of two hundred dimensions. This page processes every line it is given, up to 5,000, and reports how many it actually read so the count can be checked against your source.
The third is that a single wrong value is invisible. In a column of numbers, one line that came out 25.4 times too large looks exactly like every other line until somebody orders the wrong material. That is what the flagging below is for.
One line, one measurement
Each line is parsed independently, so a column does not have to be in one unit. 12.5 mm, 1 1/2 in, 3/8 in and 5 ft 10 in can all sit in the same list and each is read on its own terms. Fractions, mixed numbers, quote marks and spelled-out unit names are all accepted, the same grammar the feet-and-inches calculator uses.
A line that cannot be read is reported as unreadable and left out of the conversion rather than being guessed at. In a batch job, silently skipping a line is worse than failing it loudly: a silently skipped row changes the item count, and the item count is the only thing tying the output back to the source list.
Two lines that land on the same value
When two lines in the same list convert to the same length, within 0.05 per cent, both are marked. In practice this is one of two things: the same physical dimension written twice in different units, or the same item entered twice by accident.
The inch-and-millimeter case is the one worth understanding, because it is the one that survives a visual check. A list merged from a supplier's millimeter schedule and an in-house inch drawing will carry both 0.75 in and 19.05 mm for the same part. They read as two different sizes, they convert to exactly the same length, and anyone scanning the column counts two items where there is one. When the written numbers differ by a factor of 25.4 the note says so, because that ratio is what gives the pair away.
A flag is not a verdict. Two parts genuinely can be the same length, and then the flag costs one glance to dismiss. But if they were meant to be different sizes, one of them is probably left over from an earlier revision, and finding that out before the material is cut is worth a great deal more than the glance it took.
Export and print
The download button produces a CSV with the original line, its status, the converted value and any note attached. The original input column is preserved so the result can be audited against the source without opening the page again. Printing the result gives a table that can be clipped to a job packet, which is still the most reliable way to get a conversion onto a shop floor.
What it will not do
It converts length only — millimeters, centimeters, meters, kilometers, inches, feet, yards and miles. Area and volume are deliberately excluded even though they are derived from the same definitions, because a list mixing mm and mm2 is ambiguous to a parser reading one line at a time, and guessing is the one thing this tool is built not to do.
It also does not decide which unit a bare number means. A line reading simply 45 is read in the target unit shown in the selector, and the note column says so. If a source column is genuinely unitless, set the target deliberately before trusting the output.
Frequently Asked Questions
Is my list uploaded anywhere?
No. The conversion is performed by JavaScript running in the page. There is no network request carrying the list, no server-side processing, and no local storage write. The only way the data leaves the browser is if you download the CSV yourself. This is deliberate: a bill of materials or a drawing schedule is usually the most sensitive document in a project, and a conversion tool should not require handing it over.
What input formats are recognized?
Decimal numbers with a unit (12.5 mm, 0.75 in), fractions (3/8 in), mixed numbers (3 1/2 in), feet-and-inches pairs in either the spelled-out form (5 ft 10 in) or the trade shorthand (5' 10"), and plain numbers with no unit at all, which are read in the target unit. Unit names can be written out in full or abbreviated.
Why is a line marked as needing a check?
Because another line in the same list converts to the same length, within 0.05 per cent. That usually means the same dimension has been written twice in different units, or the same item has been entered twice. When the two written numbers differ by a factor of 25.4 — the inch-to-millimeter ratio — the note names that explicitly, since it is the clearest sign of a mixed-unit duplicate. The flag is a prompt to look, not a verdict: it catches the most common way a mixed-unit column goes wrong, and it costs one glance to dismiss when the match is genuine.
How many lines can it take?
Up to 5,000 at a time. Beyond that the list is truncated and the line count in the summary states that the limit was reached, so a partial result is never presented as a complete one. If you have more, split the list — the parser has no state between runs, so two batches give the same answer as one large one.
Does the exported CSV keep enough to check the result?
Yes, and deliberately so. Every row carries the original input text alongside the converted value, plus the status and any note. That means a second person can audit the output against the source list without re-running the conversion, and a row that was flagged can be traced back to the two lines that triggered the flag.