> 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/shade-academy/shade-academy-zh/kai-shi-shi-yong/start-uploading-assets.md).

# 开始上传素材

你可以从浏览器、手机、桌面应用、文件管理器、飞机、三星智能冰箱向 Shade 上传——你懂我的意思。

{% embed url="<https://youtu.be/ja56PFUPS4I?si=VvOfJKxpGDYFDiki>" %}

<figure><img src="https://3843445310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUNq6h2Bfw7aAK0J2ffnZ%2Fuploads%2FhTSVnJ8WsVK7BRhs3aeV%2FUpload.gif?alt=media&amp;token=d2430ee5-f818-4df8-a0f0-b02ed3bf4711" alt=""><figcaption></figcaption></figure>

## 从浏览器上传

这就像拖放一样简单。就这样。如果你想更花哨一点，也可以点击右上角的上传按钮。

## 从桌面应用上传

同样也很简单——只需拖放，或点击右上角的按钮。

## 从已挂载的驱动器上传

由于 Shade 在你的桌面上可以像已挂载的驱动器一样工作，你也可以把它当作驱动器来使用。你上传到已挂载驱动器的任何内容都会自动在应用中建立索引。

## 上传状态

当文件上传到 Shade 时，你可以在左下角的状态菜单中查看上传状态。打开此菜单会显示你的资产当前所在的任务状态，包括：

{% tabs %}
{% tab title="上传状态" %}

* 每个驱动器的上传名称、大小、位置和时间戳
* 可停止和启动上传，以及导航到已上传文件的能力
  {% endtab %}

{% tab title="下载状态" %}

* 下载的名称、状态和时间戳
* 这些是否为 Shade 生成的代理文件
  {% endtab %}

{% tab title="索引状态" %}

* 基础任务，包括文件同步、元数据更新，以及预览/代理文件生成
* AI 任务，包括视觉和音频索引，以及自定义元数据生成
* 附加任务，包括色彩调色板、面部识别和转录
  {% endtab %}

{% tab title="挂载状态" %}

* 与已挂载驱动器的同步状态
  {% endtab %}
  {% endtabs %}


---

# 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://academy.shade.inc/shade-academy/shade-academy-zh/kai-shi-shi-yong/start-uploading-assets.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.
