🌐
Reddit
reddit.com › r/ffmpeg › sorry for being stupid, but can someone help me get ffmpeg to work?
r/ffmpeg on Reddit: Sorry for being stupid, but can someone help me get FFmpeg to work?
July 11, 2022 -

As an introduction, please know that I have no idea what I'm doing. I don't know the first thing about computer science or coding or anything, I just got ytarchive and need to mux the .ts files it spits out.

I'm on windows 10, if that matters. I downloaded the second download link from gyan , the one called "ffmpeg-git-full.7z" . It downloaded fine, extracted fine, and it's got 3 .exe files in a folder called "bin" , but not a one does anything. If I spam click them fast enough, I can see the outline of a new window pop up for like a tenth of a second, but that's it. I tried running as admin, and aside from asking if I wanna let it make changes to my computer, it's the exact same.

I have no idea what to do. Any help you could offer would be super appreciated. Including suggestions of easier, more idiotproof programs to use, maybe.

Top answer
1 of 5
4
ffmpeg is command line program and does not have a graphical UI. If you're not prepared to use command line (google command line if you dont know what it is) you should use something equivalent but with a GUI. There are programs out there that act as a front end for ffmpeg. My favorite is staxrip. Nice UI on it.
2 of 5
3
Here's how you can dip your toes in: Create a new folder on your desktop. Drop FFMPEG.exe into that folder. Drop a sample movie file you'd like to play with into the folder. I would normally say to shift-right-click an empty spot in the folder to open a Windows Command Line prompt, but these days, that option is replaced with PowerShell, which is tedious. So instead, Open Notepad and type CMD. Save the file as Open_commandline.bat in the folder. Now, double-clicking that batch file will open a windows command prompt for you. Now, in that command prompt, you can try invoking FFMPEG to do something to the file. A typical commandline would be something like ffmpeg -y -i MYTESTFILE.MP4 -c:v libx264 -c:a copy MYNEWFILE.MOV This takes your input .MP4 file and converts it to H.264 video in a QuickTime .MOV container. Of course, FFMPEG can do a lot of other things, like resizing the video, cropping the video frame down, trimming the timeline down, changing the framerate, adding/removing tracks, etc. Using commandline apps like this is a bit of a learning curve, but it can be very rewarding, since you can create batch scripts to do things quickly and efficiently without having to click all over the place.
🌐
Reddit
reddit.com › r/ffmpeg › novice here, what are the things you can do using ffmpeg?
r/ffmpeg on Reddit: Novice here, what are the things you can do using ffmpeg?
December 23, 2024 - Usually you have to choose between speed, quality, and file size (two of the three). Each encoder has its pros and cons. ... Do you knowbthat mkv and mp4 are just containers and you can convert it very fast without reencoding video and audio? Like ffmpeg -i inputfile -c:v copy -c:a copy outputfile
🌐
Reddit
reddit.com › r/ffmpeg › best way to learn ffmpeg?
r/ffmpeg on Reddit: Best way to learn ffmpeg?
October 29, 2023 -

Can you recommend a way to learn many things about ffmpeg?

🌐
Reddit
reddit.com › r/videoediting › folks, if you haven’t used it, start doing so. ffmpeg is great software.
r/VideoEditing on Reddit: Folks, if you haven’t used it, start doing so. FFMPEG is great software.
September 29, 2021 -

I’ve known about it for years, and was finally in a place where I HAD to use it - (needed footage from a Samsung phone, it was recorded at a variable frame rate and wouldn’t sync with my other footage)

I think I was always intimidated by its lack of GUI (I’m aware there are paid versions for this) but it really wasn’t hard. Just converted 6 files in terminal and they came out great.

Don’t fear the FFMPEG!

🌐
Reddit
reddit.com › r/programming › introduction to ffmpeg
r/programming on Reddit: Introduction to FFmpeg
January 13, 2025 - I've made a video to gif converter using React, ffmpeg.wasm, Framer Motion and After Effects ! ... How To Use FFMPEG On Linux.
🌐
Reddit
reddit.com › r/ffmpeg › what’s your go-to ffmpeg trick or workflow? share your tips!
r/ffmpeg on Reddit: What’s your go-to ffmpeg trick or workflow? Share your tips!
August 14, 2025 -

I’m collecting practical, real-world ffmpeg moves that save time or fix messy media. What do you use?

