How to Cut Audio in Audacity (2026 Step-by-Step)

Audacity is the free, cross-platform desktop standard for audio editing. It has been the default answer to "what should I use to cut an MP3" for two decades, and it is genuinely good — multitrack editing, real fades, normalization, noise reduction, and a stable plugin ecosystem all in one open-source package. It also has a learning curve, a desktop install, and a few well-known gotchas (the LAME prompt, the Save-vs-Export confusion, the sample-rate issue) that trip up first-time users.

This guide is the step-by-step cut walkthrough, the gotcha list, and the honest comparison of when Audacity is the right tool versus when a browser cut is faster.

When to Use Audacity vs a Browser Tool

Audacity wins when:

• You need fades, normalization, or noise reduction along with the cut
• The job is multitrack (mixing two or more files)
• You are doing many cuts on the same file (Audacity is faster once loaded)
• The source needs format conversion that Audacity supports natively (FLAC, OGG, AIFF, WMA on Windows)
• You want the .aup3 project file to preserve edit history for later revision

A browser tool wins when:

• The job is a single cut on one file
• You are on a phone or tablet (Audacity is desktop-only)
• You do not want to install software
• Privacy matters and you do not want desktop telemetry (Audacity has collected basic usage telemetry by default since version 3.0; opt-out exists but is opt-out, not opt-in)
• You need the cut done in 30 seconds without launching anything

For a one-off MP3 cut, /mp3-cutter is faster than starting Audacity. For a ringtone, /ringtone-maker is purpose-built. For a 5-track podcast edit with crossfades, Audacity is the right tool.

The Cut Walkthrough

Audacity's basic cut workflow has not changed meaningfully across versions 2.x and 3.x. The current version as of 2026 is 3.5.

1. Open the file. File → Open, or drag the audio file directly into the Audacity window. MP3, WAV, FLAC, OGG, and AIFF all work natively. M4A/AAC requires the FFmpeg library on most platforms (Audacity prompts to install on first M4A open). The waveform renders within a few seconds for files under an hour; longer files take proportionally longer.

2. Wait for the waveform. Audacity displays the file as a stereo or mono waveform with time markers along the top. Zoom in with Cmd/Ctrl + scroll wheel, or use the magnifying-glass tools in the toolbar. For precise cuts, zoom in until you can see individual peaks.

3. Select what you want to KEEP. Click and drag the selection tool (the I-beam cursor, default tool) across the segment you want to keep. The selection turns dark blue. The status bar at the bottom shows the selection's start, end, and length in seconds.

4. Trim to the selection. Edit → Remove Special → Trim Audio (keyboard shortcut Cmd/Ctrl + T). Audacity deletes everything outside the selection, leaving only the selected segment. The waveform shifts left to start at zero.

Alternative — delete what you do NOT want: Select the segment you want to remove, then press Delete or Cmd/Ctrl + K. The unselected audio collapses into the remaining time. Useful when you want to remove silence from the middle without trimming the ends.

