HandBrake "No valid source found" on an MP4 or MOV: how to fix it

By the FixMP4 engineering team · · 7 min read

"No valid source or titles found" means HandBrake's scan opened your file but could not produce a single usable title from it. HandBrake grew up as a DVD ripper and still treats every input as a list of titles; for a plain MP4 or MOV there should be exactly one, called Title 1. When the list is empty, the cause is either a HandBrake setting, a feature of the file, or damage. The activity log tells you which within seconds, so start there.

Read the activity log first

Open the log right after the failed scan:

  • Windows and Linux: the "Activity Log" button on the toolbar.
  • macOS: menu Window, then Activity Log.

Scroll to the lines just after "scan: decoding previews" or "hb_scan". Messages to look for:

Log message (approximate)MeaningGo to
"ignoring title (too short)"The clip is shorter than the minimum durationFix 1
"Unsupported codec" / "no decoder"HandBrake cannot decode a streamFix 2
"moov atom not found" / "Invalid data found"The file has no valid indexFix 4
"Permission denied" / "Could not open"Path or access problemFix 3
"encrypted" / "drm"Protected mediaFix 5

Fix 1: the clip is too short

HandBrake skips titles shorter than its Minimum Title Duration, which defaults to 10 seconds in many versions. Short phone clips, slow-motion snippets and GIF-like loops fall under it. Change it in Preferences (Windows: Tools, Preferences, Advanced; macOS: HandBrake, Settings, Advanced) to 0 or 1 second, then scan again.

Fix 2: the codec is not supported

HandBrake decodes through the FFmpeg libraries, which cover almost everything, but not every variant. Problem inputs include:

  • ProRes RAW, BRAW and camera RAW formats: not supported.
  • Some 10-bit 4:2:2 HEVC from recent mirrorless cameras, depending on version.
  • Dolby Vision profile 5 without a compatible base layer.
  • Image sequences or folders of files that are not one video.

Update to the latest HandBrake release first; codec support improves with each version. If it still fails, convert with the camera vendor's tool or with FFmpeg directly, which sometimes gives a clearer error.

Fix 3: path, permissions and cloud placeholders

  • Files in OneDrive, iCloud Drive or Dropbox may be online-only placeholders. HandBrake sees a tiny stub, not the video. Right-click and choose "Always keep on this device" (or download the file) before scanning.
  • Very long paths or unusual characters can trip older builds. Move the file to a short path such as C:\Video\clip.mp4.
  • Network drives and USB readers that disconnect mid-scan produce random failures. Copy the file to your internal disk.
  • Opening a folder instead of a file: use "Open File" for a single video; "Open Folder" is for DVD structures.

Fix 4: the file has no valid index

If the log mentions a missing moov atom, invalid data or an end of file reached unexpectedly, the problem is the file, not HandBrake. This happens when:

  • a phone or camera lost power while recording;
  • OBS, Game Bar or a screen recorder crashed before stopping;
  • an editor export was cancelled or ran out of disk space;
  • a copy or download was interrupted.

Confirm by opening the file in VLC. If VLC also refuses it, or plays nothing, run the free MP4 file checker. A report of "media data present, index missing" means the frames are on disk but nothing tells players where they are. The FixMP4 repair tool rebuilds that index in your browser, using a short clip from the same device with the same settings as a reference. Once the repaired file plays, HandBrake scans it normally and you can convert as planned. For the background, see how to fix "moov atom not found".

If the issue is an interrupted copy, copy again from the source if it still exists; see video corrupted after transfer.

Fix 5: protected or fake files

  • Apple Store purchases (M4V with FairPlay) cannot be opened by HandBrake. Play them in the Apple TV app.
  • Files that are not videos at all: downloads named .mp4 that are actually HTML pages, archives or tiny placeholders. A file of a few kilobytes is a giveaway. Open it in a text editor; if you see HTML, it was never a video.

Batch scans and queues

When you add a whole folder of camera files with "Open Folder" and some are damaged, HandBrake may skip them silently or stop the batch scan. Check the activity log after a batch scan: it lists each file and any that failed. Move failed files to a separate folder, deal with them using the fixes above, and queue them afterwards. This keeps one bad recording from blocking an evening of encoding.

Command-line HandBrake gives the same answer

If you use HandBrakeCLI in scripts, the same scan runs and the same message appears as "No title found". Add --scan with verbose logging to print the full scan log without encoding. The causes and fixes are identical to the graphical version, and for damaged files you still need to repair the source first, for example with the in-browser tool described in how to uncorrupt a video file.

A quick sanity check before converting

HandBrake is a converter, so it amplifies problems in the source. Before a long encode:

  1. Play the source in VLC and scrub to the middle and end.
  2. Note the codec and frame rate from MediaInfo; phone video is often variable frame rate, which HandBrake handles but editors may not.
  3. If the source has glitches or freezes, fix those first; re-encoding a damaged file bakes the damage in. Our guide to checking a video for corruption shows how.

Summary

  • Read the activity log: it names the cause.
  • Short clip: lower the minimum title duration.
  • Unsupported codec: update HandBrake or use the vendor's converter.
  • Cloud placeholder or bad path: download locally, use a short path.
  • Missing index after a crash or power loss: repair the file with a reference clip in the repair tool, then convert it in HandBrake.

Frequently asked questions

Why does HandBrake say no valid source found for an MP4?

Its scan could not build a title from the file. Typical causes are a clip shorter than the minimum title duration, a codec its decoder library does not support, DRM, or a damaged file without an index.

Where is the HandBrake activity log?

In the Windows and Linux versions use the Activity Log button in the toolbar; on a Mac use Window, Activity Log. It shows the exact reason the scan failed.

Can HandBrake repair a corrupted video?

No. HandBrake converts videos it can read. If the scan fails because the file has no index, rebuild the file first, then convert the repaired copy.

Does HandBrake open iTunes or Apple TV purchases?

No. Protected M4V files from Apple cannot be read by HandBrake or FFmpeg and will always fail the scan.

Have a broken recording right now?

Diagnose it and hear or watch a free repaired preview. Nothing is uploaded.

Open the repair tool
  • HandBrake
  • no valid source
  • scan failed
  • MP4
  • MOV