Simple daily commands I actually use

These are small, reliable lines I reach for every day. Sometimes I stack more advanced filters/encoders, but this set covers a lot of real-world tasks fast.

# Convert M4A to MP3 (VBR ~190 kbps).
ffmpeg -i song.m4a -codec:a libmp3lame -qscale:a 2 song.mp3


# Loop a short .mov several times without re-encoding (fast remux).
ffmpeg -stream_loop 4 -i 1.mov -c copy looped_1.mov


# Remux MP4 to MOV with no quality change. Useful for NLE/project needs.
ffmpeg -i vid.mp4 -c copy vid.mov


# Resize an image to exactly 512×512. (Fixed size; will distort if aspect differs.)
ffmpeg -i img.png -vf "scale=512:512" resized_img.png


# Turn a static image + audio into a video.
ffmpeg -loop 1 -i img.png -i song.wav -c:v libx264 -tune stillimage -c:a aac -b:a 192k -shortest -movflags +faststart video.mp4


# Extract best-quality MP3 from a video file (audio-only output).
ffmpeg -i voiceover.mp4 -q:a 0 -map a voiceover.mp3


# Resize wide to 3000 px, keep aspect; write compact PNG without alpha.
# Note: PNG -compression_level caps at 9; 10 behaves like 9.
ffmpeg -i img.png -vf "scale=3000:-1" -compression_level 10 -pix_fmt rgb24 compressed_img.png


# Upscale a small thumbnail to 1280×720 for a quick 16:9 placeholder.
ffmpeg -i thumb_small.png -vf "scale=1280:720" thumb_resized.png

If you’ve got cleaner flags or better defaults for these basics, I’m all ears. For heavier jobs (denoise/deband, loudness targets, hardware AV1/HEVC, HLS/DASH packaging), I switch to longer chains.

My setup:

OS: macOS 15.5
CPU/GPU: Apple M1 Pro
Install: Homebrew
Shell: zsh
ffmpeg Version: 7.1.1 built with Apple clang version 17.0.0

Find elsewhere
🌐
Reddit
reddit.com › r/commandline › learning how to use ffmpeg
r/commandline on Reddit: Learning how to use FFMPEG
April 22, 2016 -

Hi, I do a little bit of casual video editing in FCPX and I'd like to start putting these videos in WebM format. It doesn't seem like Compressor supports this, so I'm looking at alternatives, namely ffmpeg.

I've tried to use ffmpeg in the past, but always find the gazillion arguments and such that must be used to be overwhelming. This is probably because I'm a command line newb.

If anyone could point me to resources or give me tips on learning to use ffmpeg from the CLI, I'd appreciate it.

🌐
Reddit
reddit.com › r › editors › wiki › ffmpeg
links for film and video editors - people who make their living in the field.
December 11, 2017 - As such it's a remarkably flexible tool, and a great thing to have in your back pocket, even in the professional realm. A pre-built package of FFmpeg typically contains three programs: ffmpeg, ffplay, and ffprobe. ffmpeg is the core of the unit, and the only program you actually need. ffplay is a simple player that can be used to quickly preview files, especially those which don't play with other players or editors.
🌐
Reddit
reddit.com › r/ffmpeg › can i install ffmpeg with a single click?
r/ffmpeg on Reddit: can i install FFmpeg with a single click?
April 15, 2023 -

i want to use FFmpeg because APNG's are the most obscure file type and i can almost cant find any program that supports it apart from FFmpeg
sadly all documentation regarding the installation assumes any prior knowledge regarding windows command prompt and something called PATH (system variables??)
does an easy install exist? or is this just to gatekeep the software to keep simple folk out?

i'm really confused why the install seems to be so complicated

