Skip to content

Instantly share code, notes, and snippets.

@maximebories
Last active March 4, 2025 10:29
Show Gist options
  • Save maximebories/91d79c0ec25fd3f990615dcf355de8eb to your computer and use it in GitHub Desktop.
Save maximebories/91d79c0ec25fd3f990615dcf355de8eb to your computer and use it in GitHub Desktop.
FFmpeg command to convert webm to mp4 video files

WebM to MP4 using FFmpeg

This FFmpeg command converts a .webm video file to a standard .mp4 file using the libx264 codec for video, aac codec for audio, and a CRF value of 22. The preset is set to 'slow' for higher quality encoding, and the audio bitrate is set to 128 kbps.

If the input and output filenames don't contain spaces, quotation marks or other special characters:

ffmpeg -i input.webm -c:v libx264 -preset slow -crf 22 -c:a aac -b:a 128k output.mp4

Or escape spaces using backslashes

ffmpeg -i input\ with\ spaces.webm -c:v libx264 -preset slow -crf 22 -c:a aac -b:a 128k output\ with\ spaces.mp4

Or use quotation marks in any other cases:

ffmpeg -i "input with spaces.webm" -c:v libx264 -preset slow -crf 22 -c:a aac -b:a 128k "output with spaces.mp4"

Explanation:

-i input.webm: Specifies the input WebM file (use quotes or backslashes for spaces). -c:v libx264: Uses the libx264 encoder for video (widely compatible). -preset slow: Prioritizes quality over speed (consider 'medium' for faster encodes). -crf 22: Sets Constant Rate Factor (lower values mean higher quality, typically 18-28 is good). -c:a aac: Encodes audio with AAC (common and efficient). -b:a 128k: Sets audio bitrate to 128 kbps (adjust based on needs). output.mp4: Names the output MP4 file (use quotes or backslashes for spaces).

Alternatives & common values:

Video codec alternative to libx264:

  • libx265 (for even better compression, but may require more processing power)

Audio codec alternative to AAC and common bitrates:

  • libopus (modern, efficient codec) at 64k, 96k, 128k (for music), or even lower for speech-only content
  • mp3 (widely supported, but less efficient than AAC or Opus) at 128k, 192k, 256k

Potential enhancements:

1. Copying metadata:

ffmpeg -i "input with spaces.webm" -c:v libx264 -preset slow -crf 22 -c:a aac -b:a 128k -map_metadata 0 "output with spaces.mp4"

2. Scaling video (if needed):

# ffmpeg -i "input with spaces.webm" -vf scale=1280:-2 -c:v libx264 ... 

3. Hardware acceleration (if available):

# ffmpeg -hwaccel auto -i "input with spaces.webm" ... 

4. Two-pass encoding (for even better quality, but slower):

# ffmpeg -i "input with spaces.webm" -c:v libx264 -preset slow -crf 22 -pass 1 -f mp4 /dev/null
# ffmpeg -i "input with spaces.webm" -c:v libx264 -preset slow -crf 22 -pass 2 "output with spaces.mp4"

Remember:

  • Experiment with CRF and audio bitrate for your specific needs.
  • Consider hardware acceleration for faster encodes on supported systems.
  • Two-pass encoding offers the best quality but takes longer.
@Nour-MK
Copy link

Nour-MK commented Apr 15, 2024

note that there must not be spaces in the name of the .webm file to be converted. it causes the command to fail.

@StipJey
Copy link

StipJey commented Apr 25, 2024

Respect, bro!

@bdhowell
Copy link

bdhowell commented Sep 7, 2024

You can always enclose Unix filenames in quotes. That should solve Nour-MK's problem.

@kasir-barati
Copy link

kasir-barati commented Sep 21, 2024

Convert webm to mp4

This worked really well for me: ffmpeg -i screen-capture.webm -c:v copy -c:a aac -b:a 128k output.mp4.

Merge 2+ mp4 files together with ffmpeg

BTW if you also wanted to concat two or more mp4 files you can do the following:

  1. Create a text file called inputs.txt.

  2. Use file command + each mp4 file path. E.g.

    file '/home/userName/first.mp4'
    file '/home/userName/second.mp4'
    

    Remember that the order here matters. In this example it will append the second.mp4 to first.mp4.

  3. cd to where this inputs.txt is located and execute this command:

    ffmpeg -f concat -safe 0 -i inputs.txt -c copy output.mp4
    

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment