Flutter package for Supabase.

pub package
pub test

What is Supabase

Supabase is an open source Firebase alternative. We are a service to:

  • listen to database changes
  • query your tables, including filtering, pagination, and deeply nested relationships (like GraphQL)
  • create, update, and delete rows
  • manage your users and their permissions
  • interact with your database using a simple UI


  • Alpha: Under heavy development
  • Public Alpha: Ready for testing. But go easy on us, there will be bugs and missing functionality.
  • Public Beta: Stable. No breaking changes expected in this version but possible bugs.
  • Public: Production-ready


  • Null-safety
Platform Email Auth Provider Auth Database Realtime Storage

Getting Started

Import the package:

import 'package:supabase_flutter/supabase_flutter.dart';

Intialize Supabase before using it:

import 'package:supabase_flutter/supabase_flutter.dart';

void main() async {

  await Supabase.initialize(
    url: SUPABASE_URL,
    authCallbackUrlHostname: 'login-callback', // optional
    debug: true // optional


authCallbackUrlHostname is optional. It will be used to filter Supabase authentication redirect deeplink. You need to provide this param if you use deeplink for other features on the app.

debug is optional. It’s enabled by default if you’re running the app in debug mode (flutter run --debug).


Using authentication can be done easily.

Email authentication

import 'package:supabase_flutter/supabase_flutter.dart';

Future<void> signIn(String email, String password) async {
  final response = await Supabase.instance.client.auth.signIn(email: email, password: password);
  if (response.error != null) {
    /// Handle error
  } else {
    /// Sign in with success


It helps you handle authentication with deeplink from 3rd party service like Google, Github, Twitter…

For more details, take a look at the example here

When using with a nested authentication flow, remember to call startAuthObserver() and stopAuthObserver() before/after navigation to new screen to prevent multiple observers running at the same time. Take a look at the example here


It helps you protect route that requires an authenticated user.

For more details, take a look at the example here


This method will automatically launch the auth url and open a browser for user to sign in with 3rd party login.

  options: supabase.AuthOptions(redirectTo: ''),

Custom LocalStorage

As default supabase_flutter uses hive plugin to persist user session. However you can use any other plugins by creating a LocalStorage impl.

For example, we can use flutter_secure_storage plugin to store the user session in a secure storage.

// Define the custom LocalStorage implementation
class SecureLocalStorage extends LocalStorage {
  SecureLocalStorage() : super(
    initialize: () async {},
    hasAccessToken: () {
      const storage = FlutterSecureStorage();
      return storage.containsKey(key: supabasePersistSessionKey);
    }, accessToken: () {
      const storage = FlutterSecureStorage();
      return supabasePersistSessionKey);
    }, removePersistedSession: () {
      const storage = FlutterSecureStorage();
      return storage.delete(key: supabasePersistSessionKey);
    }, persistSession: (String value) {
      const storage = FlutterSecureStorage();
      return storage.write(key: supabasePersistSessionKey, value: value);

// use it when initializing
  localStorage: SecureLocalStorage(),

You can use EmptyLocalStorage to disable session persistance:

  // ...
  localStorage: const EmptyLocalStorage(),

Deeplink config

Supabase redirect URLs config

  • Go to your Supabase project Authentication Settings page.
  • You need to enter your app redirect callback on Additional Redirect URLs field.

The redirect callback url should have this format [YOUR_SCHEME]://[YOUR_AUTH_HOSTNAME]

authentication settings page

Supabase 3rd party logins config

Follow the guide

For Android

Deep Links can have any custom scheme. The downside is that any app can claim a scheme, so make sure yours are as unique as possible, eg. HST0000001://

<manifest ...>
  <!-- ... other tags -->
  <application ...>
    <activity ...>
      <!-- ... other tags -->

      <!-- Deep Links -->
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" />
        <!-- Accepts URIs that begin with YOUR_SCHEME://YOUR_HOST -->
          android:host="[YOUR_HOST]" />

The android:host attribute is optional for Deep Links.

For more info:

For iOS

Custom URL schemes can have… any custom scheme and there is no host specificity, nor entitlements or a hosted file. The downside is that any app can claim any scheme, so make sure yours is as unique as possible, eg. hst0000001 or myIncrediblyAwesomeScheme.

For Custom URL schemes you need to declare the scheme in
ios/Runner/Info.plist (or through Xcode’s Target Info editor,
under URL Types):

<!-- ... other tags -->
  <!-- ... other tags -->
  <!-- ... other tags -->

This allows for your app to be started from YOUR_SCHEME://ANYTHING links.

For more info:


  • Fork the repo on GitHub
  • Clone the project to your own machine
  • Commit changes to your own branch
  • Push your work back up to your fork
  • Submit a Pull request so that we can review your changes and merge


This repo is licenced under MIT.


View Github