What is the difference between Sentry and Crashlytics?

I want to understand the difference between Sentry and Firebase Crashlytics when evaluating crash reporting and mobile monitoring solutions.

Firebase Crashlytics is a mobile crash reporting service that’s part of the Firebase ecosystem. Sentry also provides crash and error monitoring, but goes beyond crash reporting with application performance monitoring, distributed tracing, Session Replay, profiling, release health, and tools for managing and responding to issues. Sentry can monitor your mobile applications alongside the rest of your stack, including frontend, backend, and connected services.

One of the main differences is scope. Crashlytics is primarily focused on mobile crash reporting, while Sentry is designed to give teams visibility across their entire application stack in one place.

Sentry also provides additional context to help you understand and debug issues, including breadcrumbs, device and operating system details, suspect commits, screenshots, and Session Replay. Its workflow features support issue triage and assignment, customizable alerts, and integrations with tools such as GitHub and Jira.

For mobile development, Sentry offers first-class SDKs for Android, iOS, React Native, Flutter, and other platforms. For example, React Native source maps can help turn minified stack traces into readable ones.

Another difference is hosting. Sentry is available both as a SaaS product and as a self-hosted option, while Crashlytics is a Google-hosted service within Firebase.

If you’re specifically evaluating mobile monitoring, you can learn more in the Sentry vs Crashlytics comparison and the Mobile Developer's Decision-Making Guide. For an overview of Sentry’s mobile capabilities, see mobile monitoring and the Sentry documentation.