WinUI 3 MediaPlayerElement unable to play videos above 8K resolution while WPF can play them after installing K-Lite Codec Pack

Satyam Mishra 0 Reputation points
2026-06-09T10:41:18.6833333+00:00

Description:

We are facing an issue with WinUI 3 when trying to play ultra-high-resolution videos (e.g., 10K, 12K).

Environment

  • Windows 11
  • WinUI 3 (Windows App SDK)
  • MediaPlayerElement
  • HEVC Video Extensions installed
  • Tested with multiple video formats (H.264, H.265/HEVC)

Problem

The same video cannot be played using WinUI 3 MediaPlayerElement. Playback either fails or the media cannot be opened.

Interestingly, the same video can be played successfully in a WPF application after installing the K-Lite Codec Pack.

Similarly:

  • Windows Media Player cannot play the 12K video by default.
  • After installing K-Lite Codec Pack, Windows Media Player starts playing the video successfully.
  • WinUI 3 MediaPlayerElement still cannot play the same video even after K-Lite installation.

Questions

  1. Does WinUI 3 MediaPlayerElement use Media Foundation exclusively and ignore DirectShow codecs installed by K-Lite?
  2. Is there any supported way to extend codec support in WinUI 3 similar to how K-Lite extends Windows Media Player capabilities?
  3. Are there any documented resolution limits for MediaPlayerElement or Media Foundation?
  4. Is playback of videos above 8K officially supported in WinUI 3?
  5. If MediaPlayerElement cannot leverage third-party codecs, what is the recommended approach for playing 10K/12K videos in a WinUI 3 application?
  6. Would integrating VLC, libVLCSharp, MPV, or another external media engine be the only viable solution?

Any guidance regarding codec extensibility, Media Foundation limitations, or support for ultra-high-resolution video playback would be greatly appreciated.

Windows development | WinUI
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-06-09T10:41:41.0666667+00:00

    Media playback in WinUI 3 with MediaPlayerElement is based on the Windows media platform and its installed codecs. Behavior is therefore constrained by what codecs and resolutions the underlying OS stack supports.

    From the provided information:

    • On Windows, supported formats and capabilities depend on what codecs are installed on the machine. This is explicitly called out for Windows in the .NET MAUI MediaElement documentation, which uses the same underlying platform media stack:
      • “On Windows the supported formats are very much dependent on what codecs are installed on the user's machine.”
    • Windows N editions have no video playback formats installed by design, which further illustrates that playback is tightly coupled to the OS media components and codecs.
    • WinUI 3 apps can play audio and video using MediaPlayerElement and MediaTransportControls, but the release notes only state that these controls are available; they do not document any extended codec or resolution support beyond what the OS provides.

    Given the context:

    1. MediaPlayerElement uses the Windows media platform and its installed codecs. The documentation does not describe any mechanism for MediaPlayerElement to use arbitrary third-party codec packs (such as K-Lite) in the way that legacy players using DirectShow might. The behavior is instead tied to the codecs that Windows exposes for modern apps.
    2. There is no documented, supported mechanism in this context to extend MediaPlayerElement codec support in the same way K-Lite extends Windows Media Player. Codec support is determined by what the OS provides and exposes to the Windows media stack.
    3. The provided documentation does not list any explicit resolution limits (such as 8K, 10K, or 12K) for MediaPlayerElement or Media Foundation. It only states that supported formats on Windows depend on installed codecs.
    4. There is no statement in the provided context that playback of videos above 8K is officially supported in WinUI 3. The documents do not mention 8K, 10K, or 12K resolutions at all.
    5. Because MediaPlayerElement relies on the Windows media stack and its codecs, and there is no documented way here to plug in third-party codecs like K-Lite, the recommended approach for guaranteed playback of 10K/12K content is not covered in this context. The documentation only confirms that WinUI 3 can play media via MediaPlayerElement when the OS codecs support it.
    6. The documentation does not discuss integrating VLC, libVLCSharp, MPV, or other external engines with WinUI 3. Any such integration strategy is outside the scope of the provided material.

    In summary, the available documentation confirms that WinUI 3 MediaPlayerElement depends on the Windows media stack and its codecs, and does not document codec-pack-style extensibility, resolution limits, or explicit support for >8K playback.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Nancy Vo (WICLOUD CORPORATION) 8,155 Reputation points Microsoft External Staff Moderator
    2026-06-10T05:13:35.53+00:00

    Hello @Satyam Mishra ,

    Thanks for your question.

    Does WinUI 3 MediaPlayerElement use Media Foundation exclusively and ignore DirectShow codecs installed by K-Lite?

    Yes, MediaPlayerElement uses Media Foundation exclusively. It does not know DirectShow exists. K-Lite installs DirectShow filters/codecs which are completely invisible to Media Foundation-based apps. You can refer to the Media Foundation Architecture documentation for more details on this separation.

    Is there any supported way to extend codec support in WinUI 3 similar to how K-Lite extends Windows Media Player capabilities?

    Media Foundation has its own extension mechanism called Media Foundation Transforms (MFTs). You can install MF-compatible codec extensions such as the HEVC Video Extensions or AV1 Video Extension from the Microsoft Store. However, no MFT codec currently supports 10K/12K resolution reliably, so this will not resolve your above-8K scenario.

    Are there any documented resolution limits for MediaPlayerElement or Media Foundation?

    Yes. The built-in Media Foundation H.264 decoder is documented to support a maximum resolution of 4096×2304, meaning any H.264 video above that — will not decode through the stock Microsoft H.264 MFT. You can see this stated in the official H.264 Video Decoder documentation. For HEVC, hardware-accelerated decoding reaches up to 8K (7680×4320) with the HEVC Video Extensions and a capable GPU, but above 8K is not officially documented or supported by Media Foundation.

    Is playback of videos above 8K officially supported in WinUI 3?

    No. Microsoft has not officially documented or supported above-8K playback in Media Foundation or WinUI 3. The ceiling is 8K with HEVC + proper hardware.

    What is the recommended approach?

    I recommend using libVLCSharp - you can get started with the LibVLCSharp.Uno NuGet package (for WinUI 3) alongside the VideoLAN.LibVLC.Windows runtime package, and refer to the official quickstart guide for integration details.

    While these are non-Microsoft links, they're official Nuget documentation and are safe to visit.

    I hope this addresses your question. If this response was helpful, please consider following the guidance to provide feedback.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.