Top answer
1 of 14
7
To be blunt, if you're not happy to play around with the command line, environment variables, etc (or at least willing to learn), you're going to have a very hard time with FFMPEG. You can download the ffmpeg.exe file and put it somewhere, but you'll still have to figure out how to cd to that folder, run FFMPEG with arguments, bring your source files in, etc. Environment variables are just small useful bits of data that your computer stores. The PATH environment variable contains a list of folders where the OS should be looking for programs - you need to add whichever folder you put FFMPEG into that list in order for your computer to be able to see it, and run it from anywhere. FFMPEG isn't designed to be a user-friendly, one-click solution. It's a command-line scripting tool that is mainly used under the hood as part of other software, or by people with a fair amount of technical experience to automate. That said, googling "install ffmpeg windows" brings up about five different guides that give you very clear instructions. Alternatively, a quick query of ChatGPT also gave me a nice step-by-step guide.
2 of 14
4
FFmpeg is a command line utility. If you want to use it, you'll either have to familiarize yourself with it (there are lots and lots of free ressources out there) or you have to find a GUI wrapper for FFmpeg. The command line has a bit of a learning curve but it's very powerful once you figure it out. or is this just to gatekeep the software to keep simple folk out? What? Even “simple folk” can follow a five-step guide with pictures . You could also invoke the FFmpeg executable directly, that way you don't need to add it to the PATH environment variable our you could put it in a directory that is already part of PATH.
🌐
Reddit
reddit.com › r/youtubedl › where to download and how to apply ffmpeg
r/youtubedl on Reddit: where to download and how to apply ffmpeg
August 15, 2024 -

id like to extract the audio or download mp4 from videos, though im not sure where to get ffmpeg and then where to put it , and then how to write its location in command prompt. can someone link a video or explain the most basic way to do this to get audio? thanks in advance your the best

🌐
Reddit
reddit.com › r › ffmpeg
r/ffmpeg
April 7, 2011 - I'm trying to convert a video into a gif I can use inside of Discord, is there a way I can convert a short video into a gif without a significant drop in quality? ... I made it in 2 weeks in python and customtkinter it setups ffmpeg in first setup Github Release: download Source code: Link ...
🌐
Reddit
reddit.com › r/ffmpeg › is there a recommended ffmpeg command cookbook with common / high quality scripts?
r/ffmpeg on Reddit: Is there a recommended ffmpeg command cookbook with common / high quality scripts?
January 24, 2022 -

Hello all!

I saw a post here for Best command line for compressing to x265?

And one of the comments said that this script is best: ffmpeg -i input.mp4 -c:v libx265 -crf 25 -preset fast -pix_fmt yuv420p10le -c:a libopus -b:a 96k output.mkv

I have a few questions:

  1. i just feel like I am walking in the dark and don't know where or how I can learn they 'why' is this faster, or better - without learning the deep workings of ffmpeg. Are there any resources where I can learn this?

  2. Does anyone know if there are any 'cookbooks' of high quality / common ffmpeg commands which is reputable? I'm sure I can find some scripts online, but I do not know what is 'a good recipe' and 'a bad recipe'.

Thanks!

🌐
Reddit
reddit.com › r/ffmpeg › a simple beginner's guide to high quality video compression using ffmpeg
r/ffmpeg on Reddit: A simple Beginner's guide to high quality video compression using FFmpeg
November 14, 2025 -

How to use FFmpeg for Video Compression

Settings:

1. Video Codec: x265 (libx265) {or} if you want it even smaller and can wait a lot, you can use AV1 (libsvtav1) with CRF 28-32, but it's much slower and less widely supported.

2. Quality mode: CRF 18 (visually nearly identical), (CRF 18-22 For visually lossless qualities.) {Lower CRF = better quality + Larger file; and vice versa}

3. Speed preset: “veryslow” (smallest file, very long encode) (can also change to "slow" or “medium”, but remember - the slower the process, the smaller the output)

4. Container (output video): ".mkv" - best for encoding and most stable and safest, usually not compatible with old TVs and few devices and some video editors. {or} ".mp4" - can fail on longer files, much stricter format, doesn't support some audio formats, can corrupt easily if the encode is interrupted, But Much better compatibility than .mkv.

Best option, imo, is encode the video in .mkv format for the output, then you can change the format to .mp4 later if absolutely needed.

5. Audio: AAC 128 kb/s is fine (but I recommend not to touch it and copy it as it is).

 

Downloading ffmpeg:

1.      Use the following link: https://www.gyan.dev/ffmpeg/builds/

2.      In the sections, go to “release builds”

3.      Download the latest version of the full static file named “ffmpeg-release-full.7z”

4.      Extract the file to where you want it to be.

5.       You will see a license, readme.txt and 3 folders.

6.      Open bin folder and you should see 3 applications.

a. ffmpeg.exe

b. ffplay.exe

c. ffprobe.exe

7.      On Windows, press Win+ S and search “Edit the system Variables” alternatively, you can right click on “my pc” and go to “Advanced system setting”

8.      Make sure you’re logged in as administrator. In the Advanced Tab, find “Environment Variables” button, usually located in the bottom right hand side.

9.      In System variables, find Path and double click on it.

10.  Press “New” and then “Browse…” then find the “bin” folder, select and add it.

11.  Press “ok” and we’re ready.

Starting the Codec:

  1. Locate the folder of the video that you want to compress. If the video is on the desktop and not in any folder, open file explorer and go to Desktop where the video is.

2.  Hold shift, and right-mouse click an empty space in the folder, then press “open PowerShell window here” or “open command Prompt here”.

3.  Using the settings:

a. libx265

b. maximum compression – “veryslow”

c. CRF 18

d. Copy audio (-c:a copy)

Use this exact command: ffmpeg -i "[Video File name that you want to compress]” -c:v libx265 -preset veryslow -crf 18 -c:a copy "[Result_File_name.mkv]"

For example: ffmpeg -i "yourfile.mp4" -c:v libx265 -preset veryslow -crf 18 -c:a copy "output_compressed.mkv"

4. If you’re getting an error like “No such file or directory”, instead of opening the PowerShell window by right clicking, you can go the address bar of the folder the video is in and type “cmd” there. Then a command prompt will open and you can paste the above-mentioned command line there and the process should start.

5. If you want to compress the audio as-well, instead of (-c:a copy), use (-c:a aac -b:a 128k) so the final command would look something like this: ffmpeg -i "input.mp4" -c:v libx265 -preset veryslow -crf 18 -c:a aac -b:a 128k "output.mkv"

6.  When you run the command, you will see a line that would look something like this: "frame= 292 fps=1.1 q=24.1 size= 2560KiB time=00:00:09.66 bitrate=2169.5kbits/s speed=0.0381x elapsed=0:04:13.92"

This is what it means:

a. Frame = how many frames have been processed thus far.

b. Fps = What rate it is encoding at.

c. q = internal quality variable.

d. size = What the size of the output file is thus far.

e. Time = How much of your video has been encoded so far.

f. Bitrate = current average bitrate.

g. Speed = 0.038x means the encoding is 3.8% of real-time speed.

h. Elapsed = How much time you have spent.

7.   It’s very important that you don’t stop this process or switch off your pc or put it to sleep as it will cancel the whole process and you’ll have to start from the beginning.

 

Converting from .mkv to .mp4

1.      After the encode is done, if you really need .mp4, paste this command in the command prompt: ffmpeg -i [Output file name.mkv] -c copy [New_Output.mp4]

2.      For [Output file name.mkv], use the name of the real output file that was the result of the codec.

3.      And for [New_Output.mp4], Type in what your video should be name + “.mp4” just like in the command above.

4.      Can also be used in the opposite direction.

5.      This process will be much faster and will take only a few seconds since it’s just remuxing.

Disclaimer

I am in no way, shape or form an expert in using ffmpeg. This method may not be the best but this is the method I use and I find satisfactory results. If there’s a better way, please feel free to share and correct me where I am wrong. I am only a student there’s still a lot that I have to learn.

 

