livekit_client 1.5.3 icon indicating copy to clipboard operation
livekit_client: ^1.5.3 copied to clipboard

Flutter Client SDK for LiveKit. Build real-time video and audio into your apps. Supports iOS, Android, and Web.

pub package

LiveKit Flutter SDK #

Use this SDK to add real-time video, audio and data features to your Flutter app. By connecting to a self- or cloud-hosted LiveKit server, you can quickly build applications like interactive live streaming or video calls with just a few lines of code.

This package is published to as livekit_client.

Docs #

More Docs and guides are available at

Current supported features #

Feature Subscribe/Publish Simulcast Background audio Screen sharing End to End Encryption Multi Codec Simulcast
iOS 🟢 🟢 🟢 🟢 🟢 🟢
Android 🟢 🟢 🟢 🟢 🟢 🟢
Mac 🟢 🟢 🟢 🟢 🟢 🟢
Windows 🟢 🟢 🟢 🟢 🟢 🟢
Linux 🟢 🟢 🟢 🟢 🟢 🟢

🟢 = Available

🟡 = Coming soon (Work in progress)

🔴 = Not currently available (Possibly in the future)

Example app #

We built a multi-user conferencing app as an example in the example/ folder. You can join the same room from any supported LiveKit clients.

Installation #

Include this package to your pubspec.yaml

  livekit_client: <version>

iOS #

Camera and microphone usage need to be declared in your Info.plist file.

  <string>$(PRODUCT_NAME) uses your camera</string>
  <string>$(PRODUCT_NAME) uses your microphone</string>

Your application can still run the voice call when it is switched to the background if the background mode is enabled. Select the app target in Xcode, click the Capabilities tab, enable Background Modes, and check Audio, AirPlay, and Picture in Picture.

Your Info.plist should have the following entries.



Since xcode 14 no longer supports 32bit builds, and our latest version is based on libwebrtc m104+ the iOS framework no longer supports 32bit builds, we strongly recommend upgrading to flutter 3.3.0+. if you are using flutter 3.0.0 or below, there is a high chance that your flutter app cannot be compiled correctly due to the missing i386 and arm 32bit framework #132 #172.

You can try to modify your {projects_dir}/ios/Podfile to fix this issue.

post_install do |installer|
  installer.pods_project.targets.each do |target|

    target.build_configurations.each do |config|

      # Workaround for
      config.build_settings['ONLY_ACTIVE_ARCH'] = 'YES' # <= this line


For iOS, the minimum supported deployment target is 12.1. You will need to add the following to your Podfile.

platform :ios, '12.1'

You may need to delete Podfile.lock and re-run pod install after updating deployment target.

Android #

We require a set of permissions that need to be declared in your AppManifest.xml. These are required by Flutter WebRTC, which we depend on.

<manifest xmlns:android="" package="com.your.package">
  <uses-feature android:name="" />
  <uses-feature android:name="" />
  <uses-permission android:name="android.permission.CAMERA" />
  <uses-permission android:name="android.permission.RECORD_AUDIO" />
  <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
  <uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
  <uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
  <uses-permission android:name="android.permission.BLUETOOTH" android:maxSdkVersion="30" />
  <uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />
  <uses-permission android:name="android.permission.BLUETOOTH_ADMIN" android:maxSdkVersion="30" />

For using the bluetooth headset correctly on the android device, you need to add permission_handler to your project. And call the following code after launching your app for the first time.

import 'package:permission_handler/permission_handler.dart';

