# Flutter Crash Reporting & Performance Monitoring > Capture Dart errors and native iOS and Android crashes with symbolicated stack traces, plus tracing, session replay, and logs. **URL:** https://sentry.io/for/flutter/ --- Debug Flutter apps and prevent crashes across your entire stack. Flutter crash reporting and logging with a single view so you can diagnose, fix, and optimize the performance of your code with maximum efficiency. **Documentation:** [https://docs.sentry.io/platforms/dart/guides/flutter/](https://docs.sentry.io/platforms/dart/guides/flutter/) ## Install Install with the Sentry wizard ```bash brew install getsentry/tools/sentry-wizard && sentry-wizard -i flutter ``` See the [Flutter docs](https://docs.sentry.io/platforms/dart/guides/flutter/) for full setup options. ## Features ### Session Replay Get to the root cause of an issue faster by watching replays of real user sessions with best-in-class privacy controls. Understand when, where, and how an error is impacting your app without having to repro it yourself, talk to a customer, or expose sensitive data. ### Application Monitoring, End to End See Flutter app crash reports with details like filename and line number so you never have to guess or dig through an Flutter error log. Filter and group Flutter exceptions intuitively to eliminate noise. Monitor errors at scale without impacting throughput in production. ### Complete, Symbolicated Stack Traces See an event trail to know what the app was doing before any error occurred. Record Flutter stack traces even when devices are offline or in airplane mode, then send errors as soon as connection is regained. ### Flutter Crash Reporting Improve workflow with a full view of releases so you can mark errors as resolved and prioritize live issues. Learn in which version a bug first appeared, merge duplicates, and know if things regress in a future release. Add commit data to automatically suggest an owner of each application error and instantly send deploy emails. ### Your Logs, Next to the Crash Send logs from your Flutter app to Sentry and query them next to the errors and [traces](/product/tracing/) they belong to. The log lines leading up to a crash travel with the crash report, so you can see what the app was doing before it failed. Learn more about [Logs in Sentry](/product/logs/). ## FAQ **What is the difference between Sentry and traditional logging?** Traditional logging provides you with a trail of events. Some of those events are errors, but many times they're simply informational. Sentry is fundamentally different because we focus on exceptions, or in other words, we capture application crashes. We discuss in more detail [here](/vs/logging/) and on our [blog](https://blog.sentry.io/lets-get-ready-to-monitor/). **What languages does Sentry support?** Sentry supports every major language, framework, and library. You can browse each of them [here](/platforms/). **How much does Sentry cost?** You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our [pricing page](/pricing/). **How does Sentry impact the performance of my app?** Sentry doesn't impact a web site's performance. If you look at the configuration options for when you initialize Sentry in your code, you'll see there's nothing regarding minimizing its impact on your app's performance. This is because our team of SDK engineers already developed Sentry with this in mind. Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error. Global handlers have almost no impact as well, as they are native APIs provided by the browsers. **Does Sentry support Flutter crash reporting on iOS and Android?** Yes. The Sentry Flutter SDK captures Dart errors and unhandled exceptions as well as native crashes on the [iOS](/for/ios/) and [Android](/for/android/) layers underneath, so a crash in platform code is reported the same way as one in your Dart code. Upload your debug symbols so obfuscated release stack traces are readable, and add [Session Replay](/product/session-replay/) to see what the user did in the moments before the crash. **Can I send logs to Sentry?** Yes. Sentry Logs lets you send, view, and query structured logs from your application alongside your errors and traces. Because logs sit next to the error and the trace that produced them, you get the granular context — retries, API failures, internal state — that spans and stack traces alone can miss, without switching tools. Learn more about [Logs in Sentry](/product/logs/). **What is Seer, Sentry's AI debugging agent?** Seer is Sentry's AI debugging agent. It reads the full context Sentry already has — the error, its stack trace, the surrounding trace, logs, and profiles — to find the root cause of an issue and propose a fix. Seer can open a pull request with that fix, hand the work to an external coding agent, or review your PRs before they ship. Learn more about [Seer](/product/seer/) and [Autofix](/product/seer/autofix/). --- *Source: [sentry.io/for/flutter/](https://sentry.io/for/flutter/)*