> ## Documentation Index
> Fetch the complete documentation index at: https://new.docs.falkordb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Metadata View

> Query execution details: metadata text, explain plan tree, and profile output.

The Metadata tab provides query execution details for the current query.

<img src="https://mintcdn.com/falkordb-core/4RKo-4HTPunDsB0h/images/browser/metadata-view.png?fit=max&auto=format&n=4RKo-4HTPunDsB0h&q=85&s=7460390a54d60345fe6b15f14bccd2a0" alt="Metadata view" width="1920" height="1200" data-path="images/browser/metadata-view.png" />

## Sections

The UI is split into three main panels:

* **Profile**
  * Runs a profiling request and renders the output as a nested tree.
  * Warning: profiling can be intrusive depending on the database behavior.
* **Metadata**
  * Displays metadata text lines.
* **Explain**
  * Displays explain-plan output as a nested tree.

## When it’s enabled

The Metadata tab is enabled when the current query has metadata/explain content.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="What is the difference between Explain and Profile?">
    **Explain** shows the planned execution steps without running the query. **Profile** actually executes the query and shows real performance data including time spent at each step.
  </Accordion>

  <Accordion title="When is the Metadata tab available?">
    The Metadata tab is enabled when the current query has **metadata or explain content** available. It appears alongside the Graph and Table tabs in the results area.
  </Accordion>

  <Accordion title="Is Profile safe to run on production?">
    Be cautious — profiling **actually executes the query** and can be intrusive depending on database behavior and query complexity. Use Explain for a non-invasive execution plan.
  </Accordion>

  <Accordion title="How is the execution plan displayed?">
    Both Explain and Profile output are rendered as a **nested tree** structure, showing the hierarchy of operations in the query execution plan.
  </Accordion>
</AccordionGroup>