System requirements
  • We continually review the minimum requirements to run Webex App, and the requirements listed here may change.
  • We don't support using Webex App with pre-release or early release programs, such as the Apple Beta Software, Windows Insider Program, or any other similar programs.
  • The performance of Webex App can be influenced by factors beyond the operating system, for example: network connectivity or other applications on your devices.

Windows desktop minimum requirements

Mac desktop minimum requirements

  • MacOS 10.13 and later.

  • M1 chip or Intel CPU-based

  • Minimum 4 GB RAM

Download the installer

Install Webex

This article is about installing the desktop version of Webex App for Mac or Windows. For Linux, see Webex App for Linux.

Webex App installs to the same system folder every time it updates to a new version.

To find the installed version of Webex App, see Find your App version.

Administrators can check what version of the app their users have by running the Messaging App Version Report, see Reports for your Cloud Collaboration portfolio.

Manual install

You can install Webex App either per computer or per user. Either the users of an IT administrator can install it.

Webex App installs to the following folder by default: %LocalAppData%\Programs\Cisco Spark.

Users can download and then run the installer file (msi). They don't need administrator access privileges on their computer.

Administrators can run the installer with extra privileges and can choose per computer installation and the installation directory.

Which MSI install package should I use?

These are the differences between the packages:

  • Localized or non-localized package: Users can choose a localized package if they want Webex App to install in the language of their operating system.

    As an administrator doing a bulk install with a third-party distribution mechanism, you must deploy a non-localized package. Users can still use Webex App in their preferred language (if Webex supports that language).

    If you bulk install Webex App with a localized package, you may have trouble when uninstalling Webex App.

  • App only package: You can choose this option in most situations. The package installs only Webex App. Webex App downloads the desktop meeting app components if necessary.

    There are some exceptions when you may need the bundle instead.

  • Bundle package: This package installs both Webex App and the desktop meetings app. Only use the bundle package in the following situations:

    • You’re installing in a secure environment that blocks the users' computers from downloading software. If Webex App can't download meetings components, people may have usability problems joining meetings with the app.
    • You haven’t yet fully migrated to Webex App and your users still need the separate desktopMeetings app.
Table 1. Webex App install packages for Windows
DescriptionIs localized?OS architectureInstall package download link
Webex App onlyLocalized64 bit https://binaries.webex.com/WebexOfclDesktop-Win-64-Gold/Webex.msi
Webex App onlyNon-localized (EN)64 bit https://binaries.webex.com/WebexTeamsDesktop-Windows-Gold/Webex_en.msi
Webex App and desktop meetings bundleLocalized64 bit https://binaries.webex.com/Webex-Desktop-Windows-x64-Combined-Gold/WebexBundle.msi
Webex App and desktop meetings bundleNon-localized (EN)64 bit https://binaries.webex.com/Webex-Desktop-Windows-x64-Combined-Gold/WebexBundle_en.msi

Bulk install

Examples here use the msiexec utility from Microsoft. See https://docs.microsoft.com/en-us/windows/win32/msi/using-windows-installer for more details.

