How Many Songs Fit Calculator

How song file size is calculated

Audio file size comes down to one multiplication. Bitrate is how many kilobits of data the encoder spends on every second of sound, so the file size is bitrate times duration, divided by 8 to turn bits into bytes.

File size (MB) = bitrate (kbps) × seconds ÷ 8 ÷ 1000

That is the whole formula, and it is why the same song can be 3 MB or 24 MB. A three-and-a-half-minute track is 210 seconds long. At 128 kbps the encoder spends 128 kilobits a second, so the file is 128 × 210 ÷ 8 ÷ 1000 = 3.36 MB. At 320 kbps the same song is 8.4 MB. At lossless quality around 900 kbps it is 23.6 MB, seven times the size of the 128 kbps version for a difference most people cannot hear on earbuds.

Then divide your storage by the file size. The one detail that trips people up is the storage itself: manufacturers sell a 64 GB drive as 64,000,000,000 bytes, but computers count a gigabyte as 1,073,741,824 bytes, so the same drive shows up as 59.6 GB in a file manager. The NIST reference on SI prefixes explains the decimal-versus-binary gap, and it is worth knowing because it is the first of two bites out of your storage.

The second bite is the operating system. A phone or tablet with 64 GB of marketed storage usually has 45 to 50 GB free after the OS, pre-installed apps and caches. That is why the calculator has a usable-space input: 10% is realistic for a memory card, and 20% to 25% is realistic for a phone.

Worked example: a 64 GB phone at 256 kbps

A 64 GB phone, music encoded at 256 kbps, average song length 3.5 minutes, and 10% of the storage lost to the file system.

• Usable storage: 64 GB × 90% = 57.6 GB, which is 57,600 MB
• Song length: 3.5 minutes = 210 seconds
• File size: 256 × 210 ÷ 8 ÷ 1000 = 6.72 MB per song
• Songs that fit: 57,600 ÷ 6.72 = 8,571 songs
• Total play time: 8,571 × 3.5 minutes = 29,999 minutes = 500 hours
• That is 20.8 days of nonstop music

Drop the quality to 128 kbps and the same phone holds 17,142 songs, exactly double, because the bitrate halved. Push it to 320 kbps and you get 6,857 songs. Nothing else changed; only the encoding quality moved.

Now be honest about the phone. Use 25% for the OS and pre-installed apps instead of 10% and the usable space is 48 GB, or 48,000 MB. At 256 kbps that is 7,142 songs, 1,400 fewer than the optimistic figure, and closer to what you will see. For a phone, use 25%. For a microSD card in a dedicated player, 10% is fine.

Bitrate and file size at a glance

All figures for a 3.5-minute song on a 64 GB device with 10% lost to the file system, so 57,600 MB usable:

Reading down the table, the trade is roughly linear: doubling the bitrate halves the songs. Going from 128 to 320 kbps costs you 10,285 songs, 60% of your library, and buys a quality difference that is inaudible on phone speakers, earbuds in a car, or a Bluetooth connection, all of which re-compress the audio anyway.

Where high bitrates do earn their space is a good pair of wired headphones or a home stereo, where a 320 kbps file against a 128 kbps file is a real, repeatable difference. Lossless is worth it mainly for archiving a library you intend to re-encode later, or for classical and acoustic music with a lot of quiet detail. The FLAC format specification explains what lossless preserves if you want the technical version.

How much storage your device gives you

The capacity on the box is not the capacity you can fill with music. There are two separate deductions, and most people only account for one.

• Decimal versus binary gigabytes. A 64 GB device holds 64,000,000,000 bytes, which a file manager reports as 59.6 GB. That is a 7% gap before you have stored anything.
• The operating system. iOS and Android, plus pre-installed apps, caches and the recovery partition, take 10 to 15 GB on a modern phone. On a 64 GB phone that leaves roughly 45 to 50 GB for your own files.
• Everything else on the device. Photos and videos are the biggest competitor for space. A single 4K video clip can be 400 MB, the equivalent of 60 songs at 256 kbps.

Worked through: a 64 GB phone with 12 GB of system and 15 GB of photos has about 32 GB left for music. At 256 kbps that is 32,000 ÷ 6.72 = 4,762 songs, not 8,571. Still a lot, but less than half the headline number, and it is the number you will hit.

Memory cards are cleaner because they carry no operating system, but they still have the decimal-versus-binary gap and they need a little free space to work well. If you are buying a card for a dedicated music player, budget 90% of the stated capacity and you will not be disappointed.

MP3, AAC, FLAC and streaming

Format matters as much as bitrate, and the names are less important than two questions: is it lossy, and how efficient is the encoder?

• MP3. The oldest and most compatible lossy format. At 320 kbps it is transparent to most listeners. Every device plays it.
• AAC. Roughly 20% to 30% more efficient than MP3, which is why a 256 kbps AAC file sounds like a 320 kbps MP3 and is 20% smaller. It is the default for Apple Music and iTunes purchases.
• Ogg Vorbis and Opus. More efficient again, and open source, but support outside Android and desktop players is patchy.
• FLAC and ALAC. Lossless, about 50% to 60% of CD size with no quality loss at all. Big files, and the only format worth using if you plan to re-encode later.

The practical upshot: if you are ripping your own CDs, 256 kbps AAC or 320 kbps MP3 covers almost everyone. If you are downloading, you rarely get a choice, the store or service picks the format and the bitrate for you.

Streaming changes the arithmetic entirely, because nothing is stored. But the offline-download feature on most services is exactly this calculation: pick the quality setting and the app fills your device with the same MB-per-song figures from the table above. On a 64 GB phone, downloading at the highest quality setting rather than the default is often the difference between 1,500 songs and 5,000.

Turning songs into hours of listening

Song count is the number people search for; hours is the number that matters. The conversion is song count times average length.

Hours = songs × minutes per song ÷ 60

• 8,571 songs at 3.5 minutes: 500 hours, 20.8 days of nonstop music
• 12,000 songs at 4 minutes (128 GB at 320 kbps): 800 hours, 33.3 days
• 34,285 songs at 3.5 minutes (256 GB at 256 kbps): 2,000 hours, 83.3 days
• 2,438 lossless songs at 3.5 minutes: 142 hours, 5.9 days

For context, the average American listens to about 20 hours of music a week. Even the lossless library on a 64 GB phone is seven weeks of continuous listening, and the 256 kbps library is nearly six months of it. Unless you are running a shop sound system, almost nobody needs 17,000 songs offline at once.

The most useful way to use those numbers is per playlist. A 500-song playlist at 256 kbps is 500 × 6.72 = 3,360 MB, or 3.36 GB, a rounding error on a 64 GB phone. A 1,000-song library at the same quality is 6.72 GB. So if you are deciding between quality and capacity, ask how big your library is first: for most people it is under 2,000 songs, which fits at 320 kbps on almost anything made in the last decade.