Calculate song file sizes


Q: How much space does a song take up on an iPod nano 2G?

Calculate song file sizes

– Kelsey

A: The amount of storage space that a given music file will take up on any digital music player is actually a function of the length of the song and the bitrate at which it is encoded.

Essentially, digital music formats specify a bit-rate measured in kilobits per second, abbreviated kbps. This specifies how much digital data is used to reproduce a single second of audio. For example, looking at a commonly-used bit-rate of 128 kbps, for each second of audio on the track, 128,000 bits of data are used. Higher bit-rates mean larger files, since more data is stored for each second of audio, but this also means additional quality, since there is more data present to reproduce a higher level of fidelity in the resulting audio.

Keep in mind that in this case we are talking about measurements in terms of computer bits rather than the more commonly-used storage measurement of bytes. There are eight bits in a byte, so these numbers can be divided by eight to determine approximately how many kiloBYTES of data each second of audio will take up. So a 128 kbps audio file would take up approximately 16KB for each second of audio (this is not an exact measurement due to some unit differences, but will do fine for the purpose of getting an approximate measurement).

So, by applying some basic math, you can easily calculate the file size of any given audio track after conversion to an MP3 or AAC file. Simply take length of the track in seconds, multiply it by the bit-rate, and then divided by eight to get the result in kbps.

So if you have a 5 minute song, encoding at 128kbps, you would do this as follows:

5 minutes = 300 seconds
128kbps * 300 seconds = 38,400 kilobits of data
38,400 kilobits / 8 = 4,800 kb

To take this one step further, you could then convert this into megabytes simply by dividing the result by 1,024.

Note that the key here is the bit-rate that you are encoding at, rather than the format itself. There are no significant size differences between MP3 and AAC formats inherently, for example—a 128 kbps MP3 and a 128 kbps AAC should result in files that are approximately the same size. There will be some additional space taken up in each file to store metadata such as track, album, artist, genre, and things like album artwork, but this is generally insignificant compared to the size of the audio data itself.

Further, the ratios between the bit-rates can be used to determine the approximate size differences. 256 kbps tracks will naturally take up twice the storage space as 128 kbps files.

One other important consideration to keep in mind is that the above formula will only work for “Constant Bit Rate” or CBR files. There is another type of encoding, known as “Variable Bit Rate” (VBR) which uses an average or variable bit-rate throughout the file. Since these files may have some sections at 128 kbps and others at 192 kbps, it’s difficult to determine exactly how much space these will take up, although the average bit-rate can still be used as an approximation. Note that most files downloaded from online sources will be in a CBR format, so this is seldom an issue unless you are encoding music yourself into a VBR format.

More detailed information on these calculations can be found in the thread Calculating File Size from Bitrate in our iLounge Discussion Forums.

It should also be noted that the capacity specifications that Apple publishes for the various iPod models are based on 128 kbps files at four minutes per song. An iPod that is listed as holding “4,000 tracks” will hold significantly less if you are encoding at a higher bit-rate.

For a nice quick calculation of how many tracks each iPod can be expected to hold at various bit-rates, be sure to check out our iPod Storage Calculator:


Calculate song file sizes



Jesse Hollington

Jesse Hollington was a Senior Editor at iLounge. He's written about Apple technology for nearly a decade and had been covering the industry since the early days of iLounge. In his role at iLounge, he provided daily news coverage, wrote and edited features and reviews, and was responsible for the overall quality of the site's content.