5. Verify the cut. Press the spacebar to play. If the cut sounds right, proceed to export. If not, Cmd/Ctrl + Z to undo (Audacity's undo history is unlimited within a session).

6. Export. File → Export Audio. The export dialog asks for format, filename, and quality settings. Do not use File → Save Project — that creates a .aup3 project file (Audacity's internal format) that only Audacity can open. See the Save vs Export gotcha below.

For MP3 export, choose "MP3 Files" from the format dropdown. The bitrate dropdown offers Constant (CBR) at fixed rates, Variable (VBR) at quality presets, and Average (ABR) at target bitrates. For most uses, VBR at "Standard, 170-210 kbps" matches the LAME V2 preset and is transparent for music. For a deeper bitrate discussion see audio bitrate explained.

For WAV export, choose "WAV (Microsoft)" and pick 16-bit PCM (CD-quality) or 24-bit PCM (mastering-quality). Sample rate matches the project rate by default; verify it matches the source if you want to avoid resampling.

7. Save. Click Save. Audacity writes the file. Done.

The LAME Library Prompt (First-Time MP3 Export)

On a fresh Audacity install, the first MP3 export triggers a prompt: "To export audio in MP3 format, Audacity needs the LAME library." This is a holdover from the pre-2017 era when MP3 patents required Audacity to ship without a built-in MP3 encoder.

The patents expired in 2017, but Audacity's policy is still to download LAME at first use rather than bundle it. On modern Audacity (3.x), clicking the prompt downloads and installs LAME automatically — you do not need to manually find a binary. On older 2.x versions you may need to download lame_enc.dll (Windows) or libmp3lame.dylib (Mac) and point Audacity at the file location.

The prompt only appears once per install. Subsequent MP3 exports skip it. If the auto-install fails (corporate firewall, sandboxed install), the manual download is at the LAME project's official site.

Save vs Export — The Most Confusing Gotcha

Audacity has two file outputs and they are not interchangeable.

File → Save Project writes a .aup3 file. This is Audacity's internal format — a SQLite database containing the audio data, edit history, track structure, and project metadata. Only Audacity can open .aup3 files. The advantage: you can re-open the project tomorrow and pick up exactly where you left off, with every edit intact.

File → Export Audio writes a standard audio file (MP3, WAV, FLAC, etc.). This is what you give to other software, upload to a podcast host, send to a friend, or set as a ringtone. Once exported, the project's edit history is gone — you have a flat audio file.

First-time users frequently click Save expecting an MP3 and end up with a .aup3 they cannot play in any other app. Always Export when you want a usable audio file. Save only when you intend to come back and edit further in Audacity.

Sample Rate Mismatch

Audacity has a "project rate" set in the bottom-left corner (defaults to 44100 Hz). When you import a file at a different rate (say a 48 kHz video soundtrack), Audacity does not automatically change the project rate. On export, the audio is resampled to the project rate, which can cause subtle pitch shifts or quality loss.

Two safe approaches:

• Set the project rate to match the source rate before importing. Bottom-left dropdown → set to 48000 if the source is 48 kHz.
• Or import the file, check the source rate (Tracks menu shows it), and update the project rate to match before exporting.

For typical music files (CD-rip MP3s at 44.1 kHz), the default 44100 Hz project rate matches the source and you can ignore this.

Common Cut Problems

The file is silent after I cut it. Most likely cause: you accidentally selected a silent region and trimmed to it. Cmd/Ctrl + Z to undo, then re-select with the audio visible. Less commonly: the export went to the wrong format and the player cannot decode it. Verify by opening the export in a different player.

The cut has a click or pop at the boundary. MP3 cuts at non-zero-crossing points produce clicks. Two fixes: (1) use Edit → Find Zero Crossings (Z key) to snap the selection edges to zero crossings before cutting; (2) apply a 5-10 ms fade with Effect → Fade In / Fade Out at the boundaries.

Audacity is slow to load my file. Long files (over 1 hour) take time to render the waveform. Audacity caches the waveform after first load, so subsequent opens of the same file are fast. For very long files, consider the browser tool /audio-cutter which uses streaming decoding and renders progressively.

The MP3 export sounds worse than the original. Audacity defaults to a re-encode on export, which incurs second-generation lossy loss. For a 192 kbps source re-encoded at 192 kbps the loss is inaudible; for a 128 kbps source re-encoded at 128 kbps you may hear it. Solutions: export at a higher bitrate than the source, or use a frame-aligned tool like mp3DirectCut for true bit-exact cuts. See how to trim mp3 without losing quality for the detailed analysis.

Frame-Accurate vs Frame-Aligned in Audacity

Audacity's standard cut path is a re-encode (Path 1 in trim mp3 without losing quality). This means you can cut at any sample, but the output is a fresh re-encode of the trimmed PCM.

The mp3 stream extensions for Audacity add frame-aligned cutting (Path 2), where the MP3 frames are passed through unchanged and the cut snaps to frame boundaries. This is genuinely lossless but requires the extension and snaps cuts to ~26 ms boundaries. For sample-precise cuts at high bitrate, the standard re-encode path is fine. For archival work where bit-exactness matters, install the extensions or use mp3DirectCut.

When the Browser Tool Is Just Faster

For a single cut on a single MP3, the time math is:

• Audacity: launch (5-10 s) + open file (5 s) + wait for waveform (5-30 s) + select + trim + export (5-15 s) ≈ 30-60 seconds total.
• /mp3-cutter: drag file in (instant) + waveform (1-3 s) + select + export (instant) ≈ 5-15 seconds total.

For a single cut, the browser is faster every time. For 5 cuts on the same file, Audacity wins because the file is loaded once and the cuts compound. The crossover is around 3 cuts on the same file.

For ringtones specifically, /ringtone-maker is purpose-built and beats both Audacity and a generic MP3 cutter on workflow speed. See how to make a ringtone from MP3 for the complete ringtone walkthrough.

The Audacity Verdict

Audacity is the right tool when the job has more than one step (cut + fade + normalize), when the job is multitrack, or when you are working on the same project across multiple sessions. It is overkill for single-cut MP3 trimming, where a browser tool like /audio-cutter or /mp3-cutter finishes the job in a fraction of the time without an install.

Match the tool to the job and skip the religious wars. For format-agnostic cutting see audio cutter; for the Audacity-equivalent compression workflow see how to compress audio in Audacity.