FFmpeg Audio Conversion Commands

FFmpeg audio conversion commands: Convert audio, extract sound from video, apply filters and inspect audio streams. Examples distinguish lossy encoding options from stream inspection. This guide explains what each command does, its syntax, practical examples, useful options, and common mistakes. Commands are shown for typical installations; flags can vary across operating-system and tool versions.

Before you start

Open a terminal appropriate for the operating system shown in the examples. Check that the required tool is installed and that you are running it with the permissions needed for your task. Replace sample names, paths, hostnames and IDs with values from your own environment.

Syntax at a glance

Square brackets usually indicate optional arguments, while uppercase words such as FILE, HOST and PACKAGE are placeholders that you replace. Keep quotes around paths or text that contains spaces. Commands should be tested on a safe sample before being used in production.

Quick command reference

Command syntax and examples explained

1. ffmpeg -i input.wav output.mp3

Purpose: Convert WAV audio to MP3.

Syntax

ffmpeg -i INPUT.wav OUTPUT.mp3

Example

ffmpeg -i interview.wav -c:a libmp3lame -b:a 192k interview.mp3

Options and notes: -b:a sets target bitrate; encoder availability depends on build.

MP3 is lossy; do not transcode repeatedly if quality matters.

2. -vn

Purpose: Ignore video streams.

Syntax

-vn INPUT OUTPUT

Example

ffmpeg -i clip.mp4 -vn -c:a aac audio.m4a

Options and notes: -ar sets sample rate; -ac sets output channel count.

Use this when a video file contains audio you want to extract.

3. -af

Purpose: Apply audio filters.

Syntax

-af FILTERS

Example

ffmpeg -i voice.wav -af loudnorm normalized.wav

Options and notes: Filters include volume, loudnorm, highpass and lowpass.

Listen to the result; extreme processing can introduce artifacts.

4. -ac

Purpose: Set output audio channel count.

Syntax

-ac CHANNELS

Example

ffmpeg -i stereo.wav -ac 1 mono.wav

Options and notes: -ar sets sample rate; -b:a sets bitrate for lossy encoders.

Downmixing to mono changes spatial information.

5. ffprobe

Purpose: Inspect audio codec, duration and channels.

Syntax

ffprobe -v error -show_streams INPUT

Example

ffprobe -v error -select_streams a -show_streams audio.mp3

Options and notes: -show_format reports container-level details; -of json formats output.

Inspect before conversion to avoid unexpected sample-rate or channel changes.

Common mistakes and troubleshooting

• Command not found: confirm the tool is installed and available on your PATH; open a new terminal after changing PATH.
• Permission denied: verify the current account, file permissions and target path. Use administrator/root privileges only when genuinely required.
• Unexpected output: check the command version, quoting, current directory and exact arguments. Consult the local help or manual for options supported by your build.
• Destructive operations: preview the target and keep a backup before deleting data, rewriting history, flashing a partition or changing system configuration.

Safety tips

Review every command before running it, especially commands that delete files, change permissions, flash firmware, alter a database or expose a network service. For network scanning and remote administration, work only on devices and systems you own or are authorized to test. Keep credentials, private keys, access tokens and log files private.

Frequently asked questions

Do these commands work on every system?

Not always. Some commands are specific to Windows, Linux, Android, a particular package manager or an installed tool version. Use the syntax shown for your platform and check local help when a flag is unavailable.

Can I copy and run every example exactly?

Use the examples as templates. Replace placeholders such as filenames, package IDs, hostnames and paths with your own values, and verify the effect before executing a command that changes data or system state.

Conclusion

Use this reference as a starting point, then confirm flags in the tool’s official help or manual for your installed version. A clear understanding of syntax, options and side effects makes command-line work more reliable.