We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

YouTube 4K video playback performance issue on Windows 11

  • 5 replies
  • 1 has this problem
  • 1 view
  • Last reply by mingsun123

more options

I had been using Firefox browser for awhile, but because of playback performance issue, I have to using another browser just for video playing, especially for 4K video.

Compared to Edge, Firefox seems taking more resources to playback the YouTube video and more heat. When look at the Task Manager, the Video Processing is 0%, and GPU is running significantly more resources on '3D'.

I had been using Firefox browser for awhile, but because of playback performance issue, I have to using another browser just for video playing, especially for 4K video. Compared to Edge, Firefox seems taking more resources to playback the YouTube video and more heat. When look at the Task Manager, the Video Processing is 0%, and GPU is running significantly more resources on '3D'.

Chosen solution

The issue has been resolved after updated to Firefox 100.

Thanks.

Read this answer in context 👍 0

All Replies (5)

more options

This is the screenshots I got, the image from the left is from Firefox & next is from Edge. The YouTube Links: here

Modified by mingsun123

more options

mingsun123 said

Hello! Does it still happen in Troubleshoot Mode?: Diagnose Firefox issues using Troubleshoot Mode

more options

-elison- said

mingsun123 said

Hello! Does it still happen in Troubleshoot Mode?: Diagnose Firefox issues using Troubleshoot Mode

It even worst, and video playback was lagging.

more options

donthavecow said

You said Windows 11 but your screenshot is showing Mac?

That is the video....

more options

Chosen Solution

The issue has been resolved after updated to Firefox 100.

Thanks.