Momentum converter

Supported units are kilogram metres per second, gram centimetres per second, and pound feet per second, plus everyday aliases such as kg·m/s, kg m/s, g·cm/s, lb·ft/s, newton seconds, and pound feet per second.

What the momentum converter returns and which units it understands

A linear momentum conversion answers a narrow question: given a magnitude in one mass-times-velocity unit, what is the equivalent magnitude in another unit that people actually use in mechanics courses, laboratory notebooks, and engineering datasheets. This calculator accepts a numeric value, a source unit, and a target unit, then returns the converted result rounded to a stable precision, the canonical from and to identifiers, human-readable labels, the intermediate value in kilogram metres per second, and the SI factors used for the bridge. Canonical ids are kg_m_s for kilogram metres per second, g_cm_s for gram centimetres per second, and lb_ft_s for pound feet per second. Everyday spellings such as kg·m/s, kilogram_meters_per_second, g·cm/s, gram_centimeters_per_second, lb·ft/s, and pound_feet_per_second normalize to those ids so forms, query strings, and spreadsheets can reuse the same contract without inventing private enums. Newton-second aliases also map to the SI unit because impulse and linear momentum share that dimensional combination. There is no approximate lookup table and no floating culture-specific rounding path: the engine either multiplies and divides by fixed factors inside the supported magnitude range or rejects the input with invalid_input. Rejected cases include missing value, from, or to; non-finite numbers; magnitudes above the documented ceiling; and any unit string that is not on the supported list.

How factors are defined and how results stay reproducible

Optional scientific notation on the value string is allowed when it parses as a finite decimal; embedded spaces, hex prefixes, and non-numeric tokens are rejected with a clear message so a bad cell does not become a wrong collision result. Zero is a valid value and simply yields zero in the target unit; negative values keep their sign so signed one-dimensional momentum components stay meaningful. Computation multiplies value by the source factor in kilogram metres per second, then divides by the target factor: one gram centimetre per second is exactly one times ten to the minus five kilogram metres per second because one gram is one thousandth of a kilogram and one centimetre is one hundredth of a metre; one pound foot per second uses the exact international avoirdupois pound of zero point four five three five nine two three seven kilograms times the exact international foot of zero point three zero four eight metres. The preferred fields are value for the momentum magnitude, from for the source unit, and to for the target unit, with aliases amount, p, quantity, and momentum for the value, unit, from_unit, source, and input_unit for from, and target, to_unit, output_unit, and into for to so heterogeneous clients can share one contract. An optional precision field, with aliases decimals and dp, chooses how many decimal places to expose for value, result, and value_kg_m_s, defaulting to ten and capped at fifteen so JSON goldens stay stable. Pair the free browser run on this page with the priced API when you need the identical mathematical result inside an automated pipeline without re-implementing unit tables yourself.

Where linear momentum conversion fits in labs, teaching, and software

On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split — free interactive exploration and a priced, identical API — matches the rest of the KIT tier-A catalog and lets you move from a classroom demo to an automated pipeline without changing the mathematical result.