You need to edit audio and the app menu is empty
You just recorded a voice memo on your Fedora laptop and need to trim the silence, lower the background hum, and export it as a clean WAV file. You open the application menu and Audacity is not there. You visit the official website, download a Windows installer or a Debian package, and realize you are looking at the wrong distribution. Fedora ships Audacity in its official repositories. You do not need third-party binaries. You just need to point the package manager at the right repository and let it handle the dependencies.
How Fedora packages audio software
Fedora treats audio applications as first-class citizens. The system ships with PipeWire as the default audio server since Fedora 34. PipeWire replaces PulseAudio and JACK, handling low-latency professional audio and desktop playback in a single daemon. When you install Audacity through dnf, the package manager pulls the RPM built specifically for your Fedora release. It links against the system libraries, respects your desktop environment theming, and automatically registers with PipeWire for device access.
Downloading a standalone binary from the Audacity website bypasses the package manager. You lose automatic updates, you break desktop integration, and you force the application to bundle its own libraries. That creates conflicts when the system updates its audio stack. Stick to the repository package. It stays in sync with the rest of your system.
Audacity projects are not single files. They are directories containing a .aup3 project file alongside a _data folder with uncompressed audio chunks. This design lets you edit non-destructively. Every cut, fade, or effect leaves the original waveform intact. You can undo changes indefinitely until you export. Keep your project folders in a dedicated directory. Do not scatter them across the desktop.
Install and launch Audacity
Open a terminal and run the installation command. The package manager will resolve dependencies like libsndfile, portaudio, and the PipeWire libraries.
sudo dnf install audacity
# --setopt=install_weak_deps=False skips optional codecs if you only need WAV/FLAC
# dnf pulls the exact version matched to your Fedora release
# The transaction installs the binary, desktop file, and shared libraries
audacity
# Launches the GUI directly from the terminal
# Keep the terminal open to catch any startup warnings
If you prefer a graphical interface, search for Audacity in your application launcher. The terminal launch is useful for the first run because it surfaces missing codec warnings immediately. Fedora's package manager tracks the exact build metadata. You can verify the package origin at any time with rpm -qi audacity. The output shows the release number, architecture, and repository source. Trust the package manager. Manual file edits drift, snapshots stay.
Verify the installation and audio routing
Audacity will open to a blank project. Before you record, check that the application sees your hardware. Open the Edit menu, select Preferences, and navigate to Devices. The Host API should list PipeWire or ALSA. Select your microphone and speakers from the dropdown menus.
Run a quick test to confirm the signal path works end-to-end.
pactl list short sources
# Lists all active audio input sources recognized by PipeWire
# Look for your built-in mic or USB audio interface
audacity --check-version
# Prints the installed version and build metadata
# Confirms you are running the repository package, not a flatpak or snap
Record a ten-second clip. Play it back. If you hear your voice clearly with no crackling, the routing is correct. If the recording is silent or distorted, check the input volume slider in the system sound settings. PipeWire does not apply system-wide input gain by default. You must raise the source volume in the desktop sound panel or use pactl set-source-volume.
Sample rate mismatches cause subtle playback issues. Audacity defaults to 44100 Hz. If your hardware interface runs at 48000 Hz, you will hear pitch shifts or stuttering during playback. Open Preferences, go to Quality, and match the Project Rate to your hardware. Save the setting as the default. Run journalctl -xeu pipewire.service if the device disappears after a suspend cycle. The log will show whether udev dropped the USB audio rule.
Common pitfalls and what the error looks like
New users hit three specific walls when starting with Audacity on Fedora.
The first wall is missing export formats. Audacity ships with FLAC and WAV support out of the box. MP3 and OGG export require external codecs. If you try to export as MP3 and see Error: Audacity requires the LAME MP3 encoder to export MP3 files, you need to install the codec package.
sudo dnf install lame ffmpeg
# lame provides the MP3 encoder Audacity expects
# ffmpeg adds support for AAC, OGG, and container formats
# Restart Audacity after installation to load the new plugins
The second wall is plugin placement. Audacity supports VST, LV2, and LADSPA plugins. Fedora does not install third-party audio plugins by default. When you download a plugin, place VST2 files in ~/.vst/ or /usr/lib/vst/. Place LV2 plugins in ~/.lv2/ or /usr/lib/lv2/. Audacity scans these directories on startup. Never drop plugins into /usr/lib/audacity/. That directory belongs to the package manager and will be overwritten on the next update.
The third wall is latency and buffer size. If your recording sounds choppy or your CPU spikes to one hundred percent, your buffer size is too low. Open Preferences, go to Quality, and set the Buffer size to 1024 or 2048. Lower numbers reduce latency but increase CPU load. Higher numbers stabilize performance on older hardware.
Configuration files for audio routing live in ~/.config/pipewire/ or /etc/pipewire/. User modifications belong in the home directory. System-wide defaults ship in /usr/lib/pipewire/. Edit the user directory. Never touch /usr/lib/. When troubleshooting silent outputs or missing devices, run journalctl -xeu pipewire.service. The x flag adds explanatory context and the e flag jumps to the end of the log. Most routing failures show up as permission denials or missing udev rules. Read the actual error before disabling services.
When to use Audacity versus other tools
Use Audacity when you need a straightforward waveform editor for podcasts, voiceovers, or quick track cleanup. Use Ardour when you are recording multi-track instruments and need a full digital audio workstation with MIDI routing. Use Ocenaudio when you want a lightweight, single-file editor that opens instantly without a project system. Use command-line tools like sox or ffmpeg when you are scripting batch conversions or processing audio in headless servers. Stay on the repository package if you want automatic security updates and seamless PipeWire integration.