google-services.json Validator

What is google-services.json Validator?

The google-services.json file is the central configuration artifact that connects an Android application to its Firebase project. It carries the project identifier, mobile app ID, API keys, OAuth client credentials, and storage bucket references that the Firebase SDK needs at initialization time. The Google Services Gradle plugin reads this file during the build process and injects its values into Android resource strings, making them available to Firebase Analytics, Cloud Messaging, Remote Config, and every other Firebase service. A missing or malformed google-services.json is one of the most common reasons Firebase integration fails at compile time.

How to Use

1. In Parse mode, paste or upload an existing google-services.json to validate its structure and inspect every field in a readable layout
2. In Generate mode, fill in your Firebase project details — Project ID, Package Name, and API Key are mandatory — to produce a syntactically correct file
3. Upload a file from your workstation to check for missing fields, invalid keys, or mismatched package names before you ship
4. Download the generated file and place it in your Android project's app/ root directory so the Gradle plugin can process it
5. Review the validation results — errors block compilation, while warnings indicate optional fields that may cause runtime issues

Tips & Best Practices

• Always download the production google-services.json from the Firebase Console rather than generating one manually — Console-generated files include all OAuth client entries
• Commit google-services.json to version control, but restrict the API keys in the Firebase Console to your app's signing certificate SHA-1 fingerprint
• Use separate google-services.json files for debug and release build types by placing them in the appropriate source set directories (src/debug and src/release)
• Verify that the package_name field exactly matches the applicationId in your app-level build.gradle — a mismatch causes Firebase services to silently fail
• Never expose Firebase API keys in public repositories without applying app-level restrictions in the Firebase Console

Frequently Asked Questions

Real-world Examples

{
  "project_info": {
    "project_number": "123456789012",
    "project_id": "my-firebase-project",
    "storage_bucket": "my-firebase-project.appspot.com"
  },
  "client": [{
    "client_info": {
      "mobilesdk_app_id": "1:123456789012:android:abc123",
      "android_client_info": { "package_name": "com.example.myapp" }
    },
    "api_key": [{ "current_key": "AIzaSyC1234567890abcdefghijklmnop" }]
  }]
}

Valid google-services.json
Project ID: my-firebase-project
Client 0 package: com.example.myapp
Client 0 API keys: 1

Project ID: my-new-app | Package: com.startup.myapp | API Key: AIzaSyD... | App ID: 1:987654321:android:xyz789

{
  "project_info": {
    "project_number": "987654321",
    "firebase_url": "https://my-new-app.firebaseio.com",
    "project_id": "my-new-app",
    "storage_bucket": "my-new-app.appspot.com"
  },
  "client": [{
    "client_info": {
      "mobilesdk_app_id": "1:987654321:android:xyz789",
      "android_client_info": { "package_name": "com.startup.myapp" }
    },
    "api_key": [{ "current_key": "AIzaSyD..." }]
  }],
  "configuration_version": "1"
}

Related Tools