How it works
Nothing arrives until something asks for it.
A ReachFS drive is a filesystem, not a folder of downloads. Windows sees real sizes, permissions and modification dates for every file, and the bytes behind them stay in the cloud until an application reads them.
Step by step
Signed in and cutting in about a minute.
Sign in, and a drive appears
The ReachFS drive appears in Explorer beside your local disks, usually as R:. Every file your team has is already in it, with real sizes, permissions and modification dates, and none of it is on your disk. Explorer, your applications and the command line all treat it as an ordinary drive.
Time to mount1.4 s
Open and edit straight from it
Cut, grade and scrub straight off the drive. ReachFS pulls only the byte ranges your application asks for and keeps only what you actually touched, under a cache ceiling you set. Nothing is kept on your disk unless you ask for it.
Default cache ceiling50 GB
Find anything in milliseconds
Press Ctrl+Shift+Space for a search field over every drive you can reach. It indexes names, folders and media details such as codec, resolution and reel, so three letters is usually enough to open the file you meant.
Median search latencyunder 40 ms
Files land before they finish uploading
When a teammate writes to the drive, every other machine can open, scrub and edit that file while the upload is still running. There is no import step and no waiting for a transfer to complete before the work can continue.
Visible to others afterthe first chunk
Under the hood
What a scrub actually costs.
Playing four seconds of an 847 GB camera original needs the header, the index, and the frames under the playhead. ReachFS requests those ranges and caches them. The rest of the file is never touched.
- File size, as Explorer reports it
- 847.00 GB
- Bytes fetched to play it
- 41.20 MB
- Held in local cache
- 41.20 MB
- Added to your disk
- 0 B
Requirements
What it needs from your connection.
ReachFS adapts its read-ahead to the bandwidth it measures, so a slower link degrades into buffering rather than failure.
- 4K timeline, comfortable
- 100 Mbps
- Proxies, stills and documents
- 25 Mbps
- Offline
- pinned files only
- Supported
- Windows 10 and 11
Try it on a real project.
Seven days, the whole drive, no card until you decide.