Top answer
1 of 2
5
ffmpeg has quickly become one of my favorite tools because it’s so flexible. AME is my usual tool because it’s easy and fast and does most of the things one could want. But when you have problems: corrupt frames, unusual codecs, ffmpeg usually has it covered. It saved me just earlier this week on a file converting a corrupt VOB that Handbrake and AME couldn’t read. The one big drawback that keeps me from always using it is batch conversions. Bash isn’t terrible to program but it’s usually more hassle to convert, say, a bunch of camera files to H.264 dailies in ffmpeg than something else. It’s not the program for everything, but well worth knowing how to use. It also has some great synergy with programs like youtube-dl (download and convert most videos from the web) and cron (setup watch folders that automatically transcode files).
2 of 2
1
How is it any different/better than say, AME? It's an open source tool that wasn't originally developed with professional applications in mind. It was originally configured to deal with a lot of amateur and consumer formats, so this meant analog TV captures, digital TV captures, DVDs, VCDs, video games, and so on. To work with all these different formats (and I mean, seriously, look at the length of that list!) it had to be very flexible. That meant being able to deal with interlacing, telecine, a wide variety of frame rates, resolutions, chroma subsampling, bit depths, and color spaces, and non-compliant signals. As a result it can basically handle any thing you throw at it, partially because it was open source. "OK, SpamKing696969, you want to be able to transcode RoQ files from Quake Ⅲ, then add the code!" There was nobody to say "no," and nobody had any reason to say "no." How does the project suffer from being able to encode/decode one more format? It doesn't! At the same time, how does the project suffer from having old legacy formats supported? As long as the code doesn't interact with something else and cause an unintended malfunction, it doesn't. And that's how you wind up with the fact that ffmpeg can still handle Intel Indeo 2, but nothing else can. Another fun thing about it being open source means it can run almost anywhere and on almost anything. Windows, Linux, OS X macOS, you could probably compile it to run on a BeBox , an SGI Octane , or an Amiga 4000 , if you had the right compiler, enough patience, and weren't depending on any hardware-specific code. So basically all this put together means it can handle almost anything at almost any time on almost any machine. Since the project became more mature, that is more fully developed, it's cast its eyes towards not just supporting everything under the sun, but doing everything as best as possible. So that meant implementing better deinterlacing algorithms, even if they are obtusely complicated and unrealistically slow, better scaling algorithms, even if only a handful of people understand how to work them, and supporting the newest standards. So when H.264 started to hit consumers, ffmpeg was one of the first free consumer pieces of software that could encode it. If you wanted to put your own videos on your 5G iPod , instead of buying them off iTunes, you needed ffmpeg. Now, as you can guess this takes a lot of effort, to build your own implementation of a codec, and sometimes they just don't. They often borrow the efforts of other open source codec implementations by adding support for those libraries. So ffmpeg developers went off and built a way to use the x264 encoding library into their own system. They did the same thing with x265 , NVENC SDK , AMF SDK , Intel Media SDK , and Google's efforts with libvpx ( VP8 / VP9 ). So ffmpeg in many areas benefits from the expertise of others, bringing it together in a single, flexible tool that we don't have to build from scratch ourselves. And this is great, because as x265 becomes a better H.265 encoder, ffmpeg benefits by just having the user install the latest version of their libraries. This is extremely common practice among open source software developers, and even closed source developers too! Go pop open the licenses page on a game console, I promise you'll see libjpeg and libtiff acknowledged. Huge swaths of Linux software are built on toolkits from Gnome, KDE, and even stuff originally developed for GIMP . Adobe Media Encoder, however, is built as a professional tool, for professional use with professional formats, and as such does not support a lot of more consumer-y things. If Adobe really wanted to they could borrow bits and pieces of ffmpeg, however that might make for some legally questionable situations for them (especially regarding software patents). Or Handbrake? OK, this is where things get fun. Remember how I said ffmpeg was built on different libraries produced by other developers? And how parts of Linux programs are built on libraries from Gnome, KDE, and GIMP? That happened because they compartmentalized off the components they were using into libraries that others could borrow for their own use. Well ffmpeg did the same thing, and it's comprised of three major components: ffmpeg (the program you execute), libavcodec (the encoding/decoding libraries developed by ffmpeg contributors) and libavformat (AKA "Lavf", the reading/writing libraries for different container files). So any developer that wants to can go in and borrow those libraries for use in their own project (as long as they comply with the LGPL 2.1 and GPL 2.0 licensing stipulations . And that's what the Handbrake guys did. They borrowed libavcodec (and I think libavformat too) and use it as their primary decoding library, and encoder for MPEG-4 and MPEG-2 , and relying on x264, x265, and libvpx for H.264, H.265, VP8, and VP9 respectively (just like ffmpeg largely does). IIRC it also borrows bits and pieces from ffmpeg development for scaling and filtering, and for all its audio and subtitle codecs as well (except on OS X macOS where it uses Core Audio for AAC .
🌐
Reddit
reddit.com › r/ffmpeg › [deleted by user]
How to really install ffmpeg
December 15, 2020 - Your advice made it so that (hopefully) I'll never have to struggle like that again, so thanks very much! ... Thank you for your help. Instructions clear, dick still in pants. ... Thank you I love you! ... This is awesome, dude. Your steps were very straightforward and concise. This should be the gold standard of documentation! ... Where did you download ffmpeg? Use gyans website to download ffmpeg - here.