Frequency converter

Supported units are hertz, kilohertz, megahertz, gigahertz, revolutions per minute, and radians per second, plus everyday aliases such as Hz, kHz, MHz, GHz, rpm, rev/min, and rad/s.

What the frequency converter returns and which units it understands

A frequency conversion answers a narrow question: given a magnitude in one unit, what is the equivalent magnitude in another unit that people actually use for oscillators, radio bands, rotating machines, and angular-rate control. 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 hertz, and the SI factors used for the bridge. Canonical ids are Hz for hertz, kHz for kilohertz, MHz for megahertz, GHz for gigahertz, rpm for revolutions per minute, and rad_s for radians per second. Everyday spellings such as hertz, kilohertz, megahertz, gigahertz, rev/min, revolutions_per_minute, rad/s, and radians_per_second normalize to those ids so forms, query strings, and spreadsheets can reuse the same contract without inventing private enums. There is no approximate clock-drift path and no temperature-compensated crystal model: 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 clock rate. Zero is a valid value and simply yields zero in the target unit. Computation multiplies value by the source factor in hertz, then divides by the target factor: one kilohertz is exactly one thousand hertz; one megahertz is exactly one million hertz; one gigahertz is exactly one billion hertz; one revolution per minute is one sixtieth of a hertz because one revolution per second equals sixty RPM; one radian per second is one over two pi hertz because angular frequency omega equals two pi times cyclic frequency f. The preferred fields are value for the frequency magnitude, from for the source unit, and to for the target unit, with aliases amount, frequency, n, and quantity 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_hz, 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 frequency conversion fits in RF, motors, 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.