diff --git a/docs/platforms/native/common/enriching-events/attachments/index.mdx b/docs/platforms/native/common/enriching-events/attachments/index.mdx
index 9b5e2bbf5cd6cc..3a2fdb61037b7c 100644
--- a/docs/platforms/native/common/enriching-events/attachments/index.mdx
+++ b/docs/platforms/native/common/enriching-events/attachments/index.mdx
@@ -56,3 +56,13 @@ Alternately, attachments also appear in the _Attachments_ tab on the **Issue Det
 <Include name="common-imgs/attachments-list-example" />
 
 If you chose to limit the number of crash reports per issue, you can show _Only Crash Reports_. This removes all other attachments from the list, which can be useful if the issue has accumulated a large number of events.
+
+## Attaching view hierarchy
+
+<PlatformContent includePath="enriching-events/attach-viewhierarchy" />
+
+<Alert> The file must have the exact name `view-hierachy.json`, as described in [RFC#33](https://github.com/getsentry/rfcs/blob/main/text/0033-view-hierarchy.md). </Alert>
+
+Along with the file appearing in the _Attachments_ tab, it is visualized on the issue as such:
+
+<Include name="common-imgs/viewhierarchy-example" />
diff --git a/platform-includes/enriching-events/attach-viewhierarchy/native.mdx b/platform-includes/enriching-events/attach-viewhierarchy/native.mdx
new file mode 100644
index 00000000000000..af0648953b8c93
--- /dev/null
+++ b/platform-includes/enriching-events/attach-viewhierarchy/native.mdx
@@ -0,0 +1,5 @@
+To add a view hierarchy attachment, the path to the file has to be configured when initializing the SDK. It will monitor the file and upload it along with any event or crash that is sent to Sentry:
+
+```c
+sentry_options_add_view_hierarchy(options, "./view-hierarchy.json");
+```