> For the complete documentation index, see [llms.txt](https://docs.navless.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navless.ai/building-interactive-demos/interactive-tours/record/importing-media.md).
# Importing Media
When building media tours, you can upload media from your computer or pull entire screens from different tours.
## Option 1: Import from your Computer
Tourial accepts multiple file types to function as your primary screens within the tour: screenshots (images), videos, and gifs. Please note that when uploading media for screen background use, you'll want all of your media to be at a 16:9 aspect ratio and high resolution. \
\
Here's the full list of supported file types for media uploads in media tours: \
\
.mp4, .mov, .webm, .png, .jpeg, .jpg, .png, .gif, .svg, .webp
1. Either select Media Library in the bottom right or Add Screen in the Storyboard\
2. In the pop-up, click Upload to upload your images or videos.\
3. Once uploaded, select the screen and click Add to tour\
## Option 2: Import from another Tour
Let's say you built a page that you love in a previous Tourial. It has all the tools, views and interactions and now you want to use that page in another Tourial.
With the Import Screen feature, you can easily select a screen(s) from any existing Tour in your account and use it in a different one.
## To import a screen
1. Open the Tour you'd like the other page imported into
2. Select Media Library located on the right of the Storyboard
3. In the pop-up window, select Import screen and then choose with Tour you want to import from and the screen you want to import
4. Click Add to tour
**Note:** Tourial's file size limit for media imports is 99MB per file
---
# 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.navless.ai/building-interactive-demos/interactive-tours/record/importing-media.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.
