Seven Common Video File Problems and What Actually Causes Them

Most video problems look mysterious and have dull, specific causes. Here are the ones that come up repeatedly.

1. The video plays but there is no sound

Almost always an audio codec the player does not support. The container opened, the video stream decoded, the audio stream did not.

This happens with AC-3 or DTS audio in files intended for home cinema systems, and occasionally with newer codecs like Opus in players that predate them. The fix is to re-encode the audio to AAC, which is as close to universally supported as audio gets. The video stream can be copied across untouched, so it is quick and costs no video quality.

2. The file will not open at all

Either the container or the video codec is unsupported. An MKV in a browser, or H.265 on a machine without a decoder, both produce this.

Try a player with its own bundled decoders, such as VLC, before concluding the file is corrupt. If it plays there, the file is fine and your original player was simply missing a codec. Converting to H.264 in an MP4 makes it openable essentially anywhere.

3. Audio and video drift out of sync

Two distinct causes, and they need different fixes.

Constant offset: audio is consistently ahead or behind by the same amount throughout. This is a timestamp problem and is easily corrected by shifting the audio track.

Progressive drift: sync is fine at the start and worsens over time. This means the frame rate is variable. Screen recorders and phone cameras often record variable frame rate footage, which many editors mishandle by assuming a constant rate. Converting to constant frame rate before editing fixes it. If you have the choice, record at constant frame rate in the first place.

4. The video looks worse after editing

Generational loss. Formats like H.264 are lossy, so every decode-and-re-encode cycle discards more detail. Edit an export, then edit that, and the degradation compounds.

Two habits prevent it: always work from the original source rather than a previous export, and prefer stream-copy operations, which do not re-encode at all. Trimming can often be done losslessly.

5. The trimmed clip starts in the wrong place

Keyframes. A lossless trim can only cut at frames that stand alone, so your start point snaps to the nearest one before your chosen moment. This is normal and is the trade for speed and zero quality loss. Re-encoding gives frame-accurate cuts at the cost of time and a compression generation. We cover the mechanics in our guide to keyframes.

6. The file is far larger than expected

Bitrate, usually inherited from a camera that records at very high quality by default. Phones shooting 4K at 60 fps produce enormous files.

Check the duration and bitrate before assuming something is wrong. If the number is genuinely high for the content, re-encoding at a sensible bitrate will shrink it dramatically with little visible difference. Trimming unwanted footage first is free and always worth doing.

7. The video is rotated or sideways

Phones record in a fixed sensor orientation and store a rotation flag in the metadata telling players how to display it. Players that honour the flag show it correctly; players that ignore it show it rotated.

The file is not damaged. Either fix the metadata, or re-encode with the rotation physically applied so the pixels themselves are the right way up. The second is more reliable if the file is going somewhere unpredictable.

The general principle

Almost every one of these is a mismatch between what a file contains and what a particular piece of software expects, rather than damage to the file. Before re-encoding anything, find out what is actually inside: container, video codec, audio codec, frame rate, bitrate. Knowing those five things resolves most of these problems immediately.