Premiere → Shade · Bosley Handoff Guide
EyeClap Studios · Bosley Project · RD → Kevin Handoff

Premiere to Shade
Handoff Guide

Three phases: create proxies in Premiere, consolidate the project to only what Kevin needs, then upload to Shade with the correct folder structure. Storage-lean workflow — no unnecessary footage leaves your machine.

Phase 1
Create proxies
Phase 2
Consolidate project
Phase 3
Upload to Shade
Phase 1
Create Proxies
Why proxies for this job
Kevin is replacing graphics on finished sequences — not recutting. Proxies give him lightweight, streamable versions of the footage so ShadeFS doesn't have to stream full-res media over his connection. He works on proxies, you do the final export from your original media.
01
Open your Bosley project in Premiere Pro
Make sure all your sequences are finalized and named clearly before creating proxies. Rename any sequences with generic names now — Kevin will be navigating these by name.
02
Select the clips in your sequences
In the Project panel, select only the clips that are used in the sequences you're handing to Kevin. You can right-click a sequence → Select in Project to highlight the relevant clips automatically.
03
Create proxies via Ingest Settings
With clips selected, right-click → Proxy → Create Proxies. A dialog will appear.
Format: H.264 — widely compatible, small file size
Preset: GoPro CineForm 1280x720 (Proxy) or Low Resolution Proxy — 720p is sufficient for a graphics replacement job
Destination: Create a folder on your local drive called Bosley_Proxies — you'll upload this folder to Shade in Phase 3
Click OK — Media Encoder will open and process the proxies in the background
04
Confirm proxies are attached
When Media Encoder finishes, return to Premiere. In the Program Monitor, click the wrench icon → enable Toggle Proxies button. Click it to confirm your timeline switches to proxy media. You should notice the resolution drop slightly — that's correct. Toggle it back to full res when you're done confirming.

Phase 2
Consolidate the Project
What consolidation does
Premiere's Project Manager copies only the media actually used in your selected sequences — trimmed with handles — into a new self-contained folder. This is what keeps your Shade upload lean. Instead of the full camera roll, Kevin only gets the clips that appear in the edit.
01
Open Project Manager
Go to File → Project Manager. This is Premiere's tool for packaging and consolidating projects.
02
Select only the sequences Kevin needs
In the Project Manager dialog, you'll see all your sequences listed. Uncheck everything except the Bosley sequences you're handing off. This is the most important step — it determines what media gets included.
03
Configure the Project Manager settings
Set these options in the dialog:
Action: Collect Files and Copy to New Location
Options: Check Include Preview Files — OFF. Check Include Audio Conform Files — OFF. These add bulk you don't need.
Include Handles: set to 25 frames — gives Kevin a little breathing room on clip edges without copying the entire clip
Convert Image Sequences to Clips: OFF unless you have image sequences in the edit
04
Set the destination folder
Click Browse and create a new folder called Bosley_Consolidated on your local drive. This will be the folder you upload to Shade. Click OK to run the consolidation — Premiere will copy everything into that folder.
05
Copy your proxies into the consolidated folder
Project Manager copies original media, not proxies. Manually copy your Bosley_Proxies folder from Phase 1 into the Bosley_Consolidated folder. Keep them in a clearly named subfolder so they're easy to find.
06
Open the consolidated project and relink proxies
Open the new .prproj file inside Bosley_Consolidated. Premiere may show offline media or unlinked proxies. Right-click any offline clip → Link Media → navigate to the consolidated folder to relink. Once one clip relinks, Premiere will usually find the rest automatically. Confirm the proxy toggle still works before moving on.

Phase 3
Upload to Shade
Target folder structure
Everything goes into the Bosley client folder inside your EyeClap + NEEBA drive, following the _ASSETS / _PROJECT / _DELIVERY convention.
EyeClap + NEEBA drive
Bosley
_ASSETS
Camera (trimmed consolidated media)
Proxies (Bosley_Proxies folder)
Graphics (any source graphic files)
_PROJECT
Bosley_Consolidated.prproj
_DELIVERY
(empty for now — Kevin's exports go here)
01
Open the Shade web app or desktop app
Go to app.shade.inc or open the desktop app. Navigate to the EyeClap + NEEBA drive → Bosley folder. If you haven't created the Bosley folder and subfolders yet, do that now: _ASSETS, _PROJECT, _DELIVERY.
02
Upload the consolidated media to _ASSETS
Navigate into the _ASSETS folder. Drag and drop the media subfolder from your Bosley_Consolidated folder — the trimmed camera files and the Proxies folder. Shade recommends dragging and dropping large folders rather than using the file picker for better reliability on large uploads.
03
Upload the project file to _PROJECT
Navigate into _PROJECT. Drag and drop Bosley_Consolidated.prproj. This is the file Kevin will open directly from the mounted Shade drive — it's small and uploads in seconds.
04
Wait for upload and AI indexing to complete
Watch the bottom of the Shade interface — it shows upload progress and AI indexing status. Don't send Kevin the project until indexing is complete. You'll see 0 of X AI indexed tick up in the bottom left. Once done, Shade's AI search can find clips by scene, face, or transcript.
05
Confirm the structure looks correct
Before inviting Kevin, browse through the Bosley folder in Shade and confirm: media is in _ASSETS, project file is in _PROJECT, _DELIVERY is empty and ready. Take a screenshot of the folder structure and include it in Kevin's onboarding message so he knows where everything lives before he logs in.
Next step after this guide
Once the upload is confirmed, Kevin gets his Shade invite, installs the desktop app, mounts the EyeClap + NEEBA drive, and opens the project file directly from the cloud. A separate guide covers Kevin's setup and the ShadeFS remote editing workflow.