The conversions you look up once a year: cooking, pace, sound, and more

Some units do not belong to a single field the way torque belongs to mechanical engineering or sievert belongs to radiology, they show up once in a recipe, once in a race result, once in an internet plan comparison, and are gone again before the conversion sticks in memory. UnitSnap groups ten of these under Other: data transfer, cooking, dry volume, lumber volume, metric prefixes, frequency, sound, typography, pace, and number bases. This guide covers the ones people search for most, with enough context that the number means something rather than being a figure copied and forgotten.

Cooking measurements: the conversion every recipe eventually needs

Cooking conversions trip people up because volume measures, cups, tablespoons, milliliters, are only reliable for liquids and free-flowing dry ingredients; a cup of flour and a cup of sugar do not weigh the same, so a serious baking recipe increasingly gives weights in grams rather than volumes. As a working reference, 1 US cup equals roughly 237 milliliters, 1 tablespoon equals 3 US teaspoons or about 15 milliliters, and 1 cup of all-purpose flour weighs approximately 120 to 125 grams when spooned rather than packed, a distinction that alone can shift a recipe's outcome by ten percent or more.

Dry volume and lumber volume extend this idea into bulk quantities: dry volume units like the US bushel and peck still appear in agricultural and gardening contexts (1 bushel equals about 35.24 liters), while lumber volume, board feet in the US versus cubic meters elsewhere, is what a hardware store or timber supplier actually prices material by, and getting the conversion wrong on a large order is an expensive mistake rather than a minor one.

Pace and speed: what a race result actually means

Pace, typically minutes per kilometer or minutes per mile, is speed expressed backwards, time per distance rather than distance per time, which is why it does not convert with a simple multiplier the way speed does: converting min/km to min/mile requires inverting to a speed, converting the distance unit, then inverting back. A 5:00 min/km pace, a solid recreational running pace, works out to roughly 8:03 min/mile, a conversion runners doing international race comparisons look up constantly since US races are typically timed in miles while most of the world runs in kilometers.

Data transfer and storage: bits, bytes, and why downloads look slow

Data transfer speed, in megabits per second (Mbps), and file size, in megabytes (MB), use different base units that are easy to confuse: there are 8 bits in a byte, so an internet connection advertised at 100 Mbps downloads at a theoretical maximum of 12.5 MB per second, not 100 MB per second, a factor-of-8 gap that explains why a download always seems to run slower than the plan's headline speed suggests. Storage capacity itself adds a second wrinkle: manufacturers typically use decimal gigabytes (1 GB equals 1,000,000,000 bytes) while operating systems often report binary gigabytes (1 GiB, commonly labeled GB in the interface, equals 1,073,741,824 bytes), which is the entire reason a freshly bought drive shows less capacity than the box advertised.

Sound, frequency, and the decibel scale

Sound level, in decibels (dB), is logarithmic rather than linear, meaning each 10 dB increase represents roughly a tenfold increase in sound intensity, not a proportional one, which is why a quiet room at 30 dB and a normal conversation at 60 dB are separated by far more than double the loudness they might appear to be on the number line. A whisper measures around 20 to 30 dB, normal conversation around 60 dB, a busy street around 80 to 85 dB, and prolonged exposure above roughly 85 dB is commonly cited as the threshold where hearing protection becomes advisable. Frequency, in hertz (Hz), measures pitch rather than loudness, with human hearing typically spanning about 20 Hz to 20,000 Hz (20 kHz), and the two are independent, a sound can be loud and low-pitched or quiet and high-pitched.

Typography and number bases: the conversions programmers and designers need

Typography units, points and picas, are holdovers from print production that persist in design software: 1 point equals 1/72 of an inch, and 12 points make a pica, so a 12-point font is, by definition, one-sixth of an inch tall in its nominal size, a figure worth knowing when translating a print layout to a screen measured in pixels instead.

Number base conversions, binary to decimal, hexadecimal to decimal, and the reverse, come up constantly in programming and networking rather than everyday life: a color code like #FF6600 is hexadecimal, an IP address subnet mask calculation often needs binary, and a memory address or error code in a technical document is frequently given in hex because it maps more compactly to binary than decimal does, four binary digits map to exactly one hex digit, which is the entire reason the format persists in technical contexts despite looking unfamiliar to a general reader.

Metric prefixes: the ones people forget

Metric prefix conversions, kilo, mega, giga, milli, micro, and the less common centi, deci, and nano, underpin nearly every other conversion in this guide even when they are not the star of the calculation: a kilogram is 1,000 grams, a megabyte is generally understood as 1,000,000 or 1,048,576 bytes depending on convention, and a microfarad is one millionth of a farad. The prefixes people forget rather than misuse are usually the less common ones in casual conversation, deci- (one tenth, as in decibel and deciliter) and centi- (one hundredth, as in centimeter and centigram), both of which sit between the familiar milli- and the base unit and are easy to skip over when scanning a table quickly.

A grab-bag category, but not a random one

What ties these ten categories together is not a shared field but a shared pattern: each one is a conversion most people need rarely enough to never fully memorize, but often enough that looking it up from scratch every time is wasteful. Bookmarking the specific converter for the one or two you actually use, a recipe conversion, a pace calculator, a hex-to-decimal tool, tends to be more useful than trying to remember the factors, since the factors themselves are exact and instantly available below.