A few weeks ago I wrote about the math behind fitting 11 songs into 4MB — a claim someone made at a party, the numbers I ran when I got home, and what the science of audio compression actually says about what's possible. [You can read that here.] The short version: at standard song lengths, 4MB for 11 songs produces audio that sounds like music being described by someone who vaguely remembers it. The math doesn't lie.

But that piece assumed something I didn't examine until later: that a "song" is three minutes long.

In 2026, that assumption is losing ground fast — and when you let go of it, everything changes. Songs are getting shorter. That's documented, industry-wide, and accelerating. The average track length has been declining since streaming became dominant, because streaming rewards replays, not duration. Spotify pays per stream regardless of length (above a 30-second minimum threshold). TikTok and Reels conditioned listeners to expect a payoff in the first eight seconds or they're already gone. Entire genres — hyperpop, phonk, drill, bedroom pop — are built around tight, sub-two-minute structures where brevity isn't a compromise, it's the point.

So the question this piece is actually answering is: if songs are getting shorter anyway, and if file sizes shrink dramatically when songs are shorter, what does that open up — and should you be compressing smarter even when nobody's forcing you to?

The answer to that last question is yes. Here's why, and here's how.

At one minute and twenty seconds per song — which is a real, plausible track length in 2026 — eleven songs in 4MB produces audio at about 37 kbps. That's not comfortable, but it's no longer in "unrecognizable" territory, especially with Opus in mono. Tighten it to 47 seconds per song and you break 64 kbps, which is AM Radio quality — listenable, present, the notes are all there. Get to 23 seconds per song at 128 kbps and you have standard MP3 quality. That's good. No asterisks.

The constraint hasn't changed. What changed is the art form operating inside it.

File compression isn't just an emergency measure when you've run out of space. There are real professional contexts where understanding this is the difference between someone who's prepared and someone who's scrambling.

Mobile Games and Interactive Experiences

Game audio is one of the most aggressive compression environments in professional music. Apple's App Store recommends keeping apps under 200MB for cellular download — and that 200MB has to include the entire engine, art assets, UI, and code, not just audio. A composer scoring a mobile game is working with audio budgets that make "4MB for 11 songs" look generous. Short ambient loops, UI interaction sounds, and adaptive music layers all need to be small, load fast, and loop cleanly. Knowing how to get a 90-second ambient loop to 400KB without sounding hollow is a skill that gets you hired and re-hired. Developers remember composers who deliver to spec.

The same logic applies to browser-based experiences, WebXR, and interactive installations where audio needs to load over a network before a user's attention moves on.

NFT Platforms and On-Chain Audio

Different platforms have different file size caps and different formats they'll accept. Knowing how to get your audio to the right size without sacrificing what matters — before you pay a minting fee — is basic professional hygiene at this point. The platforms don't tell you how to do this. They just tell you the limit.

There's also a more interesting on-chain conversation happening around recursive ordinal inscriptions on Bitcoin, which is explored in [Part 3 of this series], but the short version is: audio that lives permanently on a blockchain needs to be small enough to be economically feasible to inscribe, and understanding compression is how you get there without your music sounding like a phone call from 2003.

Social Media Recompression: Know What Survives

This is one that almost nobody talks about and every musician should understand. When you upload audio or video to Instagram, TikTok, YouTube, or Twitter/X, the platform recompresses it. You don't get to opt out. Your 320kbps master hits their transcoding pipeline and comes out the other side at whatever bitrate their system decided. Instagram Reels audio is famously aggressive about this. Tracks with a lot of sub-bass and stereo width are the most vulnerable — the recompression tends to collapse the low end and narrow the image.

What survives? Clear mid-range. Strong transients. Arrangements that don't rely entirely on frequencies that compression artifacts destroy. Understanding what happens at low bitrates tells you what to protect in your mix for social delivery. That's not a compromise — that's knowing your medium.

Sync Licensing Libraries

Sync libraries — Artlist, Musicbed, Epidemic Sound, Musicbed, and dozens of others — have technical delivery specs. Wav files, specific sample rates, loudness targets. Some of them also have upload limits per submission or per account tier. The musicians who move through these pipelines quickly are the ones who've built a file management workflow that doesn't require reformatting everything from scratch every time they have a deadline.

Developing Markets and Low-Bandwidth Listeners

If your music reaches audiences in regions where mobile data is expensive and connection speeds are inconsistent — and if you're releasing independently with any kind of global ambition, it does — then the file size of your streaming deliverable matters to your actual listeners. Most DSPs handle this automatically with adaptive streaming, but for direct distribution, smart archives, and anything you're hosting yourself, smaller well-encoded files mean more people actually hear your music without buffering.

Radio and Broadcast Delivery

Broadcast specs vary by country and by station. Some require specific loudness levels (LUFS), specific bit depths, specific sample rates. Many broadcasters receive hundreds of submissions. Having files that are correctly formatted and appropriately sized is the basic table-stakes of professionalism in that space. Being the person who sends a 200MB WAV when a 7MB MP3 at 320kbps was what was needed doesn't make you seem serious — it makes you seem like you've never done this before.

