An overview with minimal system requirements for the presenter and viewers of webinars.

Each presenter has their own connection to the webinar. The minimum required upload speed for broadcasting a webinar with WebinarGeek is about 250 kilobytes per second (equal to about 2 Mbps).

If you are connected to multiple presenters, you will also need a sufficient download speed, up to 100KBps (800Kbps). We automatically scale the reception down if that is necessary for your computer or your internet speed.

More important than the internet speed is the stability of your connection. To be able to videostream live, you need a stable connection. Preferably use a wired internet connection over Wi-Fi. If you do choose to use Wi-Fi, make sure to place yourself as close to the router as possible. If you are on a VPN network we recommend you to disconnect from your VPN to get more out of your connection.

The minimum required upload speed for the each presenter in a webinar with more than one presenter is about 250 kilobytes per second (2 Mbps).

For viewers, a minimum download speed of 60 kilobytes per second (equal to 0.5 Mbps) is required. WebinarGeek automatically adapts the quality of the webinar (up or down), depending on the available bandwidth and CPU power of the viewer.

You can test your internet connection speed here. Click on 'Start test' after loading and choose a nearby location. Make sure the (upload or download) speed in 'Mbps' is higher or equal to the indicated minimum speed requirements.

Streaming a live webinar will ask more from your computer than most other ‘regular’ computer tasks. For example, your computer has to process video and audio and make sure they’re in sync. Especially processing video and audio will ask a lot from your CPU/processor, and therefore we recommend to use a relatively new PC.

As a rule of thumb, for a computer to be deemed ‘modern enough’, we recommend the following:

WebinarGeek will generally work fine on even older computers, but if you’re experiencing any issues, using a newer computer is recommended. When testing or live broadcasting your webinar, we’ll measure how busy your computer is with processing the broadcast.

Always make sure that your computer is as powerful as possible with all other applications closed. The more powerful, the better (e.g. MacBook Pro over Air).

For presenting a webinar, you’ll need:

WebinarGeek has been tested on multiple operating systems:

For joining the stage during a webinar, you’ll need:

Webinars can also be viewed on mobile devices with:

Practically all browsers that have the ability to play a video stream allow viewers to join the webinar. For Android it’s required to follow the webinar using Google Chrome, which is standard software on Android 5.0 or higher.

You're able to see your current operating system on this page.

The following browsers are supported by WebinarGeek.

For an optimal experience, we recommend using the latest version of Google Chrome.

If you’re already using the Google Chrome browser, you can check your current version in the top right of your browser by clicking the three dots, and choosing 'Help' > 'About Google Chrome'.

As many browsers are built upon the same browser as Google Chrome (Chromium), you'll have the same experience using the latest version of Microsoft Edge, Vivaldi or Brave browsers if you don't want to use Chrome.

You can check this page which type of browser you’re currently using.

Practically all (virtual) cameras and microphones are supported for the presenter, as long as your browser is able to detect them as a compatible device. For the non-standard webcam, you’ll sometimes need additional hard- or software, such as Blackmagic Web Presenter, U-TAP or OBS. Cameras must have a minimum resolution of 1280x720 px.

Following a webinar is possible in all networks that allow visiting websites (without restrictions), as long as a stable connection is available.

WebinarGeek uses a variety of domains, IP addresses, ports, and protocols to host your webinar. If you are using a corporate network or VPN, it is wise to check these settings with your IT manager.

You'll need to make sure you can access the following domains:

Additionally, you'll want to make sure you can access *.daily.co on port 443, as it's used for a variety of fallback connection types.

If you have a firewall, you should allow UDP hole punching, which is essentially the standard behavior for most firewalls. If you're explicitly allowing or denying UDP ports, you'll definitely need to open port 3478 for signaling and media tunneling. You'll also need to open UDP ports 40000-65534 for all (co-)hosts in order for peer-to-peer calls to work correctly.

If you are required to use a VPN, webinars will have much better quality if WebinarGeek’s traffic is able to bypass it. You can usually do that by configuring split tunneling. Try to exempt all UDP traffic. If not possible, exempt port 433 for at least the Twilio IP ranges and ideally also for Xirsys.

Twilio's IP ranges: https://www.twilio.com/docs/stun-turn/regions

Xirsys's IP ranges: https://docs.xirsys.com/?pg=ip-whitelist

If you need to control access to resources with a Content-Security-Policy (CSP) header, use the following:

Keywords: systeemvereisten, specifications, mbit, livestream