Video Pre-Flight Checker for YouTube, Facebook & Twitch
Drop in the file you plan to stream and find out whether YouTube Live, Facebook Live and Twitch will accept it — before you schedule the event, not after it fails.
Your file is read in this tab and never uploadedDrop a video file here
or click to choose one — MP4, MOV, MKV and WebM
Will it stream?
What is in the file
Related reading
Converting MP4 to H.264
The fix when the checker flags your codec or level.
Choosing a Bitrate for Streaming
Why the recommended figures differ per platform.
Optimising Video for YouTube
Getting a file through ingest the first time.
What Bitrate for 1080p
The most common resolution, and its most common mistake.
Questions this tool gets asked
Why would Facebook reject a file whose resolution and bitrate are both fine?
Because it also pins the H.264 level. A level is a decoder capability contract, not a label, and level 4.0 cannot carry 1080p60 at all regardless of how the file is otherwise encoded. Most checkers only look at codec and resolution, which is why this particular failure tends to get discovered at broadcast time.
My file passes YouTube but fails Twitch. Which one is wrong?
Neither — the platforms genuinely differ. YouTube ingests up to 2160p60 and publishes its bitrates as recommendations, while Twitch caps at 1080p60 and enforces a far lower bitrate for non-partner channels. A file can be comfortably within one and well outside the other.
It says my bitrate is above the recommendation but the file still passes. Should I re-encode?
Not necessarily. A recommendation is not a rejection, and these platforms accept higher rates routinely. The warning is there because viewers on slower connections are the ones who pay for the extra bitrate, not because the broadcast will fail.
What is faststart, and does it matter for live streaming?
It means the file's index sits at the front rather than the end, so playback can start before the whole file has been read. It matters more for direct playback than for streaming, which is why it is reported as a warning rather than a failure.
An attribute came back unknown. Why not just pass the file?
Because a file that could not be fully read is not one anyone can promise will work. An unreadable attribute holds the verdict at incomplete rather than letting it quietly count as a pass.
Where do these platform limits come from, and how current are they?
Every verdict card links its source and shows the date it was last checked. YouTube's figures come from Google's own encoder settings documentation. Twitch's and Facebook's official pages do not serve readable content to automated tools, so those are corroborated from secondary sources and labelled as such on the card.
Is my file uploaded anywhere?
No. It is read inside the page by a WebAssembly build of MediaInfo, a chunk at a time, which is also why a large file does not need to finish loading before the result appears. There is no server behind this tool and no request carries any part of the file.