What You NEED to Know Before Touching a Video File
A comprehensive field guide to video encoding for novices, written by arch1t3cht after watching subtitling and re-editing communities make the same mistakes repeatedly. It is the video equivalent of a good API design guide: boring fundamentals, sharp opinions, and a clear taxonomy of what not to touch.
Key Quotes
"Quality is how closely it resembles the source it was created from."
This is the guide's central definition and its most transferable insight. Quality isn't an absolute property — it's fidelity to a reference. The same framing underpins evals, spec-driven development, and any system where output must be measured against ground truth. Commentary: This is the video-encoding version of "the spec is the product." Without a reference, quality is meaningless.
"HEVC is 50% more efficient than AVC' is a sentence you will hear a lot. It's just plain wrong."
The author systematically dismantles received wisdom about codec superiority, resolution, bitrate, and format — showing that the encoder program and its settings dominate the format itself. Commentary: This is the encoding parallel to "the model matters less than the harness." The tooling around the standard is more important than the standard.
"frame interpolation is bad. There's not even any nuance here this time, just don't do it."
One of several opinions delivered without hedging. The guide earns the right to be categorical by first explaining the domain in detail, then drawing bright lines. Commentary: Rare in technical writing. Most guides equivocate. This one tells you where the cliffs are and doesn't apologize.
"Always try to manually evaluate sources using your eyes."
The author rejects proxy metrics (Blu-ray > web, higher resolution > lower) in favor of direct sensory evaluation. This is the video equivalent of "don't trust the benchmark, watch the system." Commentary: Taste over metrics. The hardest thing to teach and the first thing automation strips away.
"do not touch any other settings you do not understand."
The encoding template includes exactly one -x264-params flag for anime and a firm injunction against everything else. Commentary: This is deliberate friction as a feature — the encoding equivalent of Slowing the Fuck Down.
Key Themes
- #tool — Video encoding tools evaluated with strong opinions: MediaInfo (essential), ffmpeg (the universal tool), mpv (best player), Handbrake (footgun). The tool recommendations are as opinionated as the encoding advice.
- #concept — Remuxing vs. reencoding: the fundamental distinction between container operations (lossless, fast) and stream operations (lossy, slow). This is a Separation of Concerns pattern that applies far beyond video.
- #concept — Quality as fidelity-to-source rather than absolute goodness. Requires a reference. Maps directly to eval methodology in software.
- #pattern — Reencode once, at the very end. Lossless intermediates everywhere else. The "don't accumulate lossy operations" principle.
Critical Analysis
This is one of the best technical craft guides I've read, across any domain. It succeeds because it does three things most guides get wrong:
It defines quality before discussing it. The interlude on "what is quality actually?" is the structural keystone. Without it, the mythbusting section would read as a collection of "well, actually" corrections. With it, each myth becomes a case study in what happens when you optimize a proxy metric instead of fidelity to source.
It earns its dogmatism. The guide is thick with sharp injunctions — "just don't do it," "do not touch," "not recommended." But each one is backed by an explanation of the underlying mechanism. The reader isn't being told what to think; they're being told what the author has concluded after understanding the mechanism, which is a different thing entirely.
It understands that beginners don't need options, they need defaults. The encoding template is a single ffmpeg command with exactly one situational flag (bframes=8 for anime). This is the opposite of documentation that lists every possible parameter. It's a recommendation, not a reference.
The guide's one weakness is its scope ceiling. It explicitly targets people making edits for distribution or archiving. If you need to produce video from scratch — color grading raw footage, mixing audio, managing multi-camera edits — this won't help. But that's a feature, not a bug. The guide knows exactly what it is and what it isn't.
The Gemini-generated TL;DR in the comments is a perfect accidental demonstration of the guide's thesis: an AI summary can tell you the facts, but it strips the craft. "Use x264 with CRF" is information. Understanding why, and developing the taste to know when, is knowledge.
Cross-References
- Software Engineering Craft — This is a canonical example of craft fundamentals: know your tools, understand the mechanism, develop taste
- Elements of Code — "Wrong in correctable ways" — the guide teaches correctability through understanding
- Feedback Loop is All You Need — Quality defined as fidelity to source is a feedback loop; proxy metrics are open-loop optimization
- Slowing the Fuck Down — "Do not touch any settings you do not understand" is deliberate friction as a discipline
- Radical Accountability — "Use your eyes" is taste, and taste is all that's left when automation handles the mechanics
- Good API Design — Both guides share the same architecture: boring fundamentals, strong defaults, sharp opinions earned through mechanism understanding
- The Mundanity of Excellence — Excellence in encoding isn't more effort; it's qualitatively different choices about what matters
- Common Diagram Mistakes — Same genre: expert catalogues what novices get wrong, explains why it's wrong, gives you the right default
- Better Error Messages — Both are practitioner-to-practitioner craft education that improves output by teaching principles, not recipes
- Proving It Works — The same craft at the end of a pipeline: an ffmpeg-based Claude Code skill that records narrated proof movies and runs a mechanical gate (
check-movie) that catches the silent defects (frozen picture, silent audio, subtitles that quit early) before you hand one to anyone — with "use your eyes" on a contact sheet as the final check
Sources: What you NEED to know before touching a video file Last updated: 2026-05-15