---
title: "View Hierarchy"
description: "Learn more about debugging the view hierarchy when an error occurs. Sentry pairs the view hierarchy representation with the original event, giving you additional insight into issues."
url: https://docs.sentry.io/platforms/dart/guides/flutter/enriching-events/viewhierarchy/
---

# View Hierarchy | Sentry for Flutter

Sentry makes it possible to render a JSON representation of the view hierarchy of an error and includes it as an [attachment](https://docs.sentry.io/platforms/dart/guides/flutter/enriching-events/attachments.md).

This feature only applies to SDKs with a user interface, such as the ones for mobile and desktop applications. In some environments like native iOS, rendering the view hierarchy requires the UI thread and in the event of a crash, that might not be available. Another example where the view hierarchy might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution.

Deobfuscation for view hierarchies is fully supported for native SDKs, and React Native, but is currently not supported for Flutter.

## [Enabling View Hierarchy Attachments](https://docs.sentry.io/platforms/dart/guides/flutter/enriching-events/viewhierarchy.md#enabling-view-hierarchy-attachments)

View hierarchy debugging is an opt-in feature. You can enable it as shown below:

```dart
await SentryFlutter.init((options) {

  options.attachViewHierarchy = true;

});
```

### [Customize View Hierarchy Capturing](https://docs.sentry.io/platforms/dart/guides/flutter/enriching-events/viewhierarchy.md#customize-view-hierarchy-capturing)

By default, Flutter limits view hierarchy captures to once every 2 seconds to minimize performance impact. While this debounce interval cannot be changed, you can customize capture behavior by implementing the `beforeCaptureViewHierarchy` callback in your `SentryFlutterOptions`.

This callback gives you fine-grained control over view hierarchy captures based on event and hint data, allowing you to implement conditional logic.

The `shouldDebounce` parameter is `true` if the debounce is active. If you want to capture view hierarchies regardless of the debounce, you can ignore the `shouldDebounce` parameter.

```dart
await SentryFlutter.init((options) {

  options.beforeCaptureViewHierarchy = (event, hint, shouldDebounce) async {
    // If debounce is active, skip capturing
    if (shouldDebounce) {
      return false;
    }
    // Capture view hierarchy if it's a fatal event
    return event.level == SentryLevel.fatal;
  };

});
```

## [Viewing View Hierarchy Attachments](https://docs.sentry.io/platforms/dart/guides/flutter/enriching-events/viewhierarchy.md#viewing-view-hierarchy-attachments)

View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](https://docs.sentry.io/product/issues/issue-details.md) page of that specific event.

On the **Issue Details** page, you can interact with the view hierarchy attachment in a section called "View Hierarchy". This section represents the state of your application at the time of an error event. There are three displays: a tree view, wireframe, and detailed view for a selected node. You can select nodes in either the tree or the wireframe to view the properties collected by the SDK. The SDK will report on the following keys for each node in the view: `alpha`, `visible`, `x`, `y`, `width`, `height`, `type`, and `identifier` if applicable, but there may be additional values specific to the SDK. This feature can be used as an exploratory tool to debug layout issues, visualize unnecessarily rendered content, or gain a better understanding of the relationship between views.