These are the command-line parameters you can use with a Webex App MSI install package:

  • Installation context

    When you set ALLUSERS=1 to specify a per computer installation, you must have administration access privileges. See https://docs.microsoft.com/en-us/windows/win32/msi/allusers for more details.

  • Silent installation

    You can include /qn to install without user interaction. For example: msiexec /i c:\work\Webex.msi /qn.

  • ACCEPT_EULA

    Set this property TRUE to accept the end-user license agreement on behalf of users. The installer doesn't prompt users to accept the end-user license agreement.

    For example: msiexec /i c:\work\Webex.msi ACCEPT_EULA=TRUE ALLUSERS=1.

    The end-user license agreement doesn't appear when you set either of the following registry entries to eula-disabled:

    • HKEY_LOCAL_MACHINE\Software\CiscoCollabHost\Eula Setting

    • HKEY_LOCAL_MACHINE\Software\WOW6432Node\CiscoCollabHost\Eula Setting

  • AUTOSTART_WITH_WINDOWS

    Specifies whether Webex App automatically runs when Windows starts up.

    The default value is TRUE. You need administrative privileges to change it.

    Examples:

    • msiexec /i c:\work\Webex.msi AUTOSTART_WITH_WINDOWS=true ALLUSERS=1

      Webex App automatically starts when Windows starts up (default). This setting enables and grays out the Start Webex when my computer starts control, so the user can't change it.

    • msiexec /i c:\work\Webex.msi AUTOSTART_WITH_WINDOWS=false ALLUSERS=1

      Webex App doesn't automatically start with Windows. Users can change Start Webex when my computer starts in the Webex App settings.

  • DEFAULT_THEME

    Specifies the theme used for the Webex App.

    The default value is Dark. You need administrative privileges to change it.

    Users can change the theme in Webex settings.

    Examples:

    • msiexec /i c:\work\Webex.msi DEFAULT_THEME="Light" ALLUSERS=1

      Specifies the light theme for Webex App.

    • msiexec /i c:\work\Webex.msi DEFAULT_THEME="Dark" ALLUSERS=1

      Specifies the dark theme for Webex App.

  • DELETEUSERDATA

    Specifies whether to delete or retain user database and log files.

    The default value is 0 which retains the database and logs during install.

    Examples:

    • msiexec /i c:\work\Webex.msi DELETEUSERDATA=1 ALLUSERS=1

      Removes user database and logs during install.

  • EMAIL

    This parameter allows you to streamline the Webex App sign-in process for users by specifying their email address or a pattern that indicates how to derive the email address.

    For example: msiexec /i c:\work\Webex.msi EMAIL=acassidy@example.com prepopulates acassidy@example.com into the Webex sign-in flow.

    You can use the following values with the EMAIL parameter:

    • User's email address (example: acassidy@example.com)—Sets an actual email address to prepopulate the sign-in flow. Don't use with the ALLUSERS=1 parameter because it represents just one email address. This isn't recommended for devices that have multiple users.

      For example: msiexec /i Webex.msi EMAIL=$acassidy@example.com

    • $userPrincipalName—Instructs Webex to retrieve the user's User Principal Name (UPN) from Windows at the time of sign in. You can use this for devices with multiple users.

      For example: msiexec /i Webex.msi EMAIL=$userPrincipalName ALLUSERS=1

    • $mail—Instructs Webex to retrieve the user's email address, if available, from LDAP/Active Directory at the time of sign in. You can use this for devices with multiple users.

      For example: msiexec /i Webex.msi EMAIL=$mail ALLUSERS=1

    • $SAMAccountName—Instructs Webex to retrieve the user's SAMAccountName from Windows at the time of sign in. This is typically used for legacy environments. You can use this for devices with multiple users.

      For example: msiexec /i Webex.msi EMAIL=$SAMAccountName ALLUSERS=1

    Combining the EMAIL parameter with an authentication method, such as Kerberos or mTLS, allows users to sign in automatically.

    When you use the EMAIL parameter, users can't change the Webex identity they use to sign in.

  • ENABLEOUTLOOKINTEGRATION

    Specifies whether Webex App registers with Microsoft Outlook for presence integration. You need administrative privileges to change it.

    The default value is 0.

    Examples:

    • msiexec /i c:\work\Webex.msi ENABLEOUTLOOKINTEGRATION=1 ALLUSERS=1

      Webex App registers with Microsoft Outlook for presence integration on Windows.

      Users can change Connect Webex to Microsoft Outlook in Webex settings.

    • msiexec /i c:\work\Webex.msi ENABLEOUTLOOKINTEGRATION=0 ALLUSERS=1

      Webex App doesn’t register with Microsoft Outlook for presence integration on Windows (default).

      This setting grays out (disables) the Connect Webex to Microsoft Outlook control for all users. You must have administration access privileges to change this option.

  • FORCELOCKDOWN

    Applies only to the bundle install packages. Locks the meetings desktop app if it’s a compatible version with the meeting site. You need administrative privileges to change it.

    Example: msiexec /i WebexBundle.msi FORCELOCKDOWN=LockWhenCompatible

  • INSTALL_ROOT

    Specifies the install folder for the Webex App.

    Example: msiexec /i c:\work\Webex.msi INSTALL_ROOT="C:\Program Files" ALLUSERS=1

  • INSTALLWV2

    Installs the WebView2 embedded browser from Microsoft when installing Webex App.

    Webex App requires this embedded browser. Learn more about WebView2 and Webex.

    Example: msiexec /i c:\work\Webex.msi INSTALLWV2=1

  • FORCECLIENTSPCOMPATIBLEVERSIONNO

    Applies only to the bundle install packages. This parameter extends the Webex Meeting client version to be compatible with the meeting site. Webex Meeting client gets a version number that is greater among the ClientSPCompatibleVersionNo or ForceClientSPCompatibleVersionNo. You need administrative privileges to change it.

    For example: msiexec /i WebexBundle.msi FORCECLIENTSPCOMPATIBLEVERSIONNO=10

