Sample 640x360 3s MP4
https://assets.testfiles.dev/video/sample-3s.mp4 MP4 · 120 KBSample 640x360 3s MOV
https://assets.testfiles.dev/video/sample-3s.mov MOV · 120 KBSilent 640x360 3s WebM
https://assets.testfiles.dev/video/silent-3s.webm WebM · 144 KBSilent 640x360 3s MP4
https://assets.testfiles.dev/video/silent-3s.mp4 MP4 · 80 KBSilent 640x360 3s MOV
https://assets.testfiles.dev/video/silent-3s.mov MOV · 80 KBTiny 320x240 2s WebM
https://assets.testfiles.dev/video/tiny-320p.webm WebM · 125 KBTiny 320x240 2s MP4
https://assets.testfiles.dev/video/tiny-320p.mp4 MP4 · 56 KBTiny 320x240 2s MOV
https://assets.testfiles.dev/video/tiny-320p.mov MOV · 56 KBStable video samples for playback, upload, codec, and Range tests
Published videos have stable URLs, exact byte sizes, verified hashes, codec metadata, posters, and dedicated detail pages. Compare matching WebM, MP4, and MOV fixtures to isolate container behavior.
Test method
Use matching MP4, MOV, and WebM clips in the player and upload pipeline, including the silent and low-resolution variants.
Validation steps
Check status 200, request an initial byte range, inspect duration, dimensions and tracks, then seek and replay the downloaded file.
Expected result
The server returns 206 for valid Range requests, metadata matches the detail page, and playback reaches the end without decode errors.
Failure signals
Flag missing Accept-Ranges, a full 200 response to a valid range, incorrect duration, an unexpected audio track, stalled seeking, or a codec error.