About the web app

The Pexip web app is automatically available as part of all Pexip Infinity deployments. It provides a WebRTC interface to Pexip Infinity conferencing services.

The web app is supported in the following browsers. We strongly recommend using the latest publicly-released version (i.e. "stable version" or "supported release") of a browser, and while we aim to support all recent versions of the browser, support is guaranteed only against the latest versions available at the time of release, as follows:

  • Google Chrome version 138 and later (64-bit only) on Windows, Linux, macOS, iOS*, and Android*
  • Mozilla Firefox version 140 and later on Windows, Linux, macOS, and iOS*
  • Microsoft Edge version 138 and later (64-bit only) on Windows and iOS*
  • Apple Safari version 18 and later on macOS and iOS*

* For the best experience on mobile devices, we recommend using the Pexip app for mobile.

Web app versions

The latest Pexip web app version is Webapp3. Earlier versions are no longer under active development.

Language support

The web app natively supports over 20 of the most popular languages. If the user's browser is set to use any one of these supported languages, it will use that automatically instead of the default English. Users can also change the language from within the Settings > Languages option in the web app itself. Alternatively, users can view the web app in any of the supported languages by appending the appropriate language code to the end of the URL.

Administrators can add additional languages using branding and customization.

Administrators can restrict which languages are supported via the availableLanguages setting in the manifest file. When this option is specified, if a user's browser is set to use a language not included in the availableLanguages list, the default en.json is used. Additionally, the languages available to users from within the Settings > Languages menu is restricted to only those specified in the availableLanguages list. This option can be used if, for example, administrators edit their language files to use specific terminology and want to limit the number of language files they need to maintain.

The web app currently supports the following languages:

Code Native name English name
ar اللغة العربية Arabic
en English English
cs Česky Czech
cy Cymraeg Welsh
da Dansk Danish
de Deutsch German
es-ES Español Spanish (Spain)
es-US Español de Ustados Unidos Spanish (Americas)
fi Suomi Finnish
fr-CA Français (Canadien) French (Canada)
fr-FR Français French (France)
ga Gaeilge Irish
he עִבְרִית Hebrew
id Bahasa Indonesia Indonesian
it Italiano Italian
ja 日本語 Japanese
ko 한국어 Korean
nb Norsk (bokmål) Norwegian (Bokmål)
nl Nederlands Dutch
pl Polski Polish
pt-BR Português Portuguese (Brazil)
sv Svenska Swedish
th ภาษาไทย Thai
vi Tiếng Việt Vietnamese
zh-Hans 简体中文 Chinese (Simplified)
zh-Hant 繁體中文 Chinese (Traditional)

Accessing a conference or making a call

To access a conference or make a call using the web app, users enter into their browser's address bar the IP address or domain name of their nearest Conferencing Node or reverse proxy.

System administrators and conference organizers can also provide a preconfigured link to a meeting, with one or more options (such as the meeting name) already configured.

Support for first-time and infrequent users

The web app offers two different joining flows with different levels of assistance for participants. The same meeting can be joined by participants using either flow.

  • Express flow (frequent users): by default, users' names are remembered and they are simply asked to enter the Meeting ID (if not already included in the URL), which is the alias of the conference or person they want to call. They then get the opportunity to check their setup (camera, microphone and speakers) before selecting Join.

    This flow is aimed at users who are familiar with the web app, are frequent users, and want to join a meeting quickly.

  • Step-by-step flow (infrequent / guest users): for occasional or less experienced users who might require assistance with selecting and checking their camera, microphone and speakers, you can include role=guest in the URL you give them to join the meeting. This offers them an alternative join flow that takes them through the setup of their camera, microphone and speakers before they are able to Join the meeting. For more information, see Creating preconfigured links to launch conferences via Pexip apps.

    This flow is designed for participants who might be using the web app for the first time or infrequently, and who might require some guidance. It also provides users who can't see, speak or hear with the opportunity to enable further support.

To enable the "step-by-step" flow for a participant, include role=guest within the URL that you provide them with to join the meeting. All other participants who join the meeting using a URL that does not include this parameter will join using the "express" flow. For more information, see Links to a specific meeting with additional parameters included.

Enabling access for external users

If your Pexip Infinity deployment is located inside a private network and you want to allow Pexip app users who are located outside your network to connect to your deployment, see Setting up DNS records and firewalls for Pexip apps connectivity.

Hardware requirements

The performance of the app typically depends on a combination of factors including the choice of browser, which other applications are currently running on the device, and the device's GPU and CPU specifications.

We recommend that your client device has a minimum of 8 GB of RAM in addition to that required by other applications.

In addition, note that use of background effects (blur and replacement) incur a significant local processing overhead which could affect the performance of your device.

User guide

See Using the Pexip web app.