> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/guides/editing-integrations/send-shade-metadata-into-your-editing-app.md).

# Send Shade metadata into your editing app

Bring tags, descriptions, statuses, and selects from Shade into Premiere Pro, Resolve, or Avid bins.

**Outcome:** the logging work done in Shade, such as AI tags, descriptions, ratings, and statuses, shows up as columns in your editing app's bins, so editors can sort and search footage without switching apps.

**Who it's for:** assistant editors and editors who log in Shade and cut in Premiere Pro, DaVinci Resolve, or Avid Media Composer.

**Time:** about 10 minutes.

## Before you start

* Fill in the fields you want to carry over. AI-filled fields work too. See [Metadata and Custom Fields](https://academy.shade.inc/ai-tools/custom-and-automated-metadata).
* Import the same media into your editing app from the mounted Shade drive. Exports are matched to clips, so the clips have to be the same files.

## Steps

{% stepper %}
{% step %}

### Build a view with only the columns you want

Create a view, or open an existing one, and show only the fields editors need, for example Description, Tags, Shot type, Rating, and Status. Filter it to the footage you're working with. You'll export from this view in the next step.
{% endstep %}

{% step %}

### Export with your editing app's preset

Open the view's **More options** (**…**) menu, choose **Export**, and pick the preset:

* **Premiere Pro**: exports an ALE file
* **Avid Media Composer**: exports an ALE file
* **DaVinci Resolve**: exports a CSV file

CSV, TXT, ALE, and TSV are also available for other tools. In a collection, the same options are in the collection's download menu.
{% endstep %}

{% step %}

### Import into your editing app

* **Premiere Pro and Avid:** import the ALE into the project. The metadata merges onto clips with matching names.
* **DaVinci Resolve:** select the clips in the media pool, then import the CSV metadata. In the import options, turn off **Match using clip start and end Timecode**, or the clips won't match.
  {% endstep %}
  {% endstepper %}

## Variations

* **Comments, not metadata:** export review comments from the comments panel menu. Resolve users can choose **Export to Resolve (EDL)** to bring notes in as timeline markers. See [The client review loop](/guides/review-and-client-delivery/the-client-review-loop.md).
* **Subtitles and scripts:** export transcripts as SRT, VTT, or ScriptSync from the asset's **Transcription** panel.

## Related guides

* [Edit remotely over ShadeFS](/guides/editing-integrations/edit-remotely-over-shadefs.md)
* [Design a metadata schema that scales](/guides/custom-objects-and-metadata/design-a-metadata-schema-that-scales.md)
* [Build a searchable archive](/guides/search-ai-and-archives/build-a-searchable-archive.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.shade.inc/guides/editing-integrations/send-shade-metadata-into-your-editing-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.