Compress audio files

Need to fit an attachment limit? Re-encode at a lower bitrate and pick your size/quality trade-off. Conversion happens in your browser — the file never touches a server.

Loading tool…

Audio compression shrinks a file's size by re-encoding it at a lower bitrate, measured in kbps. A track exported at 320 kbps carries far more data per second than the same track at 128 kbps, and dropping that number is the single biggest lever on final file size. This is lossy compression, so the discarded data doesn't come back — but for a Suno song that's headed to a Discord chat, a Reddit post, or an email thread, the difference is usually inaudible on phone speakers and earbuds while the file weighs a fraction of the original.

You reach for this when a hard size ceiling is in the way: a messaging app that rejects anything over its cap, a form that won't accept your upload, or a storage folder you're trying to keep lean. Because everything runs in your browser, there's no queue, no account, and no upload — your unreleased tracks stay on your machine. Pick a bitrate, watch the estimated size, and export when the trade-off looks right for where the file is going.

How it works

  1. 1

    Drop the audio file.

  2. 2

    Pick a target bitrate — 96 kbps halves most MP3s and still sounds decent.

  3. 3

    Click compress and download.

When to use it

  • Squeezing a Suno track under Discord's free-tier upload cap so you can drop it straight into a server channel without a Nitro subscription or an external link.
  • Trimming a batch of demo MP3s before attaching several to a single Gmail or Outlook message that would otherwise blow past the 25 MB attachment limit.
  • Shrinking reference tracks so they load faster and eat less storage when you're collecting feedback in a shared Google Drive or Dropbox folder.

FAQ

How small will it get?

Size scales with bitrate: a 3-minute track is ~2.9 MB at 128 kbps, ~2.2 MB at 96, ~1.4 MB at 64.

What's the catch?

Lower bitrates lose detail — cymbals and airy reverbs suffer first. 64 kbps is fine for voice, rough for music.

Does compressing an already-compressed MP3 hurt the quality more?

Yes. Re-encoding a lossy file to a lower bitrate is generational loss — the encoder throws away data a second time on top of what Suno's original export already discarded. For the best result, start from the highest-quality version you have and compress once rather than repeatedly re-saving the same file.

What bitrate should I pick for a Suno song?

For casual sharing and phone playback, 128 kbps is a common sweet spot that roughly halves a 256 kbps file while staying clean on most earbuds. Drop to 96 kbps only when you need every kilobyte, and keep 192 kbps or higher if the listener might play it on real speakers or headphones.

Will compressing change the length or format of my track?

No. Lowering the bitrate only reduces how much data is stored per second — the song plays for exactly the same duration. The output stays a standard audio file that any player, phone, or upload form will accept; only the file size and audio detail change.

Related tools