Yes. With a structure.

Not "compress everything to the smallest possible size" — that's a different and wrong answer. The right answer is: keep your masters untouched and build a compression workflow into how you archive and distribute everything else.

Here's the philosophy: storage is cheap until it isn't, transfer is fast until you're on a plane, and the habit of file hygiene compounds across a career. A producer with ten years of work and no file management system is sitting on terabytes of session data, duplicate bounces, and full-quality files for demos that were rejected in 2019. A producer with a compression workflow is sitting on a navigable, affordable archive of everything they've made, formatted correctly for every use case they encounter.

The other reason to compress intelligently — even when you have space to spare — is that it forces a discipline of intentional delivery. Every file you send, post, or store has a purpose. The purpose determines the format. A reference mix going to a collaborator doesn't need to be a 50MB WAV. A preview clip for an A&R doesn't need to be lossless. A session archive for your own records needs to be complete but not bloated. Getting precise about what each file is for makes you a better-organized artist and a more professional collaborator.

Here's what the math looks like on Pinata — one of the most common IPFS pinning services used for music NFTs and on-chain storage. Their free tier is 1GB.

For session stems specifically, the difference is violent. A typical project bounce — ten stems, three minutes each — runs about 506MB as WAV files. The same ten stems as Opus at 96kbps runs about 21MB. Pinata's free tier holds two full WAV sessions or 48 full Opus sessions. Same account. Same storage limit. Different workflow.

The same math applies across every free-tier service you're using:

The actual workflow, step by step:

1. Keep your masters sacred. Your working session and your final WAV/AIFF mix stay in their original, uncompressed format. Non-negotiable. This is the original painting. Everything else is a print.

2. Bounce reference stems from every session before you close it. Bass, drums, vocals, everything else — separate stems, full quality WAV. These are your working archive. Store them locally on an external drive and don't touch them.

3. Create compressed Opus versions of everything for cloud/IPFS storage. Using FFmpeg (free, command line):

# High-quality archive version — you'd be comfortable sending this to anyone
ffmpeg -i mix.wav -c:a libopus -b:a 96k output_archive.opus

# Streaming/preview version
ffmpeg -i mix.wav -c:a libopus -b:a 64k output_preview.opus

# Batch process a whole folder
for f in *.wav; do ffmpeg -i "$f" -c:a libopus -b:a 96k "${f%.wav}.opus"; done

4. Pin the Opus versions to Pinata (or your IPFS service of choice). Name your pins clearly — artist name, project name, stem type, date. Pinata lets you add metadata to pins. Use it. Your future self will thank you when you're looking for a specific bass stem from 2024.

5. Keep a simple log. A spreadsheet with columns for: project name, session date, what's stored where, IPFS CID (the hash Pinata gives you), format, and notes. This takes five minutes when you're finishing a session and saves hours when you need something specific six months later.

Beyond the obvious:

Wearables and IoT. Smartwatch apps, interactive clothing, sensor-triggered audio installations — all of these have severe storage constraints. A wearable that plays music in response to biometric data needs audio that fits on an embedded processor. Short, compressed, designed for the constraint.

QR-linked physical art. An emerging practice — physical artwork, merch, or packaging with a QR code that triggers audio playback. The audio lives on IPFS or a CDN. Smaller files mean faster load on mobile networks, which means the person who scanned the QR doesn't put their phone away before the audio starts.

Interactive PDFs and ebooks. Yes, you can embed audio in PDFs. Publishers and educators do this regularly. Size limits are real. A 30-second highly compressed intro track is the difference between a document that attaches easily and one that bounces from every inbox.

Voice assistant skills. Alexa Skills and Google Assistant apps can serve audio. The response payload has size limits. Custom music experiences built into voice assistants work better when the audio assets are appropriately sized.

Archival donation and music libraries. If you're submitting music to academic archives, sample libraries, or any institution that catalogs audio, their ingest systems often have file size guidelines. Clean, correctly-formatted, compressed-but-high-quality files move through these pipelines faster and get accepted instead of flagged.

Your own direct fan distribution. Email lists, Substack attachments, Bandcamp previews, Patreon audio posts — all of these have limits that WAV files routinely exceed. A well-encoded Opus file at 96kbps is audibly indistinguishable from MP3 320kbps for most listeners and dramatically smaller. Sending your fans audio that actually loads is a basic service.

File compression is not a compromise. It's a skill set that belongs in the same category as knowing how to export at the right loudness level for streaming, or knowing the difference between 44.1kHz and 48kHz and when each is appropriate. It's the difference between an artist who understands their medium and one who is perpetually surprised by it.

The musicians who build this workflow now — before storage costs spike, before a platform changes its limits, before they have ten years of sessions in formats that are becoming obsolete — are the ones who own their catalog without friction. The ones who don't build it are the ones who will eventually be paying someone to help them figure out where everything went.

Compression as a policy isn't pessimism. It's architecture. And the people who think clearly about architecture rarely get caught by the walls.

This topic Premiered on GIRL BARS by Endodeca This is part of a series on audio compression and Bitcoin-native music.