Talk to the people who build FFmpeg

There's no single "contact us" form and no official forum — FFmpeg runs entirely on mailing lists and IRC. Here's which one to use, before any of the etiquette rules that used to come first.

Pick a channel by what you need

Mailing lists, by purpose
List	Use it for
`ffmpeg-user`	General questions about using the ffmpeg, ffplay or ffprobe command-line tools
`libav-user`	Questions about calling the FFmpeg libraries from your own code
`ffmpeg-devel`	Development of FFmpeg itself, and submitting patches
`ffmpeg-cvslog`	Read-only feed of every commit — no discussion happens here
`ffmpeg-trac`	Read-only feed of bug tracker activity — no discussion happens here

IRC, on the Libera Chat network
Channel	Use it for
`#ffmpeg`	User support and general questions, same scope as ffmpeg-user
`#ffmpeg-devel`	FFmpeg development only — not for apps that merely use FFmpeg

No account needed to read or join either channel: web.libera.chat works from a browser. Both channels are logged publicly, and both are covered by the project's Code of Conduct.

No official forum

FFmpeg doesn't run one itself. If a web forum's search engine sent you here, the mailing lists and IRC channels above are the actual project — treat any third-party forum as community-run, not officially supported.

Before you post

Mailing-list etiquette (worth reading before your first post)

Reply below the message you're quoting, not above it, and don't hijack an existing thread for a new topic.
Wrap plain-text lines around 70 characters if your mail client will let you.
Send patches as plain text or a unified diff (ideally via git format-patch or git send-email), never as an attached binary blob.
Skip the corporate email disclaimer — it doesn't apply to a public technical mailing list, and it makes your message harder to read.
Search the list archives first; most questions have already been answered there.