The Google Drive Folder Template Every Wedding Videographer Should Steal

Every wedding videographer has the same ritual. Couple signs the contract → open Google Drive → right-click → “New folder” → type the client’s name → open it → create five more folders inside (RAW, Proxies, Exports, Delivery, Archive) → copy the Drive link → paste it into the project card → forget which field you pasted it in three weeks later when you’re mid-edit.

Five minutes per project. Thirty projects a year. That’s 2.5 hours of pure right-clicking. The hidden cost isn’t the time — it’s the inconsistency. One project ends up Anna & Lars Wedding Aug 2026, the next is Wedding_Kovacs_2026-09, the third is just Sofia. When you come back six months later to grade a highlight reel for a portfolio update, you waste ten minutes hunting.

You can fix this for every future project in a weekend. Here’s how.

The naming convention that scales

Before you automate anything, commit to one naming pattern. If you’ve been doing this five years, you’ve probably got three patterns living in your Drive right now. Pick one and stick with it.

The convention I recommend for wedding and event work:

YYYY-MM-DD_ClientName_EventType/

Examples:

• 2026-08-15_Anna-Lars_Wedding/
• 2026-09-22_Kovacs_Engagement/
• 2026-10-04_Sofia-Marco_Elopement/

Why this exact shape:

• Date first, ISO format. YYYY-MM-DD sorts chronologically by default in any file system, in Drive, in Dropbox. No more scrolling for “the wedding in August”.
• Hyphens, not spaces. URLs, terminal commands, and Finder search all work better without spaces. You’ll thank yourself when you’re in a rush at 11pm exporting a version.
• Couple’s first names, hyphenated. Anna-Lars is faster to scan than Dvorakova-Hoffman. Save last names for the contract.
• Event type at the end. You’ll shoot engagement shoots, save-the-dates, rehearsal dinners, and reception-only gigs for the same couple. Suffixing the event type lets you see all three in a sorted list.

The killer feature of this convention is what happens when a bride emails you in 2028 asking for raw footage from her 2026 wedding — you search her first name, get the right folder in one click, sorted by date, labelled by event.

The five subfolders every wedding project needs

Inside every project folder, the same five subfolders. Every time. No variation. Consistency is the entire point.

2026-08-15_Anna-Lars_Wedding/
├── 01_RAW/
├── 02_Audio/
├── 03_Proxies/
├── 04_Exports/
└── 05_Delivery/

The numbered prefixes force sort order. Without them, Drive alphabetises and Audio shows up before RAW even though RAW is the first thing you touch on every job. Numbers = control.

01_RAW — every card you offloaded, untouched. Never edit here. Archive-grade. This is the folder your couple’s grandkids will thank you for in 30 years if you still have it.

02_Audio — external recorder files (Zoom, Tascam), lav mic recordings, ambient. Separated from RAW because audio has different backup windows — easier to lose, cheaper to store long-term, frequently synced after delivery.

03_Proxies — transcoded proxy files for editing. ProRes Proxy, H.264, whatever your NLE wants. Regenerable, so you can delete these after delivery if storage gets tight.

04_Exports — intermediate exports during the edit. Rough cuts, color grades in progress, client review cuts, versions you sent to music licensing. This is where you want version-stacking (v01, v02, v03) with a README noting what each is.

05_Delivery — final deliverables. The 4-minute highlight, the 45-minute documentary edit, the IG-vertical cut, the teaser for social. The folder you actually share with the couple.

You might want a sixth folder (06_Source/ for photos from the photographer, family reference photos, shot list PDFs). Start with five and add the sixth only when you have a consistent need for it.

Step 1: Build the template once

Now create this structure once, as a template.

In Google Drive: create a folder named TEMPLATE_WeddingProject/ inside a Studio Templates/ parent. Inside the template, create the five numbered subfolders. When you start a new project, right-click → “Make a copy”.

In Dropbox: same idea. TEMPLATE_WeddingProject/ in a Studio Templates/ parent. Right-click → “Copy” clones the folder and all subfolders.

This alone saves you half the folder-creation tax. You still have to rename, but the structure is pre-built.

Step 2: Pick a place for the project root

Decide where every YYYY-MM-DD_ClientName_EventType/ folder lives. Three reasonable options:

• One flat root. Projects/ contains every wedding, sorted by date. Simple, searchable, future-proof. Recommended for solo videographers under ~50 projects/year.
• By year. Projects/2026/, Projects/2027/. Good if you’re worried about Drive list rendering getting slow (it handles ~1000 folders per level fine, so this is only an issue past year 4–5).
• By season. Projects/2026-Spring/, Projects/2026-Summer/. Don’t recommend it. Too many judgment calls about which season a March wedding goes in.

Option 1 is the right default. Don’t over-organise. Your date-prefixed folder names are the organisation.

Step 3: The problem with doing this by hand