Running the app

Webex App has its own automatic update solution that is independent from the Windows operating system. The app can automatically update without the knowledge of the Windows operating system, so the installed version of the app may be different from the version the user sees while using the app.

Installing

To install Webex App, users don't need to have administrator access privileges on their computers.

Users double-click the Webex.dmg file to install it. By default, you install Webex App in the Applications folder, however users can drag and drop Webex App to any other directory.

To check the installed version of Webex App, see Find Your App Version.

Administrators can check what version of the app their users have by running the Messaging App Version Report, see Reports for your Cloud Collaboration portfolio.

Bulk install

As an administrator, you can use the Mac defaults command with the LoginHint argument to prepopulate Webex App with the user's email:

defaults write Cisco-Systems.Spark LoginHint -string "<user-email@example.com>"

In this command, user email serves as a login hint to autoadvance to password entry screen, post app install and launch. To restrict the login with specific domains or emails, the user email should be a part of the registry.

Location: HKEY_CURRENT_USER/Software/Cisco Spark Native/Params

Parameter key: email

To disable the prepopulating, use the following command:

defaults delete Cisco-Systems.Spark LoginHint

Audio driver to share computer audio

Webex App needs a special audio driver to share the computer audio. Administrators can preinstall the drivers on the end-user computers. Refer to Cisco Webex Audio Driver Package Download for Mac for instructions.

If the users don't have the driver installed, then Webex App downloads it when you click Optimize for motion and video or Share your computer audio in Webex App. But the user must have administator permission to install the driver.

Running the app

The app has its own autoupdate solution, independent from the operating system's installation mechanism. You only install the app once using the operating system mechanism. After that, the app automatically updates without the knowledge of the operating system. Therefore, the installed version of the app might be a different version than the one you see while using the app.

Update process

A new release takes 7 days to roll out to everyone. During those 7 days, users can proactively check for updates. Users can read Update the app to the latest release.

We automatically apply the update after the 7 days rollout window.

If you have Pro Pack for Control Hub, you can check what version of the app your users are on. See the Messaging App Version Report in Analytics for your cloud collaboration portfolio.

When Webex App is running1, it periodically checks to see if there’s a newer version of the app available. When a newer version becomes available, the app automatically downloads the new version and stores it on the local computer:

  • On Windows:

    C:\Users\<username>\AppData\Local\CiscoSparkLauncher

    C:\Users\<username>\AppData\Local\CiscoSpark

    C:\Users\<username>\AppData\LocalLow\WebEx

    C:\Users\<username>\AppData\Local\WebEx

  • On MacOS:

    ~/Library/Application Support/Cisco Spark

We store the current version and the new version of the application in these folders. If the upgrade doesn't work out, then the app can fall back.

If we release a patch for a release, we update all organizations within a three-day rollout window.

  1. Webex App checks for updates while it’s running, even if the user is not signed in.

    If the user is not signed in when an update is possible, the update behavior depends on who was last using Webex App:

    • If that user was signed in, the app updates itself according to the update policy of their organization. See Product update controls.
    • If that user didn’t sign in, the app updates itself to the latest version. (They could be using Webex App to join meetings as a guest).
Administrator controls to manage releases
Uninstall the Webex App

To uninstall the app use msiexec /x Webex.msi.

The path of the .msi file depends on where it was used during installation. For this command to work, the .msi file must be present in the specified location.

To uninstall Webex App, go to the Applications folder and drag Webex App to the trash.

Deployment for Virtual Desktop Infrastructure (VDI)
Deploy Webex App on mobiles

As an administrator you can secure the Webex App app on your user's mobile devices. The solutions we support include MDM/MAM with Microsoft Intune, MDM/MAM with AppConfig, app wrapping using the iOS IPA files and the Android AAB files, and admin controls for mobile management

For more information, see Secure mobile devices.