General information

Support

These tables summarize what actively-developed²⁸ engines support.

Operating systems

The operating systems that engines can run on without emulation.

Notes

Image formats

Media formats

Typography

Other items

See also

• Comparison of web browsers
• Comparison of email clients

Notes

References

1. Active status means that new Web standards continue to be added to the engine, which properly renders the vast majority of websites, including multimedia. However, Maintained status can be as minimal as ensuring the engine code still compiles; this includes relatively new engines that are not yet robust enough to be Active here. Discontinued is when the engine code is abandoned. /wiki/Web_standards ↩

2. Paul Festa (14 January 2003). "Apple snub stings Mozilla". CNET Networks. Archived from the original on 25 October 2012. Retrieved 16 February 2017. /wiki/Paul_Festa ↩

3. Bright, Peter (3 April 2013). "Google going its own way, forking WebKit rendering engine". Ars Technica. Conde Nast. Retrieved 9 March 2017. https://arstechnica.com/information-technology/2013/04/google-going-its-own-way-forking-webkit-rendering-engine/ ↩

4. Active status means that new Web standards continue to be added to the engine, which properly renders the vast majority of websites, including multimedia. However, Maintained status can be as minimal as ensuring the engine code still compiles; this includes relatively new engines that are not yet robust enough to be Active here. Discontinued is when the engine code is abandoned. /wiki/Web_standards ↩

5. "Open-sourcing Chrome on iOS!". 2017. Retrieved 26 April 2021. Due to constraints of the iOS platform, all browsers must be built on top of the WebKit rendering engine. https://blog.chromium.org/2017/01/open-sourcing-chrome-on-ios.html ↩

6. "Current browser market share". StatCounter. Retrieved 29 October 2021. https://gs.statcounter.com/ ↩

7. Goanna is a fork of an old version of Gecko. It has less web compatibility, but still renders the vast majority of websites.[5] /wiki/Fork_(software_development) ↩

8. M. C. Straver. "About Moonchild Productions". Archived from the original on 13 March 2017. Retrieved 19 April 2018. https://web.archive.org/web/20170313050503/http://www.moonchildproductions.info/about.shtml ↩

9. Internet Explorer continues to receive security updates,[7] which means Trident (a.k.a. MSHTML) is still maintained. /wiki/Internet_Explorer ↩

10. Mendelevich, Alan (14 May 2021). "You Think You Can Forget About the "Legacy" Microsoft Edge? Not So Fast!". https://blog.ailon.org/you-think-you-can-forget-about-the-legacy-microsoft-edge-not-so-fast-28ce91270a22 ↩

11. Mackie, Kurt (10 December 2018). "Microsoft Edge Browser To Get New Rendering Engine but EdgeHTML Continues". Redmond Mag. Retrieved 21 December 2019. https://redmondmag.com/articles/2018/12/10/edgehtml-continues.aspx ↩

12. In 2013, Opera replaced the Presto engine with Blink for its flagship desktop and mobile browser. But it still has a special niche usage of Presto as a server-side renderer for the Opera Mini browser, which provides a limited browsing capability on low-end phones.[10][11] Presto was last updated in 2015,[12] but is considered Maintained here because of its usage. /wiki/Flagship ↩

13. In 2013, Opera replaced the Presto engine with Blink for its flagship desktop and mobile browser. But it still has a special niche usage of Presto as a server-side renderer for the Opera Mini browser, which provides a limited browsing capability on low-end phones.[10][11] Presto was last updated in 2015,[12] but is considered Maintained here because of its usage. /wiki/Flagship ↩

14. "Flow Preview Builds". Ekioh. Retrieved 5 November 2023. Flow's goal is to render every website correctly... but there is currently a long way left to go. https://support.ekioh.com/download/ ↩

15. "About Ekioh". Ekioh. https://www.ekioh.com/company/ ↩

16. "Flow Browser". Ekioh. https://www.ekioh.com/flow-browser/ ↩

17. Servo has the goal of being a viable alternative to the major engines. However, there is still a lot of work to be done,[16] so it is Maintained status here. ↩

18. "A new browser for Magic Leap". 3 December 2018. Retrieved 20 May 2019. https://blog.mozvr.com/a-new-browser-for-magic-leap/ ↩

19. "Firefox Reality for HoloLens 2". 21 May 2020. Retrieved 17 July 2020. https://blog.mozvr.com/firefox-reality-hololens/ ↩

