Workflows
Every workflow, one drive in Finder.
goframe drive is a real disk on your Mac, so editors, renderers, photo apps and agents use it the way they use any disk. Here is what changes for five kinds of team.
01Video and post-production
Cut from the drive. Skip the download.
The shoot is in the cloud and the edit waits. Someone downloads the camera originals, fills a disk, relinks, and does it all again for the colorist. A day of footage still travels fastest in a courier’s bag.
With goframe drive
- 01.1
Plays before it downloads
Point your editor at
/Volumes/<drive>. Your Mac fetches only the parts the player reads, and reads ahead of it: up to 16 MiB, 16 workers in parallel. - 01.2
A jump costs one small fetch
Scrub anywhere and the drive fetches the piece under the playhead. Every piece is checked against its SHA‑256 before a frame reaches the app.
- 01.3
Exports finish at disk speed
Export into the drive, close the file and keep working. It uploads in the background and resumes after a crash.
Apps involved
- DaVinci Resolve
- Premiere Pro
- Final Cut Pro
- Avid Media Composer
- QuickTime Player
02Motion, 3D and VFX
Render into the drive. The team sees every frame.
An image sequence is thousands of files; a project is scenes, textures, plates and caches. Syncing the whole tree to every machine fills disks, and a render that writes to the cloud waits on the uplink for every frame.
With goframe drive
- 02.1
The whole project, nothing synced
Every folder is there at once; a file is fetched when an app reads it. Finder sees a 1 PiB volume, so the size of your Mac’s disk is not the limit.
- 02.2
Frames land at disk speed
A frame is done the moment it is journaled on your Mac, so the renderer does not wait on the uplink. Behind it, four files upload at a time.
- 02.3
Everyone sees the new frames
When a frame’s upload lands, it appears on every Mac and in every browser within seconds.
Apps involved
- After Effects
- Blender
- Cinema 4D
- Houdini
- Nuke
- Unreal Engine
03Photography
From the card to the client. No download in between.
A wedding or a campaign is hundreds of gigabytes of RAW files. They get copied to a laptop, to a sync folder, to a gallery service — and the retoucher still asks which folder has the selects.
With goframe drive
- 03.1
Offload straight into the drive
Copy the card into the drive in Finder. The copy finishes at the speed of your disk; the upload follows in the background.
- 03.2
The whole shoot, almost nothing on your Mac
Every file is listed at once, and a photo is fetched when an app reads it. Pin a folder to keep it on this Mac.
- 03.3
A link for the client
Share the selects with a read-only link: the client browses, previews JPEG, PNG and WebP, and downloads what they need. No account.
Apps involved
- Lightroom Classic
- Capture One
- Photoshop
- Finder
04Studios and agencies
One workspace for the studio. Freelancers and clients included.
Every project brings new people: an editor for two weeks, a colorist abroad, a client who only needs the cut. They end up in five tools, with files in e‑mail attachments and “final_v7_REAL.mov” in six places.
With goframe drive
- 04.1
Four roles
Owner, admin, editor and viewer. Invite people by e‑mail from the web app; an invitation stays valid for 14 days.
- 04.2
Share a drive, not the studio
Give a freelancer one drive, Can view or Can edit, and it appears under Shared with me.
- 04.3
Links for clients
A read-only public link opens in any browser without an account. Rotate it or revoke it when the project wraps.
Apps involved
- Finder
- Any modern browser
05AI agents and scripts
Give your agents a path. Not an SDK.
Agents and scripts want files, and cloud storage hands them an API: keys, an SDK, a download step, an upload step, and a copy of everything on the machine that runs them.
With goframe drive
- 05.1
It is just a path
Claude Code, Codex, a Python script or a shell loop read
/Volumes/<drive>with ordinary file calls. No plug-in, no SDK, no keys to hand out. - 05.2
Streams, doesn’t download
An agent that reads the headers of 500 clips fetches only what it reads, not 500 whole files. The rest of the library stays in the cloud.
- 05.3
Its output reaches the team
What an agent writes into the drive uploads in the background; once it lands, every Mac and browser sees it within seconds.
Apps involved
- Terminal
- Claude Code
- Codex
- Cursor
- VS Code
- Python
App by app
Media on the drive. Caches on the Mac.
One rule covers every app: originals and deliverables live on goframe drive, where everyone sees them; caches and render files live on your Mac’s SSD, where they change constantly and never need to upload.
DaVinci ResolveEdit, color, finishing
Browse the drive from the Media page
Add /Volumes/<drive> in Preferences › System › Media Storage, and the Media page browses it like any disk. In Project Settings › Master Settings › Working Folders, point cache files and gallery stills at your Mac’s SSD.
Playback verified
On goframe drive
- Camera originals
- Audio and music
- Exports and deliverables
On your Mac
- Cache files
- Gallery stills
- Project library
Premiere ProEdit
Keep the media cache local
In Settings › Media Cache, keep the media cache on your Mac’s SSD. In File › Project Settings › Scratch Disks, send video previews and auto-saves there too, then import footage straight from the drive.
On goframe drive
- Footage
- Graphics and music
- Exports
On your Mac
- Media cache
- Video previews
- Auto-saves
Final Cut ProEdit
Leave files in place
Keep the library on your Mac and import from the drive with Leave files in place, so the library points at the originals instead of copying them. The library’s Storage Locations can keep cache and backups on the SSD.
On goframe drive
- Camera originals
- Music and graphics
- Exports
On your Mac
- Library
- Render files and cache
- Library backups
After EffectsMotion and compositing
Render into the drive, cache on the Mac
Point Settings › Media & Disk Cache at a folder on your SSD. In the Render Queue, set Output To a folder on the drive: each frame finishes at disk speed and uploads in the background.
On goframe drive
- Footage and plates
- Image sequences
- Renders
On your Mac
- Disk cache
- Conformed media cache
Blender3D
Output to the drive, bakes on the SSD
Set Output Properties › Output to a folder on the drive and every rendered frame reaches the team. Point simulation and bake caches at your Mac’s SSD: they are rewritten constantly and never need to upload.
On goframe drive
- .blend files
- Textures and HDRIs
- Rendered frames
On your Mac
- Simulation caches
- Bakes
- Temporary files
These are each app’s own settings, not integrations: goframe drive is a disk, and apps treat it as one. Menu names are from current versions and may differ in yours.
Put the next project on a drive. Free in early access.
macOS 26.0+ · Apple silicon