Decimal GB vs binary GiB
Drive vendors commonly use decimal GB and TB, while operating systems and technical tools may show binary GiB and TiB. One GB is 1,000,000,000 bytes; one GiB is 1,073,741,824 bytes. Selecting the wrong basis can create a noticeable difference across a large archive, so the unit stays explicit in every calculation.
Bitrate remains decimal bits per second. When comparing a device label with an operating-system report, also account for formatting, partitions, system files, and reserved flash behavior. The reserved-space input provides a transparent planning deduction without pretending to model a specific filesystem exactly.
Reserved capacity and filesystem overhead
A storage device rarely offers every labeled byte to audio. Filesystem structures, operating-system data, application caches, wear management, project databases, and future edits consume space. Reserving 5–15% can be practical depending on the device and workflow. The calculator applies your percentage directly and does not disguise it as measured overhead.
Container headers and tags also add bytes per file. Many very short clips may have proportionally more per-file overhead than a few long episodes. Embedded cover art can dominate tiny audio assets. Since the page cannot know that metadata, treat results as audio encoding estimates and validate a representative batch before purchasing or filling storage.
Planning an archive or publishing schedule
When you enter a monthly publishing frequency, the page estimates bytes for thirty days and one year from the selected item duration and bitrate. It does not show a schedule without that explicit input. The estimate excludes backups, masters, video, transcripts, artwork, and growth in episode length unless you add room through the reserved percentage.
A resilient archive usually keeps more than one copy and may retain WAV or FLAC masters plus smaller delivery files. This calculator covers one bitrate-based tier at a time. Plan master storage separately, consider verification and replacement, and avoid treating a single drive capacity result as a backup strategy.
Worked examples
A 100 GB decimal capacity with 5% reserved leaves 95 GB. At 128 kbps that is about 1649 hours. With three-minute songs, it represents about 32,986 complete items before per-file overhead. Changing to 320 kbps reduces the time to roughly forty percent of that amount because bitrate is two and a half times higher.
For four 30-minute podcast episodes each month at 96 kbps, the encoded payload is about 86.4 MB per month and roughly 1.04 GB per twelve months before overhead. The page derives the schedule only from the frequency you enter and can export the bitrate comparison as CSV through a temporary local object URL.