starter.wikiSearch⌘K

Native push transport

Firebase Cloud Messaging

Google's cross-platform push transport for sending messages to registered app instances through platform delivery channels.

Visit official site

Editorial verdict

Choose Firebase Cloud Messaging when native transport is enough and the team will own targeting, token lifecycle, permissions, throttling, observability, and user-visible state.123

Best for

  • Teams building application-owned push orchestration
  • Products needing a no-cost mobile and web transport rail
  • Applications already prepared to manage registration tokens
123

Not ideal for

  • Teams needing managed journeys and segmentation
  • Products requiring a persistent notification inbox
  • Buyers assuming transport acceptance guarantees user delivery
123
Main trade-off

No-cost transport minimizes vendor software spend while leaving audience logic, token hygiene, permissions, observability, and delivery-state UX with the application.123

Product boundary

Whether native no-cost push transport is sufficient when the application owns targeting, token state, permissions, and delivery operations.

This page evaluates Firebase Cloud Messaging only. It does not inherit the pricing or verdict of the broader Firebase product family and does not provide a persistent inbox or full engagement suite.123

For: Teams prepared to build and operate their own push audience, token, permission, and message workflow

  • Managed segmentation or journeys become necessary
  • Project quotas or platform behavior do not fit
  • A persistent inbox or application-level notification state is required

Why teams consider Firebase Cloud Messaging

  • Cross-platform transportFCM documents message delivery for supported Apple, Android, and web clients.123
  • Application-owned controlThe application server owns targeting and send requests rather than outsourcing the engagement layer.123
  • No-cost productFirebase currently lists Cloud Messaging as a no-cost product, subject to quotas.123

Pricing

Firebase Cloud Messaging is currently listed as no-cost, but quotas, surrounding application infrastructure, token operations, observability, and any other Firebase or Google Cloud services remain separate cost boundaries.3

Push transport

No-cost product

Verified 2026-07-26: Firebase lists Cloud Messaging as no-cost; the default downstream quota is 600,000 messages per minute per project and does not constitute a delivery guarantee.3

Software price
No cost currently listed for Cloud Messaging3
Default quota
600,000 downstream messages per minute per project3
Ownership boundary
Targeting, tokens, permissions, and user-visible state remain application-owned3
Pricing checked View official pricing

Firebase Cloud Messaging vs alternatives

OneSignal

Choose when
Choose it when a managed push-engagement layer across mobile and web is worth adopting a broader messaging suite.
Avoid when
Avoid it when the team only needs native transport or wants to keep audience and journey state application-owned.
Compared with Firebase Cloud Messaging
Managed engagement features reduce product work while adding subscription-record pricing and suite dependence.45

Expo Push Service

Choose when
Choose it when an Expo application benefits from one relay API over FCM and APNs and can accept its limits.
Avoid when
Avoid it when web push, an SLA, direct native-provider control, or a managed engagement layer is required.
Compared with Firebase Cloud Messaging
Framework convenience introduces a relay dependency, published rate limits, and no service-level agreement.678

Resources and sources

Official product, pricing, and operating-policy sources

  • Firebase Cloud Messaging documentation
    Open
  • Firebase Cloud Messaging quotas
    Open
  • Firebase pricing
    Open
  • OneSignal documentation
    Open
  • OneSignal pricing
    Open
  • Expo push notification overview
    Open
  • Expo Push Service pricing and limits
    Open
  • Send notifications with Expo Push Service
    Open
  1. 1
    Firebase Cloud Messaging documentation

    Google · Accessed Official

  2. 2
    Firebase Cloud Messaging quotas

    Google · Accessed Official

  3. 3
    Firebase pricing

    Google · Accessed Official

  4. 4
    OneSignal documentation

    OneSignal · Accessed Official

  5. 5
    OneSignal pricing

    OneSignal · Accessed Official

  6. 6
    Expo push notification overview

    Expo · Accessed Official

  7. 7
    Expo Push Service pricing and limits

    Expo · Accessed Official

  8. 8
    Send notifications with Expo Push Service

    Expo · Accessed Official