Skip to content

Recipes by outcome

Every supported recipe names an input contract, command, expected output, and machine-verifiable checks.

Built from repeated user problems

These are not invented demo categories. Independent FFmpeg users repeatedly ask why MP4 works locally but not in browsers, how to fit a complete video under a size limit, and why secondary tracks disappear. Each linked PyFFmpegCore recipe turns one of those clusters into an inspectable plan, a deterministic media test, and explicit verification steps.

Use probe before and after. If the input has multiple audio tracks, chapters, attachments, rotation, HDR metadata, or cover art, verify what the workflow preserves before deleting the source.