--- title: "App Hosting has in-console environment variables and faster builds" description: "Manage environment variables in the Firebase console, and learn about a small change our engineering team made to improve build times for everyone." published: "2026-03-12" last_updated: "2026-03-12" authors: - "Julia Reid (Product Manager)" categories: - "App Hosting" - "Web" - "JavaScript" - "Firebase console" canonical_url: "https://firebase.blog/posts/2026/03/apphosting-march-update" --- # App Hosting has in-console environment variables and faster builds *Published March 12, 2026 by Julia Reid (Product Manager)* --- We're thrilled to walk you through a fresh set of updates for Firebase App Hosting! These new features, designed to speed up your deployment workflow, include an interface for managing environment variables in the Firebase console and faster deployment times. Keep reading to learn more. ### Manage environment variables in the Firebase console App Hosting has long supported configuring environment variables and secrets in `apphosting.yaml`. While this file-based approach is great for keeping a clear version history, a console UI is often more convenient. In fact, managing these settings directly in the console has been one of our top [UserVoice](https://firebase.uservoice.com/forums/948424-general/suggestions/48450056-create-a-ui-for-managing-environment-variables-and) requests. Today, we're excited to announce that you can add and edit App Hosting environment variables in the Firebase console! You can add environment variables when creating a new App Hosting backend: ![A screenshot of the "Configure your backend" step of the "Set up App Hosting" flow, showing a new form for adding environment variables.](https://firebasestorage.googleapis.com/v0/b/first-class-blog.appspot.com/o/posts%2Fapp-hosting-env-var-setup_1600x800.webp?alt=media&token=38bbe5c7-a27b-45d7-b3cb-185c9dba83db) Or add them later in backend **Settings**. To manage environment variables for an existing backend, navigate to **View Backend \>\> Settings \>\> Environment** and then add, edit, or delete environment variables. ![A screenshot of the "Environment" tab of the Settings page for an App Hosting backend, showing a new form for adding environment variables.](https://firebasestorage.googleapis.com/v0/b/first-class-blog.appspot.com/o/posts%2Fapp-hosting-env-var-settings_1600x800.webp?alt=media&token=0056b094-1696-4b73-9dfd-183afa3d534d) > **Pro tip:** To speed up migrating an existing app to App Hosting, you can [**copy and paste content directly from your dotenv files**](https://firebase.google.com/docs/app-hosting/configure#dotenv-files) into the Firebase console. Environment variables set in the console are visible to any user who has access to your project. For sensitive information like API keys, we recommend using Cloud Secret Manager for more granular access control. You can [use the `firebase apphosting:secrets:set` CLI command](https://firebase.google.com/docs/app-hosting/configure#secret-parameters) to create and add secret references in `apphosting.yaml`. The Firebase console and `apphosting.yaml` can be used in tandem to define environment variables and secrets for your backend. Firebase App Hosting merges the configurations, with **console values always taking precedence over conflicting values in `apphosting.yaml`.** Learn more about the order of precedence [in the docs](https://firebase.google.com/docs/app-hosting/configure#variable-hierarchy). To view the final set of merged environment variables for a rollout, navigate to the **Rollouts** tab and click on the rollout. In the side panel, you'll find the complete list of environment variables used and their sources. ![A screenshot of the details for a rollout, with an "Environment variables in this build" section.](https://firebasestorage.googleapis.com/v0/b/first-class-blog.appspot.com/o/posts%2Fapp-hosting-env-var-details_1600x800.webp?alt=media&token=8b93dc9e-c5c3-45a8-b5be-c50af2559afc) You'll notice a few Firebase system environment variables: `FIREBASE_CONFIG` and `FIREBASE_WEBAPP_CONFIG`. These are populated by Firebase App Hosting at build time to [automatically initialize the Firebase SDKs](https://firebase.google.com/docs/app-hosting/firebase-sdks#automatically-initialize-firebase-admin-and-web-sdks). You can override the default values for these system environment variables in the Firebase console or in `apphosting.yaml`. To learn more about App Hosting environment configuration, check out [Configure and manage App Hosting backends](https://firebase.google.com/docs/app-hosting/configure). ### Faster builds Firebase App Hosting [uses Cloud Native Buildpacks](https://firebase.blog/posts/2025/06/app-hosting-frameworks/#the-nodejs-buildpack) to transform your application source code into production-ready container images. We recently optimized the App Hosting build process by directly invoking the buildpack binary rather than using the `pack` CLI command, eliminating an unnecessary image pull step. Our internal monitoring suggests this small change has _reduced p50 build times by **\~18%** and p99 build times by **\~27%**_. Improving App Hosting builds continues to be a focus area for us. Stay tuned for future optimizations! ### Let us know what you think We hope that these new features will enhance your experience with App Hosting and we're excited to see what you build! If you haven't already, head over to the [Firebase console](http://console.firebase.google.com/project/_/apphosting) and explore our [documentation](http://firebase.google.com/docs/app-hosting) to deploy your first app. As always, if you have questions, you can hit us up on any of our [support channels](https://firebase.google.com/support), or post questions on Stack Overflow. And if you have ideas for any new features, let us know on [User Voice](https://firebase.uservoice.com/forums/948424-general?category_id=501599).