Future<void> _checkPermissions() async {
  var status = await Permission.bluetooth.request();
  if (status.isPermanentlyDenied) {
    print('Bluetooth Permission disabled');
  status = await Permission.bluetoothConnect.request();
  if (status.isPermanentlyDenied) {
    print('Bluetooth Connect Permission disabled');

void main() async {
  await _checkPermissions();

Audio Modes

By default, we use the communication audio mode on Android which works best for two-way voice communication.

If your app is media playback oriented and does not need the use of the device's microphone, you can use the media audio mode which will provide better audio quality.

import 'package:flutter_webrtc/flutter_webrtc.dart' as webrtc;

Future<void> _initializeAndroidAudioSettings() async {
  await webrtc.WebRTC.initialize(options: {

void main() async {
  await _initializeAudioSettings();
  runApp(const MyApp());

Note: the audio routing will become controlled by the system and cannot be manually changed with functions like Hardware.selectAudioOutput.

Desktop support #

In order to enable Flutter desktop development, please follow instructions here.

On M1 Macs, you will also need to install x86_64 version of FFI:

sudo arch -x86_64 gem install ffi

On Windows VS 2019 is needed (link in flutter docs will download VS 2022).

Usage #

Connecting to a room, publish video & audio #

final roomOptions = RoomOptions(
  adaptiveStream: true,
  dynacast: true,
  // ... your room options

final room = await LiveKitClient.connect(url, token, roomOptions: roomOptions);
try {
  // video will fail when running in ios simulator
  await room.localParticipant.setCameraEnabled(true);
} catch (error) {
  print('Could not publish video, error: $error');

await room.localParticipant.setMicrophoneEnabled(true);

Screen sharing #

Screen sharing is supported across all platforms. You can enable it with:



On Android, you would have to define a foreground service in your AndroidManifest.xml.

<manifest xmlns:android="">
        android:foregroundServiceType="mediaProjection" />


On iOS, a broadcast extension is needed in order to capture screen content from other apps. See setup guide for instructions.


On dekstop you can use ScreenSelectDialog to select the window or screen you want to share.

try {
  final source = await showDialog<DesktopCapturerSource>(
    context: context,
    builder: (context) => ScreenSelectDialog(),
  if (source == null) {
    print('cancelled screenshare');
  print('DesktopCapturerSource: ${}');
  var track = await LocalVideoTrack.createScreenShareTrack(
      maxFrameRate: 15.0,
  await room.localParticipant.publishVideoTrack(track);
} catch (e) {
  print('could not publish screen sharing: $e');

End to End Encryption #

LiveKit supports end-to-end encryption for audio/video data sent over the network. By default, the native platform can support E2EE without any settings, but for flutter web, you need to use the following steps to create e2ee.worker.dart.js file.

# for example app
dart compile js .\web\e2ee.worker.dart -o .\example\web\e2ee.worker.dart.js
# for your project
export YOU_PROJECT_DIR=your_project_dir
git clone
cd client-sdk-flutter && flutter pub get
dart compile js .\web\e2ee.worker.dart -o ${YOU_PROJECT_DIR}\web\e2ee.worker.dart.js

Advanced track manipulation #

The setCameraEnabled/setMicrophoneEnabled helpers are wrappers around the Track API.

You can also manually create and publish tracks:

var localVideo = await LocalVideoTrack.createCameraTrack();
await room.localParticipant.publishVideoTrack(localVideo);

Rendering video #

Each track can be rendered separately with the provided VideoTrackRenderer widget.

VideoTrack? track;

Widget build(BuildContext context) {
  if (track != null) {
    return VideoTrackRenderer(track);
  } else {
    return Container(
      color: Colors.grey,

Audio handling #

Audio tracks are played automatically as long as you are subscribed to them.

Handling changes #

LiveKit client makes it simple to build declarative UI that reacts to state changes. It notifies changes in two ways

  • ChangeNotifier - generic notification of changes. This is useful when you are building reactive UI and only care about changes that may impact rendering.
  • EventsListener<Event> - listener pattern to listen to specific events (see events.dart).

This example will show you how to use both to react to room events.

class RoomWidget extends StatefulWidget {
  final Room room;


  State<StatefulWidget> createState() {
    return _RoomState();

class _RoomState extends State<RoomWidget> {
  late final EventsListener<RoomEvent> _listener =;

  void initState() {
    // used for generic change updates;

    // used for specific events
      ..on<RoomDisconnectedEvent>((_) {
        // handle disconnect
      ..on<ParticipantConnectedEvent>((e) {
        print("participant joined: ${e.participant.identity}");

  void dispose() {
    // be sure to dispose listener to stop listening to further updates

  void _onChange() {
    // perform computations and then call setState
    // setState will trigger a build
    setState(() {
      // your updates here

  Widget build(BuildContext context) {
    // your build function

Similarly, you could do the same when rendering participants. Reacting to changes makes it possible to handle tracks published/unpublished or re-ordering participants in your UI.

class VideoView extends StatefulWidget {
  final Participant participant;


  State<StatefulWidget> createState() {
    return _VideoViewState();

class _VideoViewState extends State<VideoView> {
  TrackPublication? videoPub;

  void initState() {
    // trigger initial change

  void dispose() {

  void didUpdateWidget(covariant VideoView oldWidget) {

  void _onParticipantChanged() {
    var subscribedVideos = widget.participant.videoTracks.values.where((pub) {
      return pub.kind == TrackType.VIDEO &&
          !pub.isScreenShare &&

    setState(() {
      if (subscribedVideos.length > 0) {
        var videoPub = subscribedVideos.first;
        // when muted, show placeholder
        if (!videoPub.muted) {
          this.videoPub = videoPub;
      this.videoPub = null;

  Widget build(BuildContext context) {
    var videoPub = this.videoPub;
    if (videoPub != null) {
      return VideoTrackRenderer(videoPub.track as VideoTrack);
    } else {
      return Container(
        color: Colors.grey,

Mute, unmute local tracks #

On LocalTrackPublications, you could control if the track is muted by setting its muted property. Changing the mute status will generate an onTrackMuted or onTrack Unmuted delegate call for the local participant. Other participant will receive the status change as well.

// mute track
trackPub.muted = true;

// unmute track
trackPub.muted = false;

Subscriber controls #

When subscribing to remote tracks, the client has precise control over status of its subscriptions. You could subscribe or unsubscribe to a track, change its quality, or disabling the track temporarily.

These controls are accessible on the RemoteTrackPublication object.

For more info, see Subscriber controls.

Getting help / Contributing #

Please join us on Slack to get help from our devs / community members. We welcome your contributions(PRs) and details can be discussed there.

License #

Apache License 2.0

Thanks #

A huge thank you to flutter-webrtc for making it possible to use WebRTC in Flutter.

LiveKit Ecosystem
Client SDKsComponents · JavaScript · iOS/macOS · Android · Flutter · React Native · Rust · Python · Unity (web) · Unity (beta)
Server SDKsNode.js · Golang · Ruby · Java/Kotlin · PHP (community) · Python (community)
ServicesLivekit server · Egress · Ingress
ResourcesDocs · Example apps · Cloud · Self-hosting · CLI
pub points


verified publisher

Flutter Client SDK for LiveKit. Build real-time video and audio into your apps. Supports iOS, Android, and Web.



API reference


Icon for licenses.Apache-2.0 (LICENSE)


async, collection, connectivity_plus, cryptography, dart_webrtc, device_info_plus, fixnum, flutter, flutter_web_plugins, flutter_webrtc, flutter_window_close, http, js, logging, meta, platform_detect, protobuf, sdp_transform, synchronized, uuid


Packages that depend on livekit_client