If you stopped here, you’d already have a cleaner setup than most wedding videographers. The naming convention and the template are the core.

But there’s still friction. You have to remember to copy the template. You have to remember to rename it with the right date and names. You have to copy the Drive link and paste it into your project tracker. You have to paste it in the right field (RAW folder link, not Delivery link, not the shared client link). And if you shoot photo+video and use two tools, you paste it twice.

Each step is a 10-second micro-task, and each one is a place where you’ll forget or do it inconsistently. It’s not unusual to find five different Drive link formats inside one studio’s project tracker because every videographer pasted a different URL (edit mode vs view mode vs share mode).

Step 4: Automate it from your project tool

The fix is to automate folder creation from the moment you create the project. This is where a modern studio OS earns its keep.

The flow you want:

1. You click “New Project” in your studio tool.
2. You type Anna & Lars as client, 2026-08-15 as date, Wedding as event type.
3. You click Create.
4. Behind the scenes, the tool calls Google Drive’s (or Dropbox’s) API with your template + naming pattern and creates the project root folder with all the subfolders you defined inside it.
5. The link to that project folder is attached to the project card, one click away from any other project field.

Total time: 0 seconds. Total clicks: 0. You didn’t open Drive.

Three weeks later when you’re card-offloading at 11pm, you don’t need to remember which folder Anna and Lars got — you open the project card, click the RAW link, you’re there.

How FlowShot does it

In FlowShot this is a one-time setup on the Integrations page:

1. Connect your Google Drive or Dropbox account via OAuth.
2. Pick the template folder (the one you created in Step 1).
3. Pick the parent folder where new projects should live (Projects/ from the setup above).
4. Configure the naming pattern by picking which fields go into the folder name (event date, client name, event type, project type, venue, package, project name), the separator between them, and the date format. Compose the order yourself.

Every new project then automatically:

• Creates the project folder with your naming pattern
• Clones the subfolders from your template
• Attaches the project folder URL to the project card so editors reach it in one click from anywhere on the project

Per-project hand-overrides aren’t a feature — the template runs at project-create time. If you need to point at an existing folder for an unusual project, you’d do that manually via the project’s settings.

The RAW footage link trap

One mistake I see constantly: videographers paste the shared link into the project card. That link works for clients but doesn’t work for teammates editing in Premiere, because Premiere expects a file system path, not a web URL.

What you want is the direct Drive link (or the Dropbox “Stream” link for team members), which opens the folder in the Drive desktop app if installed, or the web UI if not. The two links look almost identical and behave differently — test it once and you’ll know.

When automation handles this for you, you get the right format every time.

Google Drive vs Dropbox vs the rest

Quick take for wedding videography specifically:

• Google Drive — cheapest for large wedding-video storage (Workspace plan gives you 2TB for $12/mo/user). Best UI for clients downloading finals. Slight proxy-streaming lag in Premiere.
• Dropbox — best desktop sync (Smart Sync), best for teams with 2+ editors. Pricier: $20/mo/user for 3TB. Preferred if your editing workflow is Mac-centric and you want offline access.
• Frame.io / Adobe Creative Cloud storage — great for review, not great for archive. Don’t use as primary storage.
• Backblaze B2 / Wasabi — great for long-term archive (cents per GB), not for active project folders.

The automation pattern works with either Drive or Dropbox — the structure and naming convention are identical. Pick whichever you already pay for.

The before/after time math

• Before: 5 min/project × 30 projects/year = 2.5 hrs/year on folder admin
• Plus: ~1 hr/year hunting for the wrong folder name
• Plus: 2 hrs/year cleaning up inconsistent naming for past clients who ask for raw files

Total pre-automation: ~5.5 hrs/year of pure overhead.

After automation: 0. The structure is applied automatically, the link is attached automatically, and five years later when that 2026 bride emails, you search anna-lars and get the folder instantly.

5.5 hrs isn’t a life-changing number on its own. But it’s 5.5 hrs of friction — the kind of work that happens at 11pm, when you’re tired, where mistakes cost you the next day. Removing friction at 11pm is worth more than the raw hours suggest.

The weekend setup checklist

If you start Friday evening, this is live by Sunday night:

• Friday evening: pick your naming convention, build the template folder with five subfolders, decide on your project root location.
• Saturday morning: migrate 3–5 recent past projects to the new naming convention (just rename them — don’t touch the files). Proves the pattern works.
• Saturday afternoon: connect Drive/Dropbox to your studio tool, point it at the template, point it at the project root, configure the naming pattern.
• Sunday: create a dummy project to verify. Delete it. Create your next real project and watch the folder appear.

Total: ~3 hours. Payoff: every project for the rest of your career.

---

If you want a project tool that handles folder creation, subfolder templating, and project-folder-link auto-attach out of the box — that’s part of FlowShot’s integrations module. Google Drive and Dropbox auto-folder creation is included on every paid plan, starting at Starter ($25/mo).