> 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/help-center/drive-faq/how-shadefs-works-real-time.md).

# How does ShadeFS work in real time?

For some, real-time might seem and sound like it's just google drive syncing or dropbox. The reality is, it's not! No, it's not instantly downloading a whole 100GB to your computer, unfortunately we cannot change your internet speed. But what we can do is model specific types of media files to your computer as if they feel like they are local. Why does this work? It's because certain types of files (like video, images, etc.) are read sequentially by a variety of programs (like Premiere Pro, Davinci Resolve, Video, etc.) this makes it possible for us to send parts of files while waiting for the entire file to actually download. That is what we mean by real-time here.

Now real-time is also about your team - Shade syncs changes completely in real-time. This means that if a file is added from computer A in New York, computer B in LA will be able to instantly see that file, a preview of that file, and drag and drop that into their editing program, instantly - no uploading or downloading required to even start. This enables your team to be able to quickly start working right when the files are ready - not when they are fully uploaded and downloaded again.


---

# 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/help-center/drive-faq/how-shadefs-works-real-time.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.
