> 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/guides/editing-integrations/edit-remotely-over-shadefs.md).

# Edit remotely over ShadeFS

Size your cache, pin footage for offline work, and choose the right media for your connection, so remote editing feels local.

**Outcome:** a mounted Shade drive that your editing app plays smoothly from home, on set, or on a plane.

**Who it's for:** editors and assistants working outside the office, or anyone whose playback stutters over a mounted drive.

**Time:** about 20 minutes.

## Before you start

* Install the Shade desktop app. You need to be a workspace member or contractor to mount drives. Guests can't mount.
* Run a [speed test](https://www.speedtest.net/) and note your download speed.
* Have an external SSD available if you can. A Samsung T7 or similar works well.

## Steps

{% stepper %}
{% step %}

### Check your connection against your media

For smooth playback, your download speed should be at least the bitrate of the media you're cutting. Rough guide:

| Media        | Typical bitrate   | Connection you want |
| ------------ | ----------------- | ------------------- |
| 1080p H.264  | 8 to 15 Mbps      | 25+ Mbps            |
| 4K H.264     | 35 to 100 Mbps    | 100+ Mbps           |
| 1080p ProRes | 100 to 300 Mbps   | 100+ Mbps           |
| 4K ProRes    | 500 to 1,500 Mbps | 1 Gbps+             |

If your connection falls short, edit with proxies (see the next step) or pin the footage before you need it. Full tables are in [Understanding Internet Speeds and ShadeFS Storage](https://academy.shade.inc/shadefs/understanding-internet-speeds-and-shadefs-storage).
{% endstep %}

{% step %}

### Use proxies when bandwidth is tight

Shade generates proxies for uploaded video automatically. Cut with the proxies, then relink to the originals for the finishing pass, ideally on a fast connection or from pinned files. Each editing app handles this differently. See the [Premiere Pro](/guides/editing-integrations/how-to-use-shade-with-adobe-premiere-pro.md), [DaVinci Resolve](/guides/editing-integrations/how-to-use-shade-with-davinci-resolve-projects.md), [Avid](/guides/editing-integrations/how-to-use-shade-with-avid-media-composer.md), and [Final Cut Pro](/guides/editing-integrations/how-to-use-shade-with-final-cut-pro.md) guides.
{% endstep %}

{% step %}

### Move the cache to a fast SSD and size it for your project

The cache holds the parts of files you've played recently. By default it's 26 GB in the `.shade` folder in your home directory, which is small for video work.

In the desktop app, open **Settings > ShadeFS > Cache Management**:

* Set **ShadeFS cache directory** to a folder on your SSD. The disk must be formatted as APFS (macOS), NTFS or ReFS (Windows), or ext4, XFS, or Btrfs (Linux). exFAT and Mac OS Extended won't work.
* Set the cache size to roughly the media you touch in a typical week of the project.

See [Managing the ShadeFS Cache](https://academy.shade.inc/shadefs/managing-the-shadefs-cache) and [Choosing an External SSD for Shade Cache](https://academy.shade.inc/shadefs/choosing-an-external-ssd-for-shade-cache).
{% endstep %}

{% step %}

### Mount the drive

In the app's sidebar, open the drive's **…** menu and choose **Mount Drive**. On macOS it appears under `/Volumes`. Point your editing project at media on the mounted drive, not at copies on your desktop.
{% endstep %}

{% step %}

### Pin what you'll need offline

Before you travel or move to a weak connection, right-click the project's footage folder and choose **Pin to Cache**. Pinned files are downloaded completely, don't count toward the cache size limit, and stay available offline. On macOS you can also pin from Finder.

Changes you make offline sync when you reconnect. If two people change the same file, the most recent change wins. Find everything you've pinned on the **Pinned Items** page. See [Pinning Files Offline](https://academy.shade.inc/shadefs/pinning-files-offline).
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
Files deleted from the mounted drive in Finder or Explorer can't be recovered from Shade's trash. Delete from the Shade app when you might want the file back.
{% endhint %}

## Variations

* **Several editors in one office:** put a shared cache server on the local network, so footage one person has opened plays at LAN speed for everyone else. See [Using Shared Cache](https://academy.shade.inc/shared-cache/using-shared-cache).
* **Big uploads:** for more than about 1,000 files or 100 GB, upload through the app rather than copying into the mounted drive.

## Related guides

* [How to use Shade with Adobe Premiere Pro](/guides/editing-integrations/how-to-use-shade-with-adobe-premiere-pro.md)
* [Send Shade metadata into your editing app](/guides/editing-integrations/send-shade-metadata-into-your-editing-app.md)
* [Roll out Shade company-wide](/guides/setup-and-migration/roll-out-shade-company-wide.md)


---

# 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 dynamically 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/guides/editing-integrations/edit-remotely-over-shadefs.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 `build a script that syncs our docs to a CMS` 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.