Convert temperature between scales
Translate Celsius, Fahrenheit, Kelvin and Rankine in real time. All conversions run locally — no server roundtrip.
How to convert temperatures
Pick the unit of your input, type a number, and read every scale at once.
- 01
Choose source unit
°C, °F or K — the math adjusts automatically.
Parsing is strict-but-tolerant — comments and trailing commas are accepted on input where the source format historically permits them; output stays canonical.
unitstricttolerantliveparseunit · source°C · liveunit = C
loaded · parsedtarget · ready - 02
Enter the value
Negative numbers and decimals work fine.
Conversion preserves type information where the target supports it (numbers stay numeric, booleans stay boolean) so the destination parser never has to re-coerce.
inputtype-preservinglosslesslivememoisedinput · options100 · live100
options applied · liveround-trip - 03
Read every scale
Celsius, Fahrenheit, Kelvin and Rankine update live.
Re-encoding is idempotent: running output back through the same converter produces the same bytes, which keeps round-trips git-friendly.
liveidempotentround-tripdiff-cleandeterministicF · converted212 · readyF = 212.0 K = 373.15
converted · livediff-clean - 04
Copy a value
One-click copy per row, or grab the full set.
Copy writes via
navigator.clipboard.writeText; downloads use the target’s native MIME so editors apply the right syntax highlighting on open.copyclipboardtarget MIMEblobclient-side✓ · copiedready · doneCopied
shipped · ready to shipsuccess
Converting between formats, safely
Pick the strictest source format
Lossy formats hide bugs. Choose JSON or YAML as your source-of-truth, convert downstream as needed.
Round-trip in CI
If your converter is idempotent, your CI can verify A → B → A equals the original. Catches subtle data loss.
Numbers vs strings differ
YAML/TOML have a number type; CSV doesn’t. Quote IDs in CSV to keep leading-zero values intact.
Watch character encoding
Source format may be Latin-1 / Windows-1252; target should be UTF-8. Convert encoding before structure.
Preserve comments where you can
YAML and TOML support comments. Don’t silently drop them — they often encode intent.
Schema-aware beats blind
Use a schema to guide conversion. Field types, required-ness, and defaults survive better with structure.
When to convert temperatures
Science, cooking, weather, engineering.
Recipes
Translate Fahrenheit oven settings to Celsius. Type information survives: numbers stay numeric, booleans stay boolean, strings stay strings. The destination parser doesn't have to re-coerce, which avoids the "'true' becomes "true"" bug class.
round-trip safeWeather
Read forecasts in the unit you grew up with. Run output back through the inverse converter to verify idempotent round-trips in CI. A → B → A should produce byte-identical input — if it doesn't, you've found data loss.
type-preservingLab notes
Switch between Celsius and Kelvin for absolute work. Comments and metadata survive where the target format supports them (YAML, TOML, HCL). The tool doesn't silently drop intent-encoded annotations, which keeps your config self-documenting.
schema-awareEmbedded firmware
Confirm sensor readings across scales. Pair with a schema (JSON Schema, OpenAPI, Zod, Pydantic) to catch shape drift on either side. Catch breaking changes at conversion time rather than at runtime in production.
losslessHVAC tuning
Match thermostat units to system specs. Output respects target-format conventions: quoting in CSV, indent in YAML, brackets in JSON. Existing parsers don't need patches, and the result drops into legacy pipelines unchanged.
diff-cleanTravel
Quickly grok temperatures abroad. Encoding-aware: handles UTF-8 vs UTF-16 vs Latin-1 / Windows-1252 transparently. The character-set surprise that breaks "works on my machine" doesn't apply here.
spec-gradeFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.