Stay organized with collections
Save and categorize content based on your preferences.
Rather than downloading a large .zip file containing all .unitypackage
files for both .NET 3.X and .NET 4.X, you can download individual packages from
the Google APIs for Unity site.
The site provides:
Individual .NET 4.X .unitypackage files to import as Asset packages.
Individual .tgz archives to import using Unity Package Manager.
This is especially useful when your app uses a single Firebase product, since
the individual .unitypackage files contain all needed dependencies, and the
.tgz files are listed alongside related .tgz files on which they depend.
This page provides instructions involving Unity Package Manager, so it's a good
idea to learn about the tool from the Unity documentation.
Import Firebase packages as Assets
When importing Firebase products from .unitypackage files downloaded from
Google APIs for Unity site,
keep the following in mind:
If you are using multiple Firebase products in your project, you must download
and upgrade all Firebase products to the same version.
Do not mix import methods in one project. That is, do not import
Firebase products with the Asset package flow and using the Unity Package
Manager flow.
After downloading, to import:
In your open Unity project, navigate to Assets > Import Package >
Custom Package.
In the Import Unity Package window, click Import.
Import Firebase packages using Unity Package Manager
When importing Firebase products from .tgz files downloaded from the Google APIs for Unity archive, keep the following in mind:
This method is only available in 2018.3+.
If you are using multiple Firebase products in your project, you must download
and upgrade all Firebase products to the same version.
Do not mix import methods in one project. That is, do not import
Firebase products with the Asset package flow and with the Unity Package Manager
flow.
Dependencies for each product .tgz file are linked alongside in their own
.tgz files. You must download and import the product .tgz file and
dependency .tgz files, in the correct order:
Firebase products used in your project. If you use Realtime Database or
Cloud Storage, import Authentication (com.google.firebase.auth) first.
After downloading, import .tgz files into your project using one of the
following methods:
Package Manager UI
Open Unity's Package Manager window.
Click the + icon in the top-left corner of the Package Manager window and
select Add package from tarball to open the file browser.
Select the desired tarball in the file browser.
Some older versions of Unity 2019 do not support adding tarballs directly.
In this case, you will need to:
Unzip the .tgz file.
Click the + icon in the top-left corner of the Package Manager
window and select Add package from disk to open the file browser.
Select the extracted folder in the file browser.
manifest.json
Create a new folder next to your project's Packages folder and name it
GooglePackages.
Place the .tgz files into that folder.
Use a text editor to open Packages/manifest.json under your Unity project
folder.
Add an entry for each package you want to import, mapping the package name
to the location on disk. Be sure to append file: to the .tgz file path. For
example, if you were importing com.google.firebase.storage and its
dependency's, your manifest.json would look like this:
Migrate from Unity Package Manager to Asset packages
In some cases, you might want to switch from using Unity Package Manager to
track Firebase products, to importing products under the Assets folder.
If you're not sure which import method you're using, in your Unity project
folder, open the file Packages/manifest.json. If the file contains entries
starting with com.google.firebase, your project used Unity Package Manager for
import.
To migrate to Asset packages:
Note current Firebase package versions in your project and remove them.
From the Window menu, select Package Manager. In the Package
Manager window, make sure "Packages: In Project" is selected.
Note the versions of imported Firebase packages.
Click on each package name, then click Remove. Be sure to remove the
External Dependency Manager package (.com.google.external-dependency-manager)
as well as Firebase packages.
Download and import replacement .unitypackage files. You have two options:
If you can upgrade to the latest version of each package, download the
Firebase Unity SDK zip file and import as described in Add Firebase to
your Unity project.
If you need to preserve current .unitypackage versions, you can download
and import individual packages as described above
on this page.
Migrate from Asset packages to Unity Package Manager
In some cases, you might want to switch from importing products under the
Assets folder to importing and tracking products with Unity Package Manager.
If you're not sure which import method you're using, in your Unity project
folder, open the file Packages/manifest.json. If the file contains entries
starting with com.google.firebase your project is already using Unity Package
Manager for import.
To migrate to Unity Package Manager:
Make sure all Firebase packages and the External Dependency Manager package
are removed from the Assets folder, using either of the following methods.
EDM4U UI
In your open Unity project, navigate to Assets > External
Dependency Manager > Version Handler > Uninstall Managed
Packages.
Select all Firebase packages and External Dependency Manager.
Click Uninstall Selected Package.
Manual removal
Using file system tools, manually delete the following folders:
Assets/Editor Default Resources/Firebase
Assets/ExternalDependencyManager
Assets/Firebase
Assets/Parse
Assets/Plugins/iOS/Firebase
Import packages using Unity Package Manager, as described above
on this page.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-27 UTC."],[],[],null,["\u003cbr /\u003e\n\nRather than downloading a large `.zip` file containing all `.unitypackage`\nfiles for both .NET 3.X and .NET 4.X, you can download individual packages from\nthe [Google APIs for Unity site](https://developers.google.com/unity/packages).\n\nThe site provides:\n\n- Individual .NET 4.X `.unitypackage` files to import as Asset packages.\n- Individual `.tgz` archives to import using Unity Package Manager.\n\nThis is especially useful when your app uses a single Firebase product, since\nthe individual `.unitypackage` files contain all needed dependencies, and the\n`.tgz` files are listed alongside related `.tgz` files on which they depend.\n\nThis page provides instructions involving Unity Package Manager, so it's a good\nidea to learn about the tool [from the Unity documentation](https://docs.unity3d.com/Manual/Packages.html).\n| **Note:** If you still need to use .NET 3.x, download the entire Firebase SDK as described in [Add Firebase to your Unity project](/docs/unity/setup#add-sdks).\n\nImport Firebase packages as Assets\n\nWhen importing Firebase products from `.unitypackage` files downloaded from\n[Google APIs for Unity site](https://developers.google.com/unity/packages),\nkeep the following in mind:\n\n- If you are using multiple Firebase products in your project, you must download\n and upgrade all Firebase products to the same version.\n\n- Do not mix import methods in one project. That is, do not import\n Firebase products with the Asset package flow and using the Unity Package\n Manager flow.\n\nAfter downloading, to import:\n\n1. In your open Unity project, navigate to **Assets** \\\u003e **Import Package** \\\u003e\n **Custom Package**.\n\n2. In the *Import Unity Package* window, click **Import**.\n\nImport Firebase packages using Unity Package Manager\n\nWhen importing Firebase products from `.tgz` files downloaded from the [Google APIs for Unity archive](https://developers.google.com/unity/archive), keep the following in mind:\n\n- This method is only available in 2018.3+.\n\n- If you are using multiple Firebase products in your project, you must download\n and upgrade all Firebase products to the same version.\n\n- Do not mix import methods in one project. That is, do not import\n Firebase products with the Asset package flow and with the Unity Package Manager\n flow.\n\n- Dependencies for each product `.tgz` file are linked alongside in their own\n `.tgz` files. You must download and import the product `.tgz` file and\n dependency `.tgz` files, in the correct order:\n\n 1. External Dependency Manager (`com.google.external-dependency-manager`)\n 2. Firebase Core (`com.google.firebase.app`)\n 3. Firebase products used in your project. If you use Realtime Database or Cloud Storage, import Authentication (`com.google.firebase.auth`) first.\n\nAfter downloading, import `.tgz` files into your project using one of the\nfollowing methods: \n\nPackage Manager UI\n\n1. Open Unity's Package Manager window.\n2. Click the `+` icon in the top-left corner of the Package Manager window and select `Add package from tarball` to open the file browser.\n3. Select the desired tarball in the file browser.\n\nSome older versions of Unity 2019 do not support adding tarballs directly.\nIn this case, you will need to:\n\n1. Unzip the `.tgz` file.\n2. Click the `+` icon in the top-left corner of the Package Manager window and select `Add package from disk` to open the file browser.\n3. Select the extracted folder in the file browser.\n\nmanifest.json\n\n1. Create a new folder next to your project's `Packages` folder and name it `GooglePackages`.\n2. Place the `.tgz` files into that folder.\n3. Use a text editor to open `Packages/manifest.json` under your Unity project folder.\n4. Add an entry for each package you want to import, mapping the package name\n to the location on disk. Be sure to append `file:` to the `.tgz` file path. For\n example, if you were importing `com.google.firebase.storage` and its\n dependency's, your `manifest.json` would look like this:\n\n {\n \"dependencies\": {\n \"com.google.external-dependency-manager\": \"file:../GooglePackages/com.google.external-dependency-manager-1.2.164.tgz\",\n \"com.google.firebase.app\": \"file:../GooglePackages/com.google.firebase.app-7.1.0.tgz\",\n \"com.google.firebase.auth\": \"file:../GooglePackages/com.google.firebase.auth-7.1.0.tgz\",\n \"com.google.firebase.storage\": \"file:../GooglePackages/com.google.firebase.storage-7.1.0.tgz\",\n // com.unity package entries...\n }\n }\n\n5. Save the `manifest.json` file.\n\n6. When Unity regains focus it will reload the `manifest.json` and import the\n newly-added packages.\n\nSome older versions of Unity do not support `.tgz` files in the `manifest.json`.\nIn this case, you should:\n\n1. Unzip the `.tgz` file.\n2. Edit your `manifest.json` to use the path to the extracted folder, instead\n of the `.tgz` file, like so:\n\n {\n \"dependencies\": {\n \"com.google.external-dependency-manager\": \"file:../GooglePackages/com.google.external-dependency-manager-1.2.164\",\n \"com.google.firebase.app\": \"file:../GooglePackages/com.google.firebase.app-7.1.0\",\n \"com.google.firebase.auth\": \"file:../GooglePackages/com.google.firebase.auth-7.1.0\",\n \"com.google.firebase.storage\": \"file:../GooglePackages/com.google.firebase.storage-7.1.0\",\n // com.unity package entries...\n }\n }\n\nMigrate from Unity Package Manager to Asset packages\n\nIn some cases, you might want to switch from using Unity Package Manager to\ntrack Firebase products, to importing products under the `Assets` folder.\n\nIf you're not sure which import method you're using, in your Unity project\nfolder, open the file `Packages/manifest.json`. If the file contains entries\nstarting with `com.google.firebase`, your project used Unity Package Manager for\nimport.\n\nTo migrate to Asset packages:\n\n1. Note current Firebase package versions in your project and remove them.\n\n 1. From the **Window** menu, select **Package Manager** . In the *Package\n Manager* window, make sure \"Packages: In Project\" is selected.\n 2. Note the versions of imported Firebase packages.\n 3. Click on each package name, then click **Remove** . Be sure to remove the External Dependency Manager package (`.com.google.external-dependency-manager`) as well as Firebase packages.\n2. Download and import replacement `.unitypackage` files. You have two options:\n\n - If you can upgrade to the latest version of each package, download the Firebase Unity SDK zip file and import as described in [Add Firebase to\n your Unity project](/docs/unity/setup#add-sdks).\n - If you need to preserve current `.unitypackage` versions, you can download and import individual packages as described [above](#alternative_individual_unitypackages) on this page.\n\nMigrate from Asset packages to Unity Package Manager\n\nIn some cases, you might want to switch from importing products under the\n`Assets` folder to importing and tracking products with Unity Package Manager.\n\nIf you're not sure which import method you're using, in your Unity project\nfolder, open the file `Packages/manifest.json`. If the file contains entries\nstarting with `com.google.firebase` your project is already using Unity Package\nManager for import.\n\nTo migrate to Unity Package Manager:\n\n1. Make sure all Firebase packages and the External Dependency Manager package\n are removed from the `Assets` folder, using either of the following methods.\n\n EDM4U UI\n\n\n 1. In your open Unity project, navigate to **Assets \\\u003e External\n Dependency Manager \\\u003e Version Handler \\\u003e Uninstall Managed\n Packages**.\n 2. Select all Firebase packages and External Dependency Manager.\n 3. Click **Uninstall Selected Package**.\n\n \u003cbr /\u003e\n\n Manual removal\n\n Using file system tools, manually delete the following folders:\n - `Assets/Editor Default Resources/Firebase`\n - `Assets/ExternalDependencyManager`\n - `Assets/Firebase`\n - `Assets/Parse`\n - `Assets/Plugins/iOS/Firebase`\n2. Import packages using Unity Package Manager, as described [above](#alternative_unity_package_manager)\n on this page."]]