Table of Contents Show
For those who don’t know the tool: Audacity is a free, open-source desktop audio editor developed by the Audacity Team in the wider Muse Group ecosystem. In production, it usually sits beside an NLE, finishing system or full DAW rather than replacing one: export audio, make a fast cut, cleanup, normalisation or compression pass, then hand the rendered file back downstream. Optional FFmpeg support broadens import and export coverage, while VST3, LV2 on Linux and Audio Units on macOS give it useful plug-in reach for editorial, dialogue, podcast and utility audio work.
We keep Audacity installed for a simple reason: when one piece of audio needs five minutes of attention, installing & opening a full DAW can feel like deploying a crane to move a chair. Trim a line, remove a click, normalise a file, put a compressor over a track, export it and move on. Audacity has been exceptionally good at that unglamorous job for years, and it costs nothing. The problem was that its speed increasingly came with an interface and editing model that felt older than the workstation around it.
Audacity 4 is interesting precisely because it does not abandon that role. The application remains a desktop audio editor and recorder, but the interface has been rebuilt on Qt and the clip-editing model has been substantially reworked. For the quick utility jobs that keep Audacity permanently installed on many production machines, that is a more consequential change than a new coat of paint.
The tool modes are gone
The most immediately obvious change is also one of the cleanest. Audacity 4 removes the separate Select, Envelope, Draw and Multi-tool modes. Their functions become contextual instead of requiring a mode switch.
Direct sample editing is a good example. Zoom into the waveform until individual samples are visible and sample drawing becomes available automatically. Volume envelopes appear through the clip-gain workflow rather than through a dedicated Envelope tool. Splitting now has its own temporary tool, activated with the S key, instead of being buried inside a general-purpose mode
Clips behave more like editorial objects
Clips can now be selected directly from their headers, with Shift-click used to build a multiple selection. Once several clips are selected, moving, trimming and time-stretching can apply to the whole selection. Clips can also be grouped so they stay together when moved, copied, pasted or duplicated.
That gives Audacity a more coherent object model for the kind of small editorial assemblies that previously became fiddly very quickly. A dialogue pickup, room tone, sting and tail can be handled as related material without pretending the application has suddenly become a full post-production DAW.
There is an important detail in how clips interact. Audacity 4 lets you move a clip over existing material instead of simply blocking the move. According to the release notes, the overlapped part of the existing clip is replaced. That is useful, but it is not the same thing as a DAW with automatic layered lanes or hidden comp material. Anyone expecting sophisticated overlap management should test the exact behaviour before using it on irreplaceable edits.
Alignment guides, sample-boundary snapping and per-project snap settings round out the new clip model. None is glamorous. All are the sort of thing that makes an audio editor feel fast after the first hundred cuts.
Sync-Lock leaves, ripple editing arrives
Audacity 3’s Sync-Lock is gone. The replacement is a combination of clip grouping and explicit ripple-style edit commands that either leave a gap or move later material to preserve timing.
That distinction is healthier for editorial work because the consequence is attached to the operation rather than to a persistent global state that can be forgotten. Delete one section and leave time intact, or delete and close the gap. Paste normally, or paste while preserving synchronisation across tracks. The intent is visible in the command rather than hiding behind a lock state somewhere else in the interface.
For simple two-track edits this may feel like semantics. For longer voice, podcast or temp-mix sessions it can reduce the classic problem where one forgotten mode changes the timing of material you were not looking at. The price is retraining: users who relied on Sync-Lock as an always-on safety rail need to learn the new ripple commands and grouping logic.
The project format is a real migration boundary
Audacity 4 introduces a new .aup4 project format. Existing .aup3 projects from Audacity 3 can be opened and converted without modifying the original file, but the converted project cannot be saved back to .aup3. Older .aup projects can also be imported.
That makes the upgrade safer than an in-place destructive conversion, but it is still a one-way project-format transition. A facility with shared utility stations should therefore avoid a casual mixed-version deployment where one operator opens a project in Audacity 4 and another expects to continue editing the converted project in Audacity 3.
Plug-ins move forward, and sideways
Audacity 4 supports VST3 and Nyquist plug-ins across platforms, LV2 on Linux and Audio Units on macOS. The release can also generate controls when a plug-in’s own interface is unavailable. MuseHub content can be browsed from the application’s Get Effects path, with compatible effects placed into the same effect chain as Audacity’s built-in processing.
There is also a compatibility subtraction. VAMP and LADSPA plug-in hosting are not available in Audacity 4.0. That matters more than the shiny VST3 headline if a workstation depends on a specific legacy analysis or processing plug-in.
Do not uninstall Audacity 3 yet
The first stable Audacity 4 release does not reproduce every Audacity 3 feature. The official release notes list Time Tracks, Note/MIDI tracks, Mixer, Macro Manager and the scripting pipe, VAMP and LADSPA hosting, and Play-at-speed as unavailable in 4.0. The team also says some exporting and rendering features, analyzers and effects are still missing.
The missing Macro Manager and scripting pipe are especially important for facilities that use Audacity as an automated utility rather than a hand-driven editor. A GUI refresh is irrelevant if the script that batch-processes a folder no longer has its execution path. Likewise, users with legacy plug-in dependencies should verify their actual chain rather than reading “VST3” and assuming universal compatibility.
Current downloads are available for Windows on x86_64 and ARM64, macOS as a Universal build for Apple Silicon and Intel, and Linux as x86_64 and ARM64 AppImages. Audacity remains free and open source under the GNU GPLv3. The direct download remains available, so the application has not turned into a subscription-shaped trap while nobody was looking.
For our usual “quickly cut this, normalise that, compress this voice and get back to the timeline” jobs, Audacity 4 is exactly the kind of update we wanted: less modal, more coherent, still fast, still free. The new project format and the missing legacy features mean it deserves a controlled rollout rather than an automatic fleet-wide replacement, but the everyday editor finally looks and behaves much closer to the speed of the jobs we use it for.
https://www.audacityteam.org/audacity-4/
https://github.com/audacity/audacity/releases
https://github.com/audacity/audacity/releases/tag/Audacity-4.0.0
| Product | Audacity 4 |
| Developer | Audacity Team |
| Version | 4.0.0 |
| Release status | Alpha 1 |
| Platforms | Windows x86_64/ARM64 installers; macOS Universal for Apple Silicon/Intel; Linux x86_64/ARM64 AppImages |
| Project format | .aup4; .aup3 converts without modifying the original; no save-back to .aup3; older .aup imports |
| Plug-ins | VST3 and Nyquist; LV2 on Linux; Audio Units on macOS |
| Windows audio | ASIO playback and recording in official builds |
| Licence | GNU GPLv3 |
| Pricing | Free |
| Download | Official download |
