Can't skip forward in a video? Why some files aren't seekable and how to fix them
By the FixMP4 engineering team · · 9 min read
A video that plays from the beginning but ignores clicks on the progress bar, jumps back to 0:00 or shows a duration of "--:--" is not seekable. The picture and sound are fine, but the player has no way to jump to a specific moment. This is a structural problem with a clear set of causes, and in most cases it is fixed in seconds with a lossless remux. This article explains what seeking requires, which kinds of files lack it, and how to repair each kind.
What a player needs in order to seek
To jump to 5:30, a player has to answer two questions: where in the file does the data for 5:30 start, and is there a keyframe there it can begin decoding from? Video is compressed in groups of pictures that depend on a keyframe, so playback can only start cleanly at one. The article keyframes and GOP explained covers that part in detail.
Containers answer the first question with an index:
- MP4 and MOV use the moov atom, which lists every sample's position and timing, plus a table of keyframes.
- Matroska and WebM use a Cues element, an index of keyframe positions, and a Duration field in the header.
- Fragmented MP4 uses per-fragment headers and, optionally, an index such as sidx or mfra.
- MPEG transport streams have no index at all; players estimate positions from the bitrate.
When the index or the duration is missing, the player either refuses to seek, guesses badly, or reads the whole file from the start to find the target.
Cause 1: browser and web app recordings (WebM)
Many web-based screen recorders, meeting tools and voice-note features use the browser's MediaRecorder interface. It produces a live stream: chunks are written as they are recorded, and when you stop, nothing goes back to the start of the file to write the duration or append the Cues index. The result is a WebM file that plays, but whose length shows as unknown or grows as it plays, and whose progress bar does nothing in many players.
Fix: remux it. With FFmpeg:
`` ffmpeg -i recording.webm -c copy fixed.webm ``
FFmpeg reads the whole stream, then writes a new WebM with a proper duration and index. MKVToolNix (mkvmerge) does the same through a graphical interface. If you need MP4 for an editor, convert instead, which re-encodes because WebM codecs (VP8, VP9, Opus) are not the usual choice for MP4.
Cause 2: recordings that stopped without finishing
When a recorder writes an MP4 or MOV and gets interrupted, the moov atom is never written. In the most common case the file will not play at all, but some players can still decode it by scanning for frames, and then seeking is the first thing to break. With Matroska recordings (OBS's MKV mode, for example), an interrupted file usually plays fine but lacks Cues, so seeking is slow or impossible.
For MKV, a remux as above rebuilds Cues. For MP4 and MOV, the index has to be reconstructed from the raw data, which is a repair rather than a remux. The FixMP4 repair tool does this in your browser with the help of a short healthy reference recording from the same device, and the rebuilt index includes the keyframe table, so the repaired file seeks normally. See what is the moov atom for why the index is written last.
Cause 3: fragmented MP4 without an index
Fragmented MP4 is written in small self-contained pieces, which makes it crash-safe and stream-friendly. Our article on fragmented MP4 explains the structure. Some recorders and download tools produce fragmented files without an overall index, and certain players then cannot seek across fragments or show the full duration. A remux to a regular, non-fragmented MP4 solves it:
`` ffmpeg -i input.mp4 -c copy -movflags +faststart output.mp4 ``
The faststart flag also moves the index to the front, which helps when the file is played over the web; more on that in MP4 fast start explained.
Cause 4: the file is served without range requests
If a video seeks fine when you open it from your disk but not when you play it from a website, the server is the problem. To jump ahead, the browser asks the server for a specific byte range of the file. A server or app that ignores those requests forces the browser to download from the beginning, so the progress bar snaps back. You can check with the browser's developer tools: a seekable video responds with status 206 Partial Content and an Accept-Ranges header. Static file servers such as nginx handle this by default; custom application code that streams files often does not, and needs to implement range support.
Cause 5: transport streams and raw streams
MPEG-TS files from TV tuners and some cameras, and raw H.264 or HEVC streams (.h264, .h265), have no index by design. VLC handles them reasonably, but many players and editors do not. Remux them into MP4:
`` ffmpeg -i input.ts -c copy -bsf:a aac_adtstoasc output.mp4 ``
The bitstream filter is needed when the transport stream carries AAC audio, because MP4 stores AAC differently.
Quick diagnosis
| Symptom | Likely cause | Fix |
|---|---|---|
| Duration unknown or growing, WebM from a browser | No duration or Cues | Remux with FFmpeg or mkvmerge |
| MKV from a crashed recording, slow seeking | Missing Cues | Remux |
| MP4 plays only in VLC, cannot seek | Missing moov atom | Rebuild the index with a repair tool |
| Seeks locally, not on the website | No HTTP range support | Fix the server |
| TS or raw stream | No index by design | Remux to MP4 |
When it is more than seeking
If the video also freezes at the same point every time, shows green or grey blocks, or stops before the end, there is damaged data in the file as well. A remux will not fix that. The article on videos that freeze halfway through explains how to tell those cases apart and what can be salvaged.
Frequently asked questions
Why does my video play but not let me skip ahead?
The player cannot map a time position to a location in the file. That happens when the file has no index of keyframes, when it has no total duration, or when it is streamed from a server that does not let the player request a specific part of the file.
Why are browser recordings often not seekable?
Recordings made in the browser with the MediaRecorder interface are written as a live stream. The browser does not know the final length while recording and does not go back to add an index at the end, so the WebM file has no duration and no seek points until it is processed.
Does fixing seeking reduce video quality?
No, as long as you remux rather than re-encode. A remux copies the compressed audio and video exactly and only rewrites the container, adding the index and duration. It is fast and lossless.
Is a video that cannot be seeked corrupted?
Not by itself. Many perfectly intact files simply lack an index. If the file also stops playing early, shows blocks of garbage or will not open in any player, then the data may be damaged too and needs a repair rather than a remux.
Have a broken recording right now?
Diagnose it and hear or watch a free repaired preview. Nothing is uploaded.
Open the repair tool