There are two web page objects in Premium, based on Chromium / Chrome and Internet Explorer. 

You may create web page objects in both Composer and Portal.



Is the default web page object. Uses Chromium Embedded Framework and is similar to Chrome in functionality. Web pages created in Composer and in Portal use the Chromium-based web page object.

User agent

Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.0 Safari/537.36

HTML5 test results

513 out of 555.


  • Transparency option for the web page
    Make the background of web page page transparent
  • Hide errors from screen
    Will show transparent or black instead of showing the web load error.
  • Scroll page
    Option to automatically scroll the page
  • Option to scale websites
  • Page reload interval setting
  • Option to hide scrollbars
  • Mouse & keyboard input
    Please note that if a keyboard is connected this could be used to control and exit the player!
  • Touch support on touch screen devices
  • URL can be data connected
  • Secure HTTPS link support
    Certificates will not be checked for errors.
  • Local proxy configuration in Windows is used automatically.
  • Uses a separate cache folder for each webpage object.
    The cache stores cookies and downloaded content.
  • Web pages are rendered isolated from the system - they can't interact with the Windows operating system or logged in user.

Good to know / limitations

  • MP4 H.264 video is not supported
  • MP3 audio is not supported
  • Not all streaming formats are supported
  • DRM protected video streaming is not supported
  • WebGL is not supported
  • Web page display is limited to system memory
    CEF will use both system and graphic card memory for render and if a page will use more memory than available in the system rendering will be aborted.

Internet Explorer-based

Uses the Internet Explorer version installed on the player PC. The IE based web page object has to be created in Composer.

User agent

On Windows 10 as of 2018-03-20
Mozilla/5.0 (Windows NT 6.2; WOW64; Tident/7.0; rv:11.0) like Gecko

HTML5 test results

312 out of 555.
(Link unavailable due to lack of touch)


  • Website zoom
  • You can make websites (background) Transparent as well as make them Transparent on error
    Make the web page object transparent if the web page has an loading error.
  • Default is to render a single image of the web page. Live option for continuous render of web page (including FPS setting)
  • Page reload interval setting
  • Option to scroll page to a certain coordinate
  • Option to render page with fixed size and apply scaling
  • Option to set cookies for web page
  • Option for "Basic Authentication"
  • May be scripted to allow form login on certain sites
  • Secure HTTPS link support
    Page will not be displayed if certificates are not valid.
  • Local proxy configuration in Windows will be used automatically
  • One cache folder is used for all web pages loaded
    The cache stores cookies and downloaded content.
  • Web pages are rendered isolated from the system - they can't interact with the Windows operating system or logged in user.

Good to know / limitations

  • ActiveX and similar components are not supported and will not be rendered
  • Mouse, keyboard and touch input is not supported


Since Premium displays web pages in a separate browser the options for logging in to a page a limited.

Basic Authentication

If the web page is using Basic Authentication you can add the username and password to the URL like this:

Bypass authentication

For your own or third party web pages you can use any of these methods to bypass authentication

  1. Create a special URL that bypasses the login
  2. Use a token in the URL
  3. Bypass login if the request comes from a trusted IP or trusted VPN

Note that all of these methods require that changes are made to the web page / server in some way.

Other types of authentication

If you have no access or ability to change the web page to bypass authentication then there are a few options left

  1. Create your own page to display the web page in an IFrame and handle authentication using script
  2. Create a proxy that injects scripts into the web page to bypass authentication

In all of the above options we ask you to consult with the operator of the web page, because bypassing authentication may not be allowed or even penalised.