20. NetSurf does not fully support HTML5 or other recent Web standards,[19][20] which means it cannot work properly on YouTube, Gmail, and many other popular websites. Thus it does not merit Active status per this article's criteria. /wiki/HTML5 ↩

21. "NetSurf Developer page". Netsurf-browser.org. Retrieved 7 February 2019. http://www.netsurf-browser.org/developers/ ↩

22. "NetSurf web browser homepage". Netsurf-browser.org. Retrieved 7 February 2019. http://www.netsurf-browser.org/ ↩

23. LibWeb will not be ready for real browsing until at least 2026.[23][24] Thus it does not merit Active status per this article's criteria. ↩

24. Kling, Andreas (1 July 2024). "Announcing the Ladybird Browser Initiative". ladybird.org. https://ladybird.org/posts/announcement/ ↩

25. Andreas Kling (September 2022). "Ladybird: A new cross-platform browser project". Please note that we're still early in development, and many web platform features are missing or broken. It's going to take a long time before Ladybird is ready for day-to-day browsing. https://awesomekling.github.io/Ladybird-a-new-cross-platform-browser-project/ ↩

26. "KHTML repository". GitHub. Retrieved 5 May 2023. Removed for KF6, the 'kf5' branch contains the last maintained state. https://github.com/KDE/khtml/tree/6d89b39ddb93aa5b655508c0b5295f3f4db626b8 ↩

27. "Port Konqueror away from KHTML". phabricator.kde.org. Retrieved 5 May 2023. https://phabricator.kde.org/T11543 ↩

28. Active status means that new Web standards continue to be added to the engine, which properly renders the vast majority of websites, including multimedia. However, Maintained status can be as minimal as ensuring the engine code still compiles; this includes relatively new engines that are not yet robust enough to be Active here. Discontinued is when the engine code is abandoned. /wiki/Web_standards ↩

29. "Open-sourcing Chrome on iOS!". 2017. Retrieved 26 April 2021. Due to constraints of the iOS platform, all browsers must be built on top of the WebKit rendering engine. https://blog.chromium.org/2017/01/open-sourcing-chrome-on-ios.html ↩

30. Must be built from source code. ↩

31. Only available through QtWebEngine. /wiki/QtWebEngine ↩

32. "#1829 Restore Mac OS X code and buildability". 31 March 2022. Archived from the original on 6 May 2022. https://repo.palemoon.org/MoonchildProductions/UXP/issues/1829 ↩

33. "Pale Moon for Android is dead". forum.palemoon.org. April 2019. Retrieved 4 May 2021. https://forum.palemoon.org/viewtopic.php?f=39&t=14723&start=20#p165642 ↩

34. "Bug 288705: [HDR] Enable SupportHDRDisplay feature by default". Webkit Team. 28 February 2025. Retrieved 21 March 2025. https://bugs.webkit.org/show_bug.cgi?id=288705 ↩

35. "Bug 288705: [HDR] Enable SupportHDRDisplay feature by default". Webkit Team. 28 February 2025. Retrieved 21 March 2025. https://bugs.webkit.org/show_bug.cgi?id=288705 ↩

36. "Bug 288705: [HDR] Enable SupportHDRDisplay feature by default". Webkit Team. 28 February 2025. Retrieved 21 March 2025. https://bugs.webkit.org/show_bug.cgi?id=288705 ↩

37. "Bug 288705: [HDR] Enable SupportHDRDisplay feature by default". Webkit Team. 28 February 2025. Retrieved 21 March 2025. https://bugs.webkit.org/show_bug.cgi?id=288705 ↩

38. "Google kills forthcoming JPEG XL image format in Chromium". The Register. 31 October 2022. Retrieved 7 August 2023. https://www.theregister.com/2022/10/31/jpeg_xl_axed_chrome/ ↩

39. Purdy, Kevin (17 April 2023). "FSF: Chrome's JPEG XL killing shows how the web works under browser hegemony". Ars Technica. Retrieved 16 February 2024. https://arstechnica.com/gadgets/2023/04/free-software-group-decries-google-dropping-space-saving-jpeg-xl-format/ ↩

40. "WebGPU Implementation Status". GitHub. Retrieved 14 March 2024. https://github.com/gpuweb/gpuweb/wiki/Implementation-Status ↩

41. "Chrome ships WebGPU". developer.chrome.com. Google. Retrieved 23 February 2024. https://developer.chrome.com/blog/webgpu-release/ ↩

42. "Pale Moon - Release Notes". 21 March 2023. https://www.palemoon.org/releasenotes.shtml ↩