Google Chrome and Chromium have several differences. For example, they support the different set of audio and video codecs:


Google Chrome Chromium
AAC, H.264, MP3, MP4, Opus, Theora, Vorbis, VP8, VP9, and WAV Opus, Theora, Vorbis, VP8, VP9, and WAV


As you may see Google Chrome supports H.264, MP3, and MP4 codecs when Chromium doesn't. The reason is that these codecs are proprietary and cannot be used in open-source and commercial projects by default. To get the rights to use the codecs, companies must pay a royalty fee to the patent holders. Different codecs have different patent holders. For example, in order to use H.264 codec, companies must acquire the licence from MPEG-LA company. You can read more about their license terms on the MPEG-LA's website.


DotNetBrowser & Proprietary Codecs


Patent holders don't license codecs to the software that represents only a part of the final product deployed to the end users (e.g. libraries, such as DotNetBrowser). In order to introduce an ability to support H.264, MP3, MP4 and other proprietary codecs in your products, you need to acquire the appropriate licences.


What should I do?


If you need to play MP3, MP4, and H.264 formats on the web pages loaded in DotNetBrowser, you can perform the following actions:

  • Contact the patent holder (e.g. MPEG-LA) and obtain licence to use the proprietary codecs you need.
  • Contact our Sales team at sales@teamdev.com and request a custom build of DotNetBrowser with enabled proprietary codecs.
  • With the licence and custom DotNetBrowser build, you will be able to load web pages with MP3, MP4, and H.264 formats and play audio and video files, just like in Google Chrome.