I have no issue with people sharing LLM generated tools if they actually work, even if they're 100% LLM generated and the poster has just validated that they work, but with just a quick glance I can see many issues with this that indicate you haven't tested it or even bothered to read the handful of words on the page:

- The target file size option on the compression tab just changes the bitrate without any consideration for the length of the video. This is immediately visible if you either test the command, if you're aware of what bitrate is, or if you even bother to read the LLM generated code in which there's a comment that says "Assuming 60 second video".

- The resolution options do not allow for anything other than 16:9, you can set one parameter to -1 (or -n for a multiple of n) to make it work with any aspect ratio. I can maybe see a person clumsily missing this one.

- There is no such thing as a "wav" encoder in ffmpeg. This is again immediately obvious if you test the generated commands as ffmpeg will print an error message and not produce an output file.

- Why does the command for "video compression" (which it isn't) in the FAQ not match the command generated by the tool?

This is dangerously oversimplified. It takes no account of source files with multiple tracks, so you'll probably end up accidentally throwing some away.

The "quality" slider implies that if you move it to the right, you'll get more quality. But higher numbers of the crf value are lower quality, not higher.

The resize function takes no account of the original aspect ratio of the source video, so you'll probably squash things.

Audio extraction ignores whatever the source codec is, missing the opportunity of extracting the source codec without recompressing. Additionally the built-in "aac" codec is very low quality and should not be used. ("libflac" is probably a better choice than "flac", too.)

Look great, a few nits:

- For the convert page, the tool seems to conflate codec and container format. For example, for MKV option, the tool specifies libx264, when MKV is capable of many more codecs. In addition, a lot of the times when people want to "convert", e.g. from MP4 to MKV, they mean to remux - i.e. "-c copy", which doesn't seem like an option here.

- For the compress page, the tool allows you to specify the target size, however the command output limits bitrate instead of target size. This means that the output size will vary depending on how long the input is, and will almost never be the specified target size.

I would suggest merge the "Convert" and "Compress" tabs, and allow specifying:

- video bitrate (-b:v)

- video codec (-c:v)

- audio bitrate (-b:a)

- audio codec (-c:a)

- container format

I found handbrake to be a good GUI-based alternative if ffmpeg commands are overwhelming.

AI has been pretty solid with ffmpeg commands

Why build "pages" with so much overhead though? Let alone with so many mistakes (as other pointed them out). It could be simple github readme or even just gist

I have to say, I used to have a similar cheat sheet, but Claude has totally solved this problem for me.

Way more than that, in fact... I had a bunch of 20-year-old 8mm film transfers on DV, where the scanner had put white-on-black titles between the reels. Claude wrote me a script combining ffmpeg and other tools that not only converted the format from DV to MP4, but found the interstitial titles, did OCR on them, regenerated them in full resolution, replaced the original titles with the new ones, and rendered the result as one file per reel.

These pages need to take input file into account to provide better flags. Maybe what you want is a page that generates shell scripts.

+ Compress to target needs to know input length, as others have mentioned. Also, usually I would encode in multiple passes to better allocate the bits if I am targeting a specific size.

+ "Extract audio" shows commands that will reencode the audio stream. If input stream is already in a format that I can use, what I would do is to copy the audio stream without reencoding (`-c:a copy`).

Unless the task is very simple, I rarely use FFmpeg commands. I use GUI tools like Handbrake, which can reduce my cognitive load. Commands only add to my pressure.

Very useful! I'll bookmark that! My most recent search to use with FFMPEG was to convert a folder of Sony videos to Prores. ChatGPT helped me with this one-liner: for f in *.MTS; do ffmpeg -y -i "$f" -c:v prores_ks -profile:v 1 -vendor apl0 -pix_fmt yuv422p10le "proResLT_${f%.MTS}.mov"; done Maybe having the option to create one liners like this, for different platforms, would be nice!

This is useful!

Personally I use AI-shell CLI, type "ai" and ask things like "ffmpeg convert input.mp4 to webm clip first 8 seconds" or any other shell command you need.

https://github.com/BuilderIO/ai-shell

This is helpful when I don't want to use AI.

Any chance you could add "extract clips" in addition to extract frames? Specifically I had to split a video into x-second clips recently & had to use AI to get the right command for that.

The FAQ is basically my use case of ChatGPT. Not just for FFmpeg but pretty much every CLI tool

I've been using ffmpeg so long and so frequently that I have almost forgotten how opaque it is to people who aren't terminally on the computer.

This looks like it could be useful for most people.

Love this. Thank you much

Alternate,

a few batch files

for all common tasks

names starting with ffmpeg.*

and -h displays help.

i use shell oracle (https://github.com/djcopley/ShellOracle), works fine most of the time

> convert this video.mp4 to webm without audio using ffmpeg

$ ffmpeg -i video.mp4 -c:v libvpx -an output.webm