Video codecs in the player

On Windows and Linux CS Player offers several video processing backends: Native (system), VLC, FFmpeg (and additionally MPV). All of them handle the same core task — decoding and playing video — but they operate differently, rely on distinct mechanisms, and come with their own sets of trade-offs.

This page will help you determine which backend to use based on your specific situation, hardware, and the type of issue you’re experiencing. The backend is selected with the --video-backend command-line argument or in the player settings of your screen; Native is the default and the recommended option.

1. Native (system codec)

How it works

This option uses the codecs already installed in your operating system. In most cases, this means the K-Lite Codec Pack, which is installed alongside the player.

Advantages

  • Best image quality among all available options.

  • Most predictable performance on a stable system.

  • Lowest CPU usage when GPU drivers are correctly configured.

What to consider

  • Sensitive to Windows updates. System updates can wipe out or replace the installed codecs, often resulting in a black screen or playback errors.

  • Depends on GPU drivers. Outdated or improperly installed drivers can cause instability.

When to use

  • By default — for the majority of installations.

  • When stability and video quality are top priorities.

  • On systems where Windows automatic updates are disabled or strictly managed.

What to do if Native fails after a Windows update

  1. Reinstall the GPU drivers (preferably using a "clean" installation).

  2. If the issue persists, temporarily switch to VLC. Reinstalling the player can also help restore the K-Lite codecs.

2. VLC

How it works

This option uses codecs from the VLC libraries, compiled specifically for the player.

Advantages

  • Independent of system codecs — ideal when Native is broken.

  • Reliable fallback when the system codec fails for any reason.

What to consider

  • Image quality and stability depend on the hardware configuration.

When to use

  • As a temporary fix when Native fails and you cannot immediately reinstall drivers or troubleshoot Windows updates.

  • On hardware where Native has never worked properly.

3. FFmpeg

How it works

This option relies on the FFmpeg library, compiled specifically for the player.

Advantages

  • Lowest resource consumption of the three.

  • Completely independent of system codecs.

What to consider

  • Playback depends on the hardware configuration.

  • When the video does not play, switch to another backend.

When to use

  • As a last resort when neither Native nor VLC works.

  • On very low-powered hardware where resource efficiency is critical and other options cause lag.

  • If you can check playback on the screen after installation and switch to another backend when needed.