Pick the right Flutter debugging tool

Flutter DevTools runs on your computer and talks to your app while it runs. It can pause your code at a line and show your widget tree. It can also find slow frames, check memory and show logs. The overview lists every part. It is made for the person at the computer. A tester who only has the phone can't open it.

The Network view shows the web calls your app makes. It sees calls made with dart:io, like HttpClient and dio. It also sees cupertino_http, cronet_http and ok_http, which log through http_profile. For a Flutter web app, the docs say to use your browser's network tools.

Some packages add their own tab to DevTools. The extensions guide names provider and shared_preferences as examples. The tab shows up when your app uses that package. You turn it on one time, and DevTools saves your choice in devtools_options.yaml. Look for these tabs before you add a new tool.

MCP lets an AI helper use your tools. The Dart and Flutter MCP server is the official one. It can read errors from your code and from the running app. It can run tests and look at your widgets. It can also hot reload or restart your app. Its README says it is still experimental, and it needs a new Dart SDK. Try it first if your AI helper mostly needs your code and widgets.

Some free packages add a list of web calls inside your app. You open it on the phone. Here is what their pub.dev pages say. Alice catches REST calls and shows them on its own screen. Chucker Flutter saves calls on the phone and lets you share them. requests_inspector logs REST and GraphQL calls, and you shake the phone to open it.

Talker does more. It catches errors and keeps a log you can share. It has add-ons, like one for dio. Each package only sees some HTTP clients, so check its README for the one your app uses. If you only need to see web calls, one small package may be enough.

Buoy puts many tools behind one button in your app. You get tools for web calls, storage, logs, speed, Riverpod, routes and images. A timeline shows events from all of them. Buoy only runs in debug builds, and you need a free Buoy account. You can also open the tools in Buoy Desktop. With Pro, AI editors can use some of the tools through MCP.

Flutter support is in beta. It does not match React Native yet, and web builds do not work yet. Buoy sees web calls that go through dart:io's HttpClient. That covers package:http, dio and image loads. The state and route tools need your providers and router set up first. See the Flutter page and the Flutter docs to set it up.

A proxy sits between your app and the internet. Proxyman is one. It sees every call you send through it, even calls from native code that Dart tools miss. Flutter needs extra work here. Dart's HTTP client does not use the phone's proxy setting, so a proxy sees nothing at first. Proxyman's Flutter guide shows how to fix this.

The guide has a quick setup for the Android emulator. It also shows how to set the proxy in your code. To read HTTPS calls, the phone must trust the proxy's certificate. Use a proxy when you need calls from outside Dart, or when you can't change the app's code.

Debug tools only see your own phone. To see errors from real users, you need crash reports. The Sentry Flutter SDK catches errors and native crashes. It also has tracing, logs and session replay. Firebase Crashlytics sends errors to the Firebase console.

Datadog and Luciq also make Flutter SDKs for apps that are out in the world. Compare what each one collects, how long it keeps data and what it costs. Send a test error before you trust one. Buoy helps you repeat a bug on your own phone. It does not collect reports from users.

Flipper's repo was archived on September 26, 2025, so it gets no more updates. Its Flutter plugin, flutter_flipperkit, last came out on pub.dev in May 2023. If you still use it, list the plugins you need. Then pick a new tool for each one: DevTools, an in-app viewer or a proxy.

Pick one real bug and try it with each tool. Write down what each tool caught and how long setup took. Keep the tools that helped.

We read the linked docs and pub.dev pages on September 30, 2026. The Buoy team wrote this guide from what those pages say. We did not run speed tests. See the comparison hub for React Native tools.