HandBrake's official documentation does not explain this error message anywhere — but it does state, in plain negative terms, which sources HandBrake will not open. That second half is the useful half, and it is the half most write-ups skip while guessing at causes.
So this page is built the other way round. Instead of decoding a string the vendor never documented, it works through the reasons HandBrake's own docs give for a source being unusable, in the order they actually come up.
What this error actually means
Start with how HandBrake reads a file at all. From the official source formats page:
"One of HandBrake's strengths is its ability to open a wide variety of video formats. HandBrake uses FFmpeg libavformat and libavcodec libraries under the hood and generally can open whatever FFmpeg will, in addition to disc-based formats like DVD and Blu-ray."
That one sentence reframes the whole problem. HandBrake is not maintaining a private parser for each format, so "can HandBrake open this?" is mostly the same question as "can FFmpeg demux and decode this?" — with disc-based sources like DVD and Blu-ray added on top.
Two things follow that are worth holding on to while you troubleshoot:
- The format lists in the docs are examples, not a whitelist. The official page keeps saying "Common video file types are…" and "including but not limited to". A format that does not appear in those lists is not therefore rejected.
- A file that FFmpeg cannot parse is not something HandBrake can parse for you. The dependency runs one way.
There is one more piece of context that saves time. HandBrake's own Troubleshooting common issues page covers only getting the application installed and launched — the .NET Desktop Runtime on Windows, deleting configuration data, reinstalling. It has no entry for this error, or for any other transcoding error. If you have been hunting for an official explanation of the message and coming up empty, that is why: there isn't one to find.
The fastest fix: if it came out of an editor, export it first
This is the single most commonly documented cause, and HandBrake states it flatly:
"Videos made using consumer video editing software such as iMovie and Shotcut must first be exported to a common video format for compatibility with HandBrake."
Note the condition the docs attach: they name consumer video editing software, with iMovie and Shotcut as the examples, and the requirement is that the video be exported first. What you hand HandBrake has to be the exported video file — not whatever your editor saved as your working document.
Which format to export to? Cross-reference the docs' own example lists and MP4 appears in every one of them. For cameras and phones: "Common video file types are MP4 or M4V, MOV, MPG or MPEG, and AVI." For screen recorders: "Common video file types are MP4 or M4V, MKV, MOV, MPG or MPEG, AVI, and WMV." For web video: "HandBrake can open web videos in FLV, WEBM, MP4, and many other formats." Export to MP4 and you are inside every list the documentation offers.
If the export you already have is a QuickTime MOV and you would rather change the container than re-run an export, you can do that in this browser tab:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
That is the embedded MOV to MP4 converter: nothing is uploaded, the file is read from disk, rewritten locally and handed back. Use it when the only thing you need is a different container. When you actually want HandBrake's re-encode — shrinking a file, controlling quality — go back to HandBrake once the source opens, and see what the RF value controls first.
Other causes, in order of likelihood
The file uses DRM
HandBrake's position here is unambiguous, and it is stated as a negative:
"Note: HandBrake does not defeat or circumvent copy protection of any kind. It does not work with video files employing Digital Rights Management (DRM). See About HandBrake for more information about what HandBrake does and does not."
That is the end of the road, by design. Purchased or rented store video, and anything else carrying DRM, is outside what the tool does. No setting, preset or version changes that, and this page offers no way around it.
Related, on the disc side, the docs add: "Without special software, it is not possible to directly copy VIDEO_TS and BDMV folders from copy-protected discs." If you copied a disc folder to your drive and HandBrake will not take it, that statement is the first thing to weigh.
A disc image that has not been mounted
The docs split image files into two groups, and the difference decides whether HandBrake sees anything at all:
- ISO (sometimes labeled CDR) — "HandBrake usually can open these directly."
- BIN+CUE, MDF+MDS, and Toast — "must first be mounted. Open the image using your operating system or appropriate software, and then open the virtual disc with HandBrake."
So for the second group, pointing HandBrake at the image file itself is not the documented workflow. Mount it first, then open the virtual disc.
AVCHD, AVCHD Lite or HD-DVD playlists
Camcorders that record in AVCHD store video the way a Blu-ray does — a folder structure with a playlist. The documentation is explicit that this is only partly supported, in two footnotes:
"AVCHD and AVCHD Lite playlists are not fully supported. Individual files/streams may work."
"HD-DVD playlists are not fully supported. Individual files/streams may work."
The workaround the docs themselves suggest: "HandBrake may be able to open individual video files from the Stream folder inside the BDMV folder. In some cases this is not reliable, e.g. where a single video stream spans multiple files."
Read that carefully — the official wording is "may be able to" and "not reliable", with a video spanning several files given as the example case. The docs do not describe what the failure looks like, so do not expect a specific symptom.
A disc that was badly mastered
For home recordings, one sentence covers a case people rarely suspect: "Recordings made by TV-to-DVD recorders are generally supported, but do note that some recorders are known for poorly making discs. Some discs may not work due to mastering errors."
If several discs from the same recorder all fail, the discs are the likelier suspect than your settings.
HandBrake itself is not running properly
If HandBrake is misbehaving generally — not launching, odd since an update — the official troubleshooting page is the checklist, though nothing on it is documented as a fix for a source that will not open. Its steps: restart the computer; on Windows, make sure the latest .NET Desktop Runtime is installed for your system; delete HandBrake's configuration data and presets; install or reinstall the latest version. That page names a specific .NET version and the number moves, so read it off the official page rather than any article.
How to tell it worked
Point HandBrake at the newly exported file, or the mounted disc, or the individual stream file. If it loads, the source problem is solved and everything after that is a preset and encoder question.
One sanity check on the output side before you commit to HandBrake at all. Its documentation states that HandBrake "creates the widely supported container formats MKV and MP4 (sometimes seen as M4V), in addition to the WebM container format, which is subset of MKV." If what you actually needed was a different container or an audio-only file, that is not what those three containers give you — browse the Clapr tools for the format you are after instead.
FAQ
Why does HandBrake say "No valid source found"? HandBrake's official documentation does not document that message, so nobody can honestly tell you what it means in every case. What the docs do give you is a list of sources HandBrake will not open: anything using DRM, project files from consumer editors that have not been exported, unmounted BIN+CUE / MDF+MDS / Toast images, and AVCHD or HD-DVD playlists, which are "not fully supported."
Can HandBrake open a DRM-protected video? No. The documentation states it "does not work with video files employing Digital Rights Management (DRM)" and that it "does not defeat or circumvent copy protection of any kind." There is no setting that changes this.
Why won't HandBrake open my iMovie project? Because a project is not a video file yet. HandBrake's docs say videos made using consumer editing software such as iMovie and Shotcut "must first be exported to a common video format" before HandBrake can use them. Export the timeline, then open the exported file.
Does HandBrake support MOV, MKV, WMV and AVI files? All four appear in the documentation's examples of file types HandBrake can open, and the underlying claim is broader: HandBrake uses FFmpeg's libavformat and libavcodec and "generally can open whatever FFmpeg will." Those lists are illustrative, not exhaustive.
Is there an official list of HandBrake error messages? Not in the documentation. The troubleshooting page covers installation and launch problems only — no transcoding errors are listed. Treat any article that confidently explains a specific HandBrake error string as unsourced unless it cites something.
Still stuck on the file itself rather than on HandBrake? The rest of the fix guides work through the same kind of problem for other tools, and if a preset went missing rather than a source, start with HandBrake's renamed Discord presets.
Quotes above are from HandBrake's official documentation at handbrake.fr, checked 16 September 2026. HandBrake's docs change between releases — verify against the official pages before relying on them.
