Get started with the Meeting SDK for Android

Beginning March 2 2026, apps joining meetings outside their account must be authorized. Authorize apps by using either ZAK or OBF tokens, or RTMS. Learn more.

The code on this page works with either the default UI or the custom UI.

Explore the Meeting SDK by running the sample Android apps that Zoom has built for you to test out the features in the Android SDK.

Prerequisites

See the Changelog for the latest supported Meeting SDK version. See our Minimum version policy for the minimum supported SDK version.

Requirements for external meeting access

To join meetings outside of your developer account, your app must:

Be reviewed by Zoom.

Authenticate with either a ZAK or On Behalf Of (OBF) token to attribute to a user in a meeting.

You can:

Publish the approved app on the Zoom App Marketplace.

Set your app to unlisted.

Contact the Integrated Software Vendor (ISV) sales team for other options.

Android Studio.
SDK Key and Secret, obtained by creating an SDK app.

Device or emulator

OS: Android 8.0 or later.
Supported Android devices: phones and tablets. TVs, box and Chromebooks are not supported.
Supported architectures: arm64-v8a or armeabi-v7a.
NDK: 27 and above.

Project and Gradle settings

Android Project
compileSdkVersion: 35
buildToolsVersion: 35
minSdkVersion: 28
targetSdkVersion: 35

Note: If you select minSdkVersion 26 or later as your minSDKVersion, reduce your app size by including android:extractNativeLibs="true" in your AndroidManifest.xml.

Required permissions

Depending on the features you add to the Meeting SDK, your app may require the same permissions as the Zoom client. Refer to the ZOOM Cloud Meetings Android app in the Google Play store for a list of permissions required by the Zoom client. See Change app permissions on your Android phone and the Permissions on Android Developer documentation for more information about permissions.

Download the Meeting SDK for Android

To access the SDK download files, you must be logged in to your Zoom App Marketplace developer account, and you need at least one app registered on the Zoom App Marketplace.

If you don't already have at least one registered app, follow these steps to create an app and download the SDK files.

Sign in to your developer account on the [Zoom App Marketplace](https://marketplace.zoom.us/?ampDeviceId=cf401538-835f-45ce-a7f1-1035e348c982&SessionId=1771892802618).
Select **Develop > Build App > General app**, and then select **Create**.
Go to **Features** and select **Embed**.
On the **Embed** page, enable **Meeting SDK**.
Under the **Meeting SDK** section, configure the settings as appropriate for your app.
To download the SDK files, select the platform **Android**. This page displays available SDK versions for the selected platform, along with links to their corresponding release notes.
Finally, select the **Download** button.

If you already have at least one registered app, follow these steps to download the SDK files using your existing app.

Sign in to your developer account on the [Zoom App Marketplace](https://marketplace.zoom.us/?ampDeviceId=cf401538-835f-45ce-a7f1-1035e348c982&SessionId=1771892802618).
Select **Manage**, and open your SDK app.
Go to **Features** and select **Embed**.
On the **Embed** page, go to the **Meeting SDK** section.
To download the SDK files, select the platform **Android**. This page displays available SDK versions for the selected platform, along with links to their corresponding release notes.
Finally, select the **Download** button.

Verify the download files

Your downloaded file should contain these files in the following file structure:

.
├── CHANGELOG.md
├── OSS-LICENSE.pdf
├── README.md
├── mobilertc-android-studio &lt;- Libraries and examples are inside.
├── proguard.cfg
└── version.txt

Inside the folder mobilertc-android-studio, you can find the regular sample app, as well as a sample app demonstrating dynamic loading of the library.

Find the version number

In the downloaded files, find the file version.txt. The number inside that file is the version number of the SDK that you downloaded.

Include the version number whenever you post a question or get support on our community forum.

Load the project

Android Studio

If you don't have Android Studio installed, go to https://developer.android.com/studio/ to download.

Launch Android Studio and load the project by selecting Open an existing Android Studio project. Navigate to the folder where you stored the package you just downloaded, go into the folder mobilertc-android-studio, then press Open.

Android Studio will typically try to sync the Gradle scripts automatically. To sync them manually, press File > Sync project with Gradle files.

Once the project is fully loaded, you will see three demo folders, named dynamic_sample, sample, and example2.

We provide three different examples for you.

sample - An Android app that has all basic features for both login users and non-login users.
example2 - An Android app that shows how to join meetings without any login credentials.
dynamic_sample - An Android app that shows how to load the Meeting SDK feature module on-demand, to give you a small install package. This is achieved using SplitInstallManager. To learn more about on demand modules, refer to the Android doc Configure on demand delivery. To fully test this function, upload the dynamic_sample app to Google Play.

Next, focus on the sample project.

Logged in user and non-logged in user

Logged in user - A user who logs in with Zoom credentials. Logged in users can start a scheduled meeting, start an instant meeting, manage Meetings, and more. While in the meeting, the display name will show the logged in user's name.

Non-logged in user - Can join or start a scheduled meeting without needing Zoom credentials. Some functions are not available for non-logged users.

Visit Account & User for detailed information.

Use the custom meeting UI

To have your own "decorations" in the video conferencing room, use our Custom Meeting UI option. Try our custom UI interfaces as shown in the sample app to get some feeling for how our custom UI works.

For further information regarding development, please refer to our later section.