Skip to main content

Browser-Based Content Display

In some scenarios, it’s more convenient to showcase content directly within a browser window instead of utilizing a full-fledged application.
Together with this option Wallboard also offers the ability to embed content displays seamlessly into an iFrame, making it easier to integrate with third-party solutions or websites.
A content preview opened in a browser stops after 15 minutes, so for continuous display you need one of the two methods below.

To address these requirements, there are two primary methods available for displaying or embedding Wallboard content in a browser.

Browser Client or Browser Session?
  • Browser Client is a fully fledged Device that runs in a browser. You register it like any other player and assign Content to it the usual way.
  • Browser Session is not a Device. It is a secure URL generated from one Content, which you can open in any supported browser.

Browser Client​

Overview​

The Browser Client application offers a more robust solution by functioning as a fully integrated client, similar to a registered device. This client can run directly in the browser, making it more versatile for setups that require device tracking, offline capabilities, and interaction with other devices.

Use Case​

  • Full device management capabilities, similar to traditional device clients.
  • Environments where you need to manage settings, content schedules, or channel interactions.
  • Scenarios where offline capability is necessary, making it ideal for low-connectivity areas.
  • When integration with other devices or more complex configurations is needed.
  • Cross-platform compatibility across desktops, laptops, and mobile devices.
  • No installation requirements, making it easy to deploy and update.

How to Use It​

The Browser Client can be used similarly to a Browser Session but offers added functionality. Simply follow the instructions in the Browser Client Guide. It’s compatible with a wide range of devices and doesn’t require a separate app to operate.

For a full list of supported functions by our Browser Client please refer to our Client platform comparison chart article.

Browser Client or Wallboard Lite?
  • Browser Client runs in any Chromium browser (version 71+) on desktops, laptops and mobile devices. You open its URL from Settings > Downloads and install it from the browser. Learn more: About our Browser Client
  • Wallboard Lite is an Android app from the Google Play Store (Android 7.0+) that runs the Browser Client inside the app and can be set as the device's home application, so it starts with the device. Learn more: About Wallboard Lite

Both register as a Device with a 4-digit code. For what each one supports, compare the Browser Client and Wallboard Lite columns of the comparison chart.

Simple Browser Session Display​

Overview​

A Browser Session is ideal if you want to quickly display content in a browser without needing advanced functionality or persistent state management. This method is perfect for one-off displays or simple setups that don’t require device registration or long-term management.

Use Case​

  • Short-term content display without needing to track or manage the device.
  • Environments where persistent settings or offline capabilities are not required.
  • Quick and simple setup with minimal configuration.

How to Use It​

To use a Browser Session, follow these steps:

  1. Make sure your customer has Browser session licenses — these are assigned by a server administrator.

  2. Navigate to the content you want to display, open its settings and select Browser signage url.

    browser-signage-url.png

  3. Copy the Browser signage url (or the shorter Browser signage short url) and open it in any Chromium-based browser.

Security Note

Each browser signage URL contains a unique signageModeSecret parameter, ensuring security. If necessary, click Reset to generate a new URL for the same content. The previously generated URL stops working.

copy-url.png

Now your content is running in signage mode, without the 15-minute preview limit.

To see and manage the browser sessions that are running, use the Browser Sessions page.

Limitations​

Browser signage display requires an online connection. If the device is offline, or the session limit is reached (see below), it shows a Content cannot be displayed screen.

signageURL-error.png

Please note

Additionally, note that browser signage may still be subject to limitations, such as Chrome’s Autoplay Policy, which may prevent certain media from playing automatically.

Therefore, browser signage URLs in certain browsers may not play automatically.

To ensure that browser signage URLs play in your local browser at any time please check your browser settings accordingly

Concurrent Content Limit
The concurrent content limit (the Browser session limit) controls how many screens can display content at the same time.

There may be circumstances where you want to limit the number of browser sessions that can run under a particular client. For example, if you have four devices, you might want to permit only four active sessions at any given time. This measure helps safeguard against unauthorized personnel accessing extra valuable sessions.

Important

This limitation can only be set on customer portals by server administrators.

If the limit is reached, any additional device trying to connect shows the Content cannot be displayed screen shown above, with the session limit as the reason.

Important

This feature requires devices to be online to verify if the limit has been reached. If a device is offline, it will show the overlay message as it cannot validate the session count.

Showing external websites​

This article is about showing Wallboard Content in a browser. Embedding works the other way around: it shows an external website inside your Wallboard Content, through the Custom widget. If that is what you need, see:

Separate webview does not work in a browser

Use separate webview needs a native player. In a browser preview, a Browser Session and the Browser Client, the website is shown in a regular iFrame instead, so a site that refuses embedding stays blank.

Version notes​

Many servers still run older versions, so these milestones are worth knowing:

  • Server 1.9: the 15-minute limit on content previews opened in a browser is introduced.
  • Server 1.10: the concurrent content limit (Browser session limit) is introduced.
  • Server 1.12: the Browser Client is officially launched.