> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/plugins/first-party-ango-plugins/file-explorer-for-multi-page-assets.md).
# File Explorer for Multi-Page Assets
## Overview
The File Explorer for Multi-Page Assets plugin is a file explorer plugin that imports folders from an AWS S3 storage integration as multi-page assets.
Use this plugin when each asset should be built from the files inside one S3 folder. The folder name becomes the asset external ID, and the files inside that folder become the pages of the imported asset.
## Plugin Functionality
The plugin lets you browse an AWS S3 bucket connected to Ango Hub through a storage integration. When you run the import, the plugin looks for subfolders in the selected folder and creates one multi-page asset per subfolder.
For example, if your selected folder contains:
```
case-001/page-1.png
case-001/page-2.png
case-002/page-1.png
case-002/page-2.png
```
the plugin imports two assets:
* `case-001`, with `page-1.png` and `page-2.png` as pages
* `case-002`, with `page-1.png` and `page-2.png` as pages
{% hint style="info" %}
Each subfolder must contain at least one file and no more than the maximum page limit supported by the plugin. Folders outside that range are skipped.
{% endhint %}
## Using the File Explorer for Multi-Page Assets Plugin
First, ensure you have created a storage integration between Ango Hub and the private bucket where the files you wish to import are stored. [More information on how to do so can be found here](/data/storages/importing-private-cloud-assets-aws.md).
Then, navigate to the project where you'd like to import the assets.
Enter the *Settings* tab, then the *Plugins* section.
Find the *File Explorer for Multi-Page Assets* plugin and click *Open*. From the plugin dialog, select the storage, bucket, and folder to import from.
In *Batch*, you may pick one or more batches to which assets imported in this session will be assigned.
In the Config JSON area, you can tweak a number of settings. By default, they are:
```json
{
"prevent_duplicates": false,
"accepted_extensions": [],
"ignored_extensions": [],
"start_index": null,
"end_index": null
}
```
* **"prevent\_duplicates":** When `true`, the plugin skips folders whose folder name already exists as an external ID in the project.
* Example:
* "prevent\_duplicates": true
* "prevent\_duplicates": false
* **"accepted\_extensions":** Imports only files with the listed extensions. Leave the list empty to accept all extensions.
* Example:
* "accepted\_extensions": \["jpg", "png"]
* **"ignored\_extensions":** Skips files with the listed extensions.
* Example:
* "ignored\_extensions": \["txt"]
* **"start\_index"** and **"end\_index":** Import only a slice of the discovered folders. Index values start at 0. Setting a value to `null` means the plugin uses the beginning or end of the list.
* Example:
* "start\_index": 0
* "end\_index": 100
---
# 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://docs.imerit.net/plugins/first-party-ango-plugins/file-explorer-for-multi-page-assets.md?ask=&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.
