> 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/general-faq/how-good-does-my-wifi-have-to-be.md).

# How good does my wifi have to be?

A guide explaining that Shade works well on standard internet connections.

Shade is designed to work effectively across a wide range of internet connections. You don't need a perfect connection to use most of Shade's powerful features. Here's what you need to know about internet requirements for Shade.

### Most Shade features work great on standard connections

Even with modest internet speeds (under 50 Mbps), you can still effectively use most of Shade's core features:

* Playing back the web proxy
* Sharing with external collaborators
* Reviewing and leaving comments
* Creating collections
* Managing and editing metadata
* Generating transcriptions and AI metadata

These features are optimized to perform well even when your connection isn't blazing fast.

### Uploads and downloads

Uploading and downloading files directly from the webapp (outside of the ShadeFS mount) will work at whatever speed your internet connection provides. These operations will complete successfully regardless of connection speed—they'll just take proportionally longer on slower connections.

### ShadeFS considerations

The ShadeFS mount is where internet speed becomes more important. Since ShadeFS works by streaming bytes of media files on demand as you access them in your file explorer or NLE, connection quality directly impacts performance.

For optimal experience with ShadeFS, especially when working with high-resolution media, we recommend:

* A stable connection of at least 500 Mbps for working with 4K video
* Ideally, a wired gigabit ethernet connection for the most consistent performance

### Working with fluctuating connections

If you experience fluctuating performance during playback, Shade provides a solution: you can pin files offline through the Shade app. Pinning videos performs a full download to your local cache, allowing you to work with them smoothly regardless of connection quality.

<figure><img src="https://328109618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlvHrZ4ybpa07fNCxAfwz%2Fuploads%2Fd0RBMnGoYu5KcUeLiXlh%2FPinning.gif?alt=media&#x26;token=86b4456f-a99f-49ca-a576-fb53a561c436" alt=""><figcaption></figcaption></figure>

### The bottom line

Shade is built to be flexible across various internet environments. While a faster, more stable connection will enhance the ShadeFS experience, the majority of Shade's functionality remains highly usable even on standard connections. You don't need perfect internet to get great value from Shade.


---

# 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/general-faq/how-good-does-my-wifi-have-to-be.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.
