Camera footage is usually higher quality than phone footage but also messier to bring in — flat file structures full of numbered filenames, occasional proprietary formats, and much larger file sizes. This stage is about landing that footage on a desktop in usable shape before it ever touches ReelWorkshop.
Offload the card first, edit later
Copy the entire card contents to a folder on your computer before you do anything else. Don't import straight from the card into the browser — card readers are slower than local disks and you risk losing footage if the card gets ejected mid-transfer. Once the copy finishes, verify the file count on disk matches what's on the card.
Check the format ReelWorkshop expects
Some cameras record in formats or containers that need converting before a browser-based tool can read them. Check the current supported-format list in the app, and if your camera outputs something unusual, convert to a standard MP4/H.264 file with a free tool before import rather than finding out mid-project that a batch of clips won't load.
Cull on the desktop, not in the browser
A card often holds far more footage than you'll ever use — false starts, duplicate takes, test shots. Do a rough pass on the desktop first: delete or move aside anything obviously unusable (black frames, out of focus, wrong framing). ReelWorkshop caps projects at 100 clips, so arriving with 300 raw files means you'll be culling inside the tool anyway; doing it earlier saves import time and clutter.
| Task | Where to do it | Why |
|---|---|---|
| Copy card to disk | Desktop file manager | Reliable, fast, no browser dependency |
| Format conversion | Desktop tool, before import | Avoids in-browser import failures |
| Rough cull of unusable takes | Desktop, folder view | Keeps the 100-clip cap for footage worth keeping |
| Final selection and scoring | ReelWorkshop | Uses fingerprinting and quality scoring on what's left |
Bring the culled folder into ReelWorkshop
Once you have a folder of candidate clips, drag them into the import area the same way you would phone footage. Each gets fingerprinted for exact duplicates and scored automatically. If your camera shot several takes of the same setup, expect the duplicate check to miss near-identical takes — that's a manual call in the next stage, not this one.
Camera footage at high bitrates imports and later renders more slowly than compressed phone video. Budget extra time for import on a large card, and don't assume a stalled progress bar means failure — check before restarting the tab.
Mistakes at this stage
- Editing directly off the card and losing work when it's ejected or reused.
- Skipping the desktop cull and importing everything, then hitting the 100-clip project cap mid-way through a shoot's worth of footage.
- Assuming a camera-native format will import without checking first.
- Losing track of which folder is the original backup versus the working copy.
When this stage doesn't apply
If you shoot exclusively on a phone, skip this and use the phone-to-browser stage instead — the two exist because the source hardware genuinely changes the early steps, not because the destination editor differs.