SEO Web Tools

FCM Configuration Tester

Test your Firebase Cloud Messaging setup, validate credentials, send test notifications, and analyze your FCM configuration with comprehensive diagnostics.

✓ Legacy & HTTP v1 API ✓ Live FCM Diagnostics ✓ Free & Private

FCM Configuration

Authentication Method:

Legacy Server Key Service Account (OAuth2)

Legacy Server Key:

Find in: Firebase Console → Project Settings → Cloud Messaging → Server Key

Device/Registration Token: FCM registration token from your app. Leave empty for configuration validation only.

Test Options:

Validate Configuration

Send Test Notification

Check Token Validity

Analyze Configuration

Test Notification Details

Title:

Body:

Priority:

Sound:

Privacy Notice: Testing is performed securely via your backend. Your keys are used only for this request and are not stored.

Ctrl/Cmd + Enter to run tests quickly

FCM Configuration Health Score

--

out of 100

Test Statistics

Test Results

Quick Actions

Related Tools

Why FileReadyNow

Validate Your FCM Setup and Send a Test Notification

Enter your credentials, provide a device token, and confirm your Firebase Cloud Messaging configuration works end to end.

Legacy and HTTP v1 API

Supports both the legacy server key method and the newer HTTP v1 API using a service account JSON file from Firebase Console.

Send Test Notifications

Provide a device registration token and the tool sends a real push notification to confirm your credentials and delivery work together.

Credential Validation

Validates your server key or service account JSON before attempting a send so authentication errors are caught before they reach production.

Detailed Error Codes

Returns the specific Firebase error code on failure with a plain explanation of what it means and how to fix it.

Android and Cross-Platform

Works for Android apps and any cross-platform app using Firebase as its notification backend, including Flutter and React Native.

No Account Required

Enter your FCM credentials and test. No signup, no subscription, and your credentials are never stored or logged.

Firebase Cloud Messaging is the standard way to send push notifications to Android devices and cross-platform apps using Firebase. Getting the credentials right is critical — a wrong server key, mismatched project, or invalid service account JSON means notifications fail silently. The FCM Configuration Tester from FileReadyNow validates your credentials, sends a test notification to a device token, and provides detailed diagnostic output so you can confirm your setup works before it reaches production.

What This Tool Does

The tester accepts your FCM credentials, connects to Firebase's messaging API, and validates the configuration. If you provide a device registration token, it sends a test notification and reports the result. Detailed feedback is returned for both successful deliveries and failures, including the specific error code and what it means, so you spend less time guessing and more time fixing the actual issue.

Authentication Methods Supported

Legacy server key: The original FCM authentication method using a server key from the Firebase Console under Cloud Messaging settings. Simple to set up but being deprecated by Google in favour of the newer service account approach.
Service account (HTTP v1 API): The recommended modern authentication method using a JSON service account key downloaded from Firebase Console. More secure and required for the FCM HTTP v1 API which supports richer notification features and better error reporting.

Common Use Cases

Initial FCM Setup Validation: After integrating Firebase into a new app or backend, verify that your credentials are correctly configured and notifications can be sent before releasing to users.
Debugging Delivery Failures: When push notifications stop arriving on Android devices, test the credentials and device token to confirm whether the issue is with the configuration or elsewhere in the stack.
Migrating to HTTP v1 API: When upgrading from the legacy server key to the service account approach required by the newer FCM v1 API, validate the new credentials before deprecating the old ones.
Multi-Platform Notification Testing: Test FCM configurations for apps that send notifications to Android, web, and Flutter clients using a single Firebase project.
Backend Integration Check: Confirm that a server-side integration with FCM is working correctly by sending a test notification directly from the credentials your backend uses, isolating any issues from the app side.

What to Expect from the Results

The tester returns a clear pass or fail result along with the full API response from Firebase. Error codes are explained in plain language so you understand what each response means. If a device token is not provided, the tool validates the credentials only without attempting to deliver a notification. Results include enough detail to take direct action, whether that means correcting a credential, refreshing a token, or investigating an issue on the device side.

Step by Step

How to Use FCM Configuration Tester

Choose authentication method: Legacy Server Key or Service Account (HTTP v1 API).

Enter credentials and optionally add a device registration token for live testing.

Run the test and view detailed diagnostic results with error explanations and recommendations.

Frequently Asked Questions

An FCM Configuration Tester is a developer tool used to verify Firebase Cloud Messaging setup by sending test notifications and checking whether credentials and tokens are configured correctly.

Android developers, backend engineers, and QA teams who work with FCM push notification Android setups and want to avoid silent delivery failures.

Yes, it sends test notifications using your provided FCM credentials to confirm whether messages can be delivered successfully.

Absolutely. This FCM tester helps identify issues like invalid server keys, expired tokens, or incorrect project configurations.

No. The tool is designed to be simple and code-free, making it easy to test configurations without modifying your app.