How to change the app name and logo on Google sign-in for a Firebase app

Why Google shows the wrong name (or no name)

• A Firebase project is a Google Cloud project. Firebase says "When you create a new Firebase project, you're actually creating a Google Cloud project behind the scenes." The OAuth branding (Firebase's FAQ calls it the OAuth brand) lives in that Cloud project.
• The brand is created for you. Firebase's FAQ says "the OAuth brand is provisioned only when Google sign-in is enabled."
• Name and logo need verification. Google's branding help says the app name appears on the consent screen only after your app passes verification, and an uploaded logo goes through the same review for external apps in production.
• Firebase's "Public-facing name" is a separate field. Firebase's help describes it as "the name presented to users when they are shown any public instances of your project," with emails after sign-up as its example. Its help page doesn't say it changes Google's sign-in screens, so use the Branding page below for those.

Step-by-step: change the name and logo

Console labels below are as of Oct 2026.

1. Open the Branding page for the right project

Go to Google Cloud console → Google Auth Platform → Branding, or open this URL with your Firebase project ID:

https://console.developers.google.com/auth/branding?project=PROJECT_ID

Your Firebase project ID is in the Firebase console under Project settings, and in your web config as projectId.

2. Set the app name

Choose a name that "distinctively represents your business." Google rejects names that could be confused with Google's or other companies' brands, or that combine Google product names with generic words. Its examples of unacceptable names include "Google Drive for iOS" and "Gmail for Android"; acceptable ones include "Inbox Assistant" and "PDF Viewer for Google Drive."

3. Upload a logo (optional)

Google's requirements: the image must represent your app, be no larger than 1 MB, use JPG, PNG or BMP, and ideally be square at 120 × 120 px. For an external app in production, a new logo goes through verification before it appears.

4. Fill in support email, app domain and developer contact

• User support email: shown to users on the consent screen; it must be your Google account's address or a Google Group you manage.
• App domain links: home page, privacy policy and terms of service. Google says these "are required for all external production apps." The home page must be on a domain you own whose ownership you've confirmed with Google, must describe your app, and "can not be only a login page"; the privacy policy must sit on the same domain as the home page.
• Developer contact information: where Google sends notices about the project.

5. Add and prove your authorized domains

On the same page, the Authorized domains list must include the top private domain of your home page, privacy policy and terms links (for example example.com for https://app.example.com/privacy), plus the domains in your web client's redirect URIs and JavaScript origins. Google asks you to prove ownership of these domains in Google Search Console, using an account that is an Owner or Editor on the project.

6. Check the audience setting

On Google Auth Platform → Audience, look at the user type and publishing status. Google's brand verification guide says an app needs verification if it is set up for External users and shows a logo or display name on the consent screen, and its branding help says a logo upload goes through verification when the app is external and in production. Apps left in Testing are limited to the test users you add and show a tester warning screen, and apps with an Internal user type serve only your Google Workspace or Cloud Identity organization.

7. Verify and publish the branding

1. Changes you make are saved as Draft branding.
2. Click Verify Branding. Google says the automated review "usually completes in a few minutes," and its brand verification guide says the process "typically takes 2-3 business days after submission" when a fuller review is needed.
3. When the status shows Ready to publish, click Publish branding. Google says a passing result is valid for 7 days; after that you must run verification again.
4. If the status shows Need to fix issues, open View issues, fix them, and request re-verification (or request an additional review if you think the findings are wrong).

You can't edit branding while a verification is running; cancel it first.

App name vs the "continue to" domain

Google's screens can show two different things, and they are set in different places:

Changing the app name does not change the domain, and changing the domain does not change the app name. If the line that bothers you is "continue to xxxx.firebaseapp.com," see Google sign-in says "continue to firebaseapp.com". Background on the setting: what Firebase authDomain is.

How to confirm the new name is live

1. On the Branding page, check that the published version matches your draft. If they differ, Google shows a View differences link.
2. On Google Auth Platform → Verification Center, check the Branding status.
3. In a private window, start Google sign-in in your app and read the name and logo on Google's screen.

Related problems

• Firebase emails use the wrong app name. Firebase's FAQ says the %APP_NAME% in Authentication email templates uses "the OAuth brand name" when one is available, so publishing new branding can also change your emails.
• Users see Google's unverified-app warning. Google's verification guide ties that screen to your audience and publishing status; see step 6.
• The sign-in popup or redirect itself fails. That's not a branding issue; start with choosing popup or redirect.