Import Workflow

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Stop duplicating your files. This lesson covers the single biggest storage mistake creators make and how to fix it.

⚠️ Critical Issue

If your FCP library is hundreds of gigabytes AND you still have "original media" folders on your drive, you're storing everything twice. This lesson fixes that.

The Duplication Problem

By default, Final Cut Pro wants to copy media into the library. This creates massive duplication:

What happens:

• You have a 200GB folder of original camera files
• You import into FCP
• FCP copies all 200GB into the library
• Now you have 400GB of identical files

Do this for a year and you'll burn through terabytes of storage unnecessarily.

The Two Import Methods

❌ Copy to Library (Default)

How it works: FCP copies all media files into the library bundle.

Result: Massive library files, duplicate storage.

Use when: Working with media you'll delete original files afterward, or need maximum portability.

✅ Leave Files in Place (Correct)

How it works: FCP references original files without copying them.

Result: Lean library (just the database), no duplication.

Use when: Keeping organized original media folders (which you should).

Setting Up Leave Files in Place

Make It the Default

1 Open Final Cut Pro > Settings

2 Click the Import tab

3 Under "Files:", select "Leave files in place"

4 Click OK

Done. All future imports will reference files instead of copying them.

🎯 Pro Tip

Uncheck "Create optimized media" and "Create proxy media" in the same settings. You can always generate these later if needed, and they take up massive space.

The Correct Import Workflow

Step-by-Step Process

  1. Organize original files first - Create folders on your drive:
    • 2025-12-16_JoshuaTree
    • 2025-12-18_Pinnacles
    • 2025-12-20_LostCoast
  2. Copy camera cards to these folders - Keep original folder structures intact
  3. Use File > Import > Media - Never drag-and-drop into FCP
  4. Verify "Leave files in place" is selected - Check the import dialog
  5. Import - FCP creates references, not copies

⚠️ Critical: Don't Drag Files Into FCP

Dragging files from Finder directly into FCP often triggers copying, even if your preference is set to "leave files in place." Always use File > Import > Media.

Folder Organization Strategy

Since you're keeping original files external, organization matters:

Recommended Structure

/Volumes/DriveA/Footage/

├── 2025/
│ ├── 01-January/
│ │ ├── 2025-01-05_JoshuaTree/
│ │ ├── 2025-01-12_Mojave/
│ │ └── 2025-01-20_SaltonSea/
│ ├── 02-February/
│ │ ├── 2025-02-03_Pinnacles/
│ │ └── 2025-02-15_BigSur/
│ └── ...

This structure:

What About Existing Libraries?

If you already have bloated libraries with copied media inside, you have two options:

Option 1: Keep It, Start Fresh

This is the safest, easiest approach.

Option 2: Relink (Advanced, Risky)

You can theoretically relink FCP projects to external media, but:

For most people, Option 1 is smarter: finish current projects, then start fresh with correct workflow.

Managing Multiple Drives

Van life often means working across multiple drives. Here's how to handle it:

Primary Workflow Drive

Archive Drive

Backup Drive

💡 Missing Media Handling

If FCP says "media offline," it usually means the external drive isn't connected. Plug it in, and FCP will automatically reconnect to the files. No relinking needed.

Storage Space Comparison

Let's look at real numbers for a typical van life creator:

Copying Method (Wrong):

Original footage: 500GB
Library with copied media: 500GB
Total: 1,000GB

Leave in Place Method (Correct):

Original footage: 500GB
Library (database only): 2GB
Total: 502GB

Savings: 498GB

That's enough space for another 10 weeks of shooting.

The Don'ts

Common mistakes to avoid:

The Checklist

Before your next import, verify:

☑ FCP preferences set to "Leave files in place"
☑ Original files organized in dated folders
☑ Using File > Import (not drag-and-drop)
☑ Verified setting in import dialog
☑ Library stays small after import

If all five are checked, you're doing it right.

The bottom line: Your library should be a lightweight database, not a massive storage container. Keep it under 10GB and your original files organized externally.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━