Try reading an audio specification without its units. “320, 44.1, 16” is fairly meaningless. Add kbps, kHz and bit, and you have three separate pieces of information. They belong in different columns, even if a player puts them beside each other.
The distinction is worth learning before you buy equipment. A shop can advertise a bigger number without explaining what it counts. Here is a way to do the arithmetic yourself and keep the claims in proportion.
Start with samples
For this example, use uncompressed stereo PCM at 44.1 kHz and 16 bit. MDN's audio concepts documentation explains the underlying terms. A sample rate of 44.1 kHz means 44,100 samples each second, for each channel. Stereo gives us two channels. Each sample in this integer PCM example takes sixteen bits.
Multiply them: 44,100 × 16 × 2 = 1,411,200 bits per second. Expressed in decimal kilobits, that is 1,411.2 kbps. The three quantities produce a data rate; none is a substitute for the others.
For four minutes, multiply by 240 seconds. Divide by eight to convert bits to bytes. The answer is 42,336,000 bytes, or about 42.34 decimal MB of audio payload. Headers and tags would add something to the file, so this is a calculation rather than a claim about a file we measured.
Change one quantity
Keep everything else the same and make the recording mono. The payload rate halves because there is one channel instead of two. Keep stereo and change the representation to 24 bit: the rate becomes 2,116.8 kbps, because twenty-four is one and a half times sixteen.
| Our calculated PCM example | Payload rate |
|---|---|
| 44.1 kHz, 16 bit, mono | 705.6 kbps |
| 44.1 kHz, 16 bit, stereo | 1,411.2 kbps |
| 44.1 kHz, 24 bit, stereo | 2,116.8 kbps |
| 96 kHz, 24 bit, stereo | 4,608 kbps |
You can reproduce every row with the same multiplication. You cannot use the last row to prove that its music sounds better. We have changed the representation, not conducted a listening comparison or inspected the recording's master.
Encoded bitrate needs a separate column
An MP3 or AAC data rate describes its encoded stream. Treating that number as directly equivalent to an uncompressed PCM rate loses the distinction between the representations. Our format comparison calculates the storage for constant-bitrate listening copies.
Lossless FLAC introduces another easily confused setting. The FLAC command-line documentation describes compression presets. A different preset is not a vote for a different lossy quality level. File size and encoding work can change while the format retains the input audio.
Take the numbers back to the device
Write down what the source contains, then check what the actual output path supports. An application's available selection does not describe every connection afterwards. Apple's device-specific lossless instructions are a useful example of why those two checks belong together.
Leave the equipment purchase until you know which requirement is missing. If the current arrangement plays what you need, a larger advertised maximum may have no practical role. If you want to compare what you hear, our ABX guide explains how to keep the sources and conditions consistent.