> For the complete documentation index, see [llms.txt](https://support.duplifyapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.duplifyapp.com/using-duplify/exporting-data/content-files.md).

# Content files

Options for exporting Shopify content files with Duplify

Duplify exports all files uploaded to your Shopify admin's **Content** > **Files**, including media such as images and videos used across your store. This allows you to move or back up all media assets without manually downloading and re-uploading them.

***

## Exporting content files

When you select the **Content files** option in Duplify:

* All media files from your source store are exported to your destination stores.
* This includes images and videos used in theme sections, blog posts, pages, product and collection descriptions, downloadable files for customers, and files linked to metafields.

#### Example

If your store has images in a blog post, promotional banner videos in the theme, and downloadable PDFs for customers, exporting content files with Duplify will transfer all of these assets to your destination store.

***

## Export events

Duplify tracks export events to determine the size of your store’s export. Each event represents one data item or file.

#### Content file export events

* Each file exported counts as **one export event**.

For a full overview of how Duplify counts export events, see our [Export events](https://support.duplifyapp.com/using-duplify/export-events.md) reference guide.


---

# 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 by asking a question.

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

```
GET https://support.duplifyapp.com/using-duplify/exporting-data/content-files.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 `automate deployments from our CI pipeline` 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.
