Webinar Technical Requirements

Last updated June 10, 2019

We’re often asked what the specific requirements are for a company or individual to attend a WorkCast Auditorium and view a live video stream. Here’s the low-down on all things technical:

What are the browser requirements?

The first point to note and one of the main features that puts us ahead of our competitors, is that there are NO WorkCast downloads or plugins. Our Auditoriums work across all major platforms, in all major browsers, using standard web based technologies. The experience will be tailored based on the viewers platform and features available within the viewers browser including HTML5, flash, and numerous other attributes.

The WorkCast Platform can be configured to deliver content using secure (HTTPS) or unsecure (HTTP) communication protocols. HTTPS requires TCP port 443 and HTTP requires TCP port 80 to be opened through your firewall for both inbound and outbound traffic.

As with most websites, there are certain browser options that must be enabled to allow full functionality and we’re no exception. In order to enable our full feature rich viewing and interactive experience, javascript must be enabled.

Cookie support is an added bonus to help enrich the experience but is not an essential.

Browser requirement summary:




WorkCast downloads and plugins


There are no WorkCast downloads or plugins

Secured Content

Firewall TCP Port 443


Unsecured Content

Firewall TCP Port 80






Optionally enabled

Enriches the experience


What are the stream requirements?

We offer multiple live video streaming formats and quality options, which vary by broadcast requirements, viewer platform, and viewer connection speed.

The stream formats we broadcast in and requirements for a viewer to receive each, are as follows:

Stream requirement summary:

Stream Format

Firewall TCP Ports (inbound and outbound)


rtmp (real time messaging protocol)

Any of the following:


NOTE: rtmp traffic must also be allowed through the firewall.

rtmpt (rtmp tunnelling)



Failover to bypass corporate traffic filtering if rtmp fails.

HLS (HTTP live streaming)



Mpeg-dash (dynamic adaptive streaming over HTTP)




That’s essentially it, concise and simple.

If in any doubt, don’t forget our test your connection page on:


Additional Articles

You may also be interested in: