Open the editor
Workflows

Phone to browser: the import stage

Most ReelWorkshop projects start on a phone. This stage covers getting footage off the device and into the browser cleanly, before you touch trimming or ordering.

Last reviewed September 20, 2026

The phone-to-browser stage is just data transfer, but it's where a lot of avoidable friction happens: wrong file formats, huge files that stall an upload, or clips that never made it off the device at all. Treat it as its own step with its own checklist rather than something you do halfway while also trying to edit.

Pick a transfer method that fits your volume

For a handful of clips, AirDrop, a cable, or a cloud sync folder (Google Photos, iCloud, a shared drive) all work fine — drag the resulting files into ReelWorkshop's import area or use the file picker. For dozens of clips shot over a weekend, a cable transfer to a laptop is usually faster than waiting on a cloud sync to finish uploading everything before you can download it back down.

MethodBest forWatch out for
Cable to computer20+ clips, large filesDriver or permission prompts on first connect
AirDrop / Nearby ShareA handful of clips, same ecosystemSlows down with many files at once
Cloud sync folderClips already backed upFull-resolution originals may not sync by default
Direct browser importA few clips, quick projectMobile browsers can struggle with very large files

Check format and length before you import

Phones default to formats that generally import fine, but screen-recorded or app-downloaded clips can arrive in unusual containers or with odd rotation metadata. Skim through what you're about to import and drop anything that won't open or play back correctly on the device — fixing it before import is faster than debugging it inside a project. If a file won't import, check the current supported-format guidance in the app rather than guessing.

Import in ReelWorkshop

  1. Open a project

    Start a new project or open an existing one where these clips belong.

  2. Drag or pick files

    Bring in up to 100 clips per project. Batch them in if you have a lot rather than trickling them in one at a time.

  3. Let fingerprinting and scoring run

    Each clip is fingerprinted locally for exact-duplicate detection and gets an automatic quality score. Both happen automatically, no action needed.

  4. Confirm the count

    Check that the number of imported clips matches what you expected before you move on to trimming or ordering.

Duplicate detection is advisory

Exact-duplicate fingerprinting catches identical files, which happens more than you'd think with cloud-synced footage saved in two places. It will not catch a near-duplicate retake of the same shot — you still have to eyeball those.

Mistakes at this stage

  • Importing straight from a cloud thumbnail-quality proxy instead of the full-resolution original.
  • Bringing in every clip on the device instead of a rough cull, which just pushes the sorting work downstream.
  • Not checking orientation before import, then discovering half the clips are sideways once you're arranging.
  • Closing the browser tab mid-import on a slow connection and assuming it will resume where it left off.

When to skip straight to a different stage

If your footage is already organized on a computer with sensible filenames, you don't need this stage at all — go straight to naming or the first-pass selection. This stage exists specifically for the phone-as-primary-camera case, which is most short-form creators most of the time.