Web Browser Showdown: Safari vs Chrome vs Brave vs Edge vs Firefox

In this article, I will compare the main and most popular browsers. I know there are more (Vivaldi, Opera, Arc, etc.), but I wanted to focus on the most popular ones to avoid making the article too long.

The versions tested are as follows:

• Safari 17.1
• Chrome 119
• Brave 1.60 (Chromium 119)
• Edge 119
• Firefox 120

First, I will test the supported features of HTML5 using the html5test.com website and summarize the differences. Differences in features that have been rejected or replaced by more modern ones will be ignored.

Then, with YouTube loaded, I’ll look at the memory each browser is using with all extensions disabled.

Let’s go!

HTML5test scores (from best to worst)

• Chrome: 476
• Brave: 476
• Edge: 476
• Safari: 475
• Firefox: 466

Differences in elements

                                  Safari  Chrome  Brave  Edge  Firefox

ping attribute on the a element     ✅      ✅     ✅    ✅      ❌

Differences in forms

                             Safari  Chrome   Brave   Edge   Firefox  

input type=month               ❌      ✅      ✅     ✅      ❌

input type=week                ❌      ✅      ✅     ✅      ❌

Differences in location and orientation

                             Safari  Chrome   Brave   Edge   Firefox 

Device orientation             ✅      ✅      ✅     ❌      ✅

Device motion                  ✅      ✅      ✅     ❌      ✅

Differences in input

                             Safari  Chrome   Brave   Edge   Firefox 

Gamepad control                ✅      ✅      ✅     ✅      ❌

Differences in peer to peer

                             Safari  Chrome   Brave   Edge   Firefox 

ObjectRTC API for WebRTC       ✅      ✅      ✅     ✅      ❌

Access the webcam              ❌      ✅      ✅     ❌      ❌

Screen Capture                 ❌      ✅      ✅     ❌      ❌

Enumerate devices              ❌      ✅      ✅     ❌      ❌

Differences in user interaction

                             Safari  Chrome   Brave   Edge   Firefox 

dropzone attribute             ✅      ❌      ❌     ❌      ❌

Differences in performance

                             Safari  Chrome   Brave   Edge   Firefox 

window.requestIdleCallback     ❌      ✅      ✅     ✅      ✅

Differences in video

                             Safari  Chrome   Brave   Edge   Firefox 

Audio track selection          ✅      ❌      ❌     ❌      ❌

Video track selection          ✅      ❌      ❌     ❌      ❌

MPEG-4 ASP support             ✅      ❌      ❌     ❌      ❌

Ogg Theora support             ❌      ✅      ✅     ✅      ✅

Differences in audio

                             Safari  Chrome   Brave   Edge   Firefox 

Speech recognition             ✅      ✅      ✅     ✅      ❌

Dolby Digital support          ✅      ❌      ❌     ❌      ❌

Dolby Digital Plus support     ✅      ❌      ❌     ❌      ❌

Ogg Vorbis support             ❌      ✅      ✅     ✅      ✅

Ogg Opus support               ❌      ✅      ✅     ✅      ✅

Differences in streaming

                                Safari  Chrome   Brave   Edge  Firefox 

DRM support                       ✅      ❌      ❌     ❌      ✅

HTTP Live Streaming / HLS         ✅      ❌      ❌     ❌      ❌

TS with H.264 support             ✅      ❌      ❌     ❌      ❌

MP4 with Dolby Digital support    ✅      ❌      ❌     ❌      ❌

MP4 with Dolby Digital Plus supp. ✅      ❌      ❌     ❌      ❌

Differences in 2D graphics

                             Safari  Chrome   Brave   Edge   Firefox 

WebP support                   ❌      ✅      ✅     ✅      ✅

Differences in web applications

                             Safari  Chrome   Brave   Edge   Firefox 

Push Messages                  ❌      ✅      ✅     ✅      ❌

Memory consumption after loading YouTube

On Windows I have only tested Edge and Firefox, because my system is ARM, and they are the only browsers that have a version for this architecture. Although the rest work correctly, they have an emulation layer, and memory consumption may be different.

I was surprised to see the difference in memory consumption between macOS and Windows. I don’t know why. They are very different systems, and in the end, all browsers work well on both systems, but the numbers are twice as high on macOS.

On the other hand, the consumption is very stable in macOS, while on Windows, a process can use 300 MB and, in a few seconds, jump to double, then go down a little, then go up again, etc. I found it easy to get an average in macOS, but on Windows, they are very changeable values. So after about 10 seconds, I wrote down the average value that seemed more stable to me.

Conclusion

One browser has come out the clear winner in both tests: Chrome. Although it has the same score in HTML5, its memory consumption is lower. So, if you want the best browser based on Chromium, with the Blink engine developed by Google, Meta, Microsoft, Opera, Adobe, Intel, IBM, and Samsung, that browser is Chrome.

If ad blocking is very important to you, instead of installing an extension, I recommend Brave, which already integrates this functionality, and you will save memory.

Edge is a unique option, being ideal if you use Microsoft services. It has unique options, such as Bing Chat support or screen splitting to load two websites in the same tab.

Safari keeps up quite well, rubbing shoulders with Chromium-based browsers. Remember that Safari is the only one that integrates with iCloud+ if you are in the Apple ecosystem and pay for this service.

With its Gecko engine, Firefox is the lowest rated in the HTML5 test. It also consumes the highest amount of memory on macOS.

Also published here.