One address, read by a person.

There is no ticket system and no contact form, because the site has no server to receive one. Email reaches the person who wrote the tool you are writing about. Replies are usually within a few days, sometimes longer when the day job is busy.

Reporting a tool that failed

Failures in a browser build of FFmpeg are usually specific to one file and one browser, so a report is only actionable with a bit of detail. The most useful message includes:

• The page you were on, as a URL.
• The command shown in the panel on that page. There is a Copy button on it.
• The contents of the ffmpeg log section underneath, which is collapsed by default and holds the actual error.
• Your browser and operating system, and whether the file was large enough that memory might be the issue.
• What the file is, as reported by media info: container, codec, resolution, duration. This is more useful than the file itself and does not require sending anything.

Please do not attach the media. It will not help, and the entire point of this site is that your files stay with you. The log and the media info are almost always enough to reproduce a problem locally.

Asking for a tool

Requests are welcome and several tools on the site exist because somebody asked. The realistic constraint is what the shipped FFmpeg build can do: it carries 12 libraries, listed on the licenses page, and anything needing a codec outside that set would mean shipping a different binary to every visitor. Encoding that is stable in a terminal is also not automatically stable in WebAssembly without threads, which is why there is no VP9 or AV1 encoder here.

Licensing and attribution

FFmpeg is distributed here under the GPL, version 2 or later, and the unmodified binary and its loader are linked directly from the licenses page so that the source obligation is satisfiable. If you believe something on this site is misattributed, incorrectly licensed, or missing a required notice, write in and it will be corrected.

Privacy questions

The privacy page covers what is collected, which is server access logs and nothing else from the tools themselves. If you have a question it does not answer, including anything about the advertising on the site or the one third-party model download, ask directly.

Press and licensing the site itself

Happy to answer questions about how the site is built, and the how it works page is a reasonable starting point. For anything commercial, including embedding these tools somewhere else, the same address is the place to start.