Error code 224003 "This video file cannot be played": real fixes
By the FixMP4 engineering team · · 7 min read
Error code 224003 comes with the message "This video file cannot be played" and is shown by JW Player, a web video player embedded on thousands of sites. The code is JW Player's translation of a browser report: the HTML5 video element was given a source it does not support or cannot decode. The fix depends on who you are. If you are watching someone else's video, the problem is almost always in your browser. If the video is yours (you uploaded it to a course platform, CMS or company portal), the problem is usually the file.
For viewers: fix the browser first
Try these in order and reload the page after each one.
1. Test in a private window
Open an Incognito (Chrome), InPrivate (Edge) or Private (Safari, Firefox) window and load the same page. Private windows start without extensions and with an empty cache. If the video plays there, the cause is one of the next two steps.
2. Disable extensions, especially ad and script blockers
Ad blockers, privacy filters and "video downloader" extensions can block the requests the player needs. Turn them all off, reload, then re-enable them one at a time to find the culprit. Allow-list the site in that extension rather than removing it.
3. Clear cached images and files
A partially cached video segment can keep failing. In Chrome press Ctrl+Shift+Delete (Cmd+Shift+Delete on a Mac), choose "Cached images and files", and clear. Cookies can stay unless the site's login is also misbehaving.
4. Toggle hardware acceleration
Chrome: Settings, System, "Use graphics acceleration when available". Edge: Settings, System and performance. Restart the browser after switching. If the video now plays, update your graphics driver and then try turning acceleration back on.
5. Update the browser and the operating system
Codec support lives partly in the browser and partly in the OS. HEVC playback in Chrome and Edge on Windows depends on hardware support and system codecs; Safari plays HEVC natively on recent Apple devices. An outdated browser may simply not know the codec.
6. Check the network
Corporate proxies, VPNs and strict firewalls sometimes strip or block video responses. Try another network, such as a phone hotspot. If the video works there, talk to whoever manages the original network.
For site owners: check the file you uploaded
If many visitors report 224003 on the same video, the browser is not the problem. Download the exact file the platform serves (or the file you uploaded) and inspect it with MediaInfo, ffprobe, or the free in-browser MP4 file checker.
Wrong codec for the web
The safest combination for every browser is H.264 video (High profile, 8-bit, 4:2:0) with AAC audio in an MP4 container. Files that cause 224003 often contain:
- HEVC/H.265 from an iPhone or camera, which Firefox does not play and Chrome only plays on some hardware;
- 10-bit or 4:2:2 H.264 from mirrorless cameras, which browsers do not decode;
- ProRes or DNxHR MOV files exported from an editor;
- PCM, AC-3 or Opus audio in an MP4.
Re-encode a copy with HandBrake (preset "Fast 1080p30" or "Web" presets) or FFmpeg:
`` ffmpeg -i source.mov -c:v libx264 -preset slow -crf 20 -pix_fmt yuv420p -c:a aac -b:a 160k -movflags +faststart web.mp4 ``
The +faststart flag moves the index to the front so playback starts before the whole file downloads; our article on MP4 fast start explains why that matters.
Incomplete or damaged upload
If the codec is fine but the file still fails locally in VLC, the upload source is broken. A recording that stopped when a laptop slept, a screen recorder that crashed, or an export interrupted halfway all leave files without a valid index. Re-export from your editor if you can. If the only copy is the broken recording, the FixMP4 repair tool can rebuild its index in your browser, using a short healthy clip from the same recorder as a reference; check the free preview, then export and re-upload. Our guide to repairing an MP4 file walks through the choices.
Server and hosting issues
Self-hosted players need the server to answer byte-range requests (HTTP 206) and to send the correct Content-Type: video/mp4. A misconfigured CDN or a missing MIME type can produce source errors in some browsers only. Test the raw video URL directly in the browser: if it does not play there, fix the hosting before blaming the player.
Example: a course video that fails for half the students
An instructor records a lesson on an iPhone, uploads the MOV to a course platform that uses JW Player, and half the class reports error 224003. The students on Safari and on recent Macs can watch; those on Firefox and older Windows laptops cannot. MediaInfo shows the video is HEVC 10-bit with Dolby Vision metadata. Nothing is broken: the file simply needs a universal format. Re-encoding to H.264 8-bit MP4 with fast start, or setting the iPhone camera to "Most Compatible" before recording, solves it for everyone. If the platform transcodes uploads itself, check that it actually produced H.264 renditions; some only repackage the original.
Related errors you might see
- 224002: the browser started decoding but hit corrupted data. With your own uploads, treat it like a damaged file.
- 232011 and 232001: network or manifest problems, often with streaming formats.
- Chrome's own "Your browser can't play this video" on a local file means the same thing outside JW Player: an unsupported codec or a damaged file. Our overview of why a video won't play after recording covers the local-file side.
Quick decision guide
- Watching someone else's video and it fails only for you: private window, extensions, cache, hardware acceleration, updates, network.
- It is your video and fails for everyone: check the codec, re-encode to H.264/AAC MP4 with fast start, and confirm the file plays in VLC before uploading again.
- Your source recording itself will not open anywhere: rebuild it first with the repair tool, then encode for the web.
Frequently asked questions
Where does error code 224003 come from?
It is produced by the JW Player web video player, which many news, e-learning and corporate sites use. It means the browser's built-in video engine reported that it could not play that source.
Does turning off hardware acceleration really fix 224003?
Sometimes. When the GPU decoder or its driver misbehaves, software decoding works instead. It is worth testing, then re-enabling acceleration if it makes no difference.
I uploaded the video myself and visitors get 224003. What is wrong?
Most often the file uses HEVC or another codec some browsers cannot decode, or the upload is incomplete or damaged. Re-encode to H.264 with AAC audio in MP4 and upload again.
Is 224003 the same as error 232011 or 102630?
They are related JW Player codes. 232011 usually points at a network or manifest problem, 102630 at an empty playlist. 224003 is specifically an unsupported or undecodable source.
Have a broken recording right now?
Diagnose it and hear or watch a free repaired preview. Nothing is uploaded.
Open the repair tool