Share a Swipe File With Your Team: 4 Setups That Work

To share a swipe file with your team, put the actual ad files in one shared place, keep one searchable index of them (Notion, Google Sheets, or a board tool like Foreplay), and give one person ownership of a weekly review. The storage choice matters less than the rules: consistent file names, tags by hook, angle and format, and a habit of pruning.

I've run team swipe files for agencies and in-house teams. Here's what held up and what quietly rotted.

What makes a team swipe file different from a personal one?

A personal swipe file only has to make sense to you. You remember why you saved an ad, so a messy folder still works.

A team swipe file has to make sense to someone who wasn't there. A designer opening it on a Tuesday needs to find "UGC ads leading with a price objection" in under a minute, without asking you.

If you're new to the idea, start with what a swipe file is. This post is about the sharing part, which is where most swipe files break.

How do you share a swipe file with your team?

There are four setups I've seen work. Most teams end up combining two of them.

Prices as verified August 2026. Here's each one in more detail.

Option 1: A shared drive folder with a naming convention

This is the cheapest team swipe file and it works better than people expect. One shared folder in Google Drive, Dropbox or similar, with a strict structure.

I use one folder per competitor, then files named like this:

advertiser_YYYY-MM-DD_format_hook.mp4

So a file reads as brandname_2026-09-12_ugc_price-objection.mp4. The date is the day you saved it. Anyone can sort, search and understand the file without opening it.

The weakness is that folders only sort one way. You can browse by brand, but not by "every ad using a before-and-after angle" across brands. That's what an index fixes.

Option 2: A Notion or Google Sheets index

Keep the files in the drive, and keep a searchable index in Notion or Sheets. One row per ad, with a link to the file.

The columns I use:

• Advertiser
• Date saved and "Started running on" date from the Ad Library
• Format (UGC, static, carousel, demo)
• Hook (the first line or first seconds, written out)
• Angle (the core reason to buy)
• Offer
• Link to the file and link to the original ad
• Saved by

Now a designer can filter to "carousel + comparison angle" across every brand in seconds. We walk through the full database setup in building a swipe file in Notion.

Sheets is fine if your team already lives there. Notion is nicer for previews and linked pages. Either works as long as the index is the single place people search.

Option 3: Foreplay boards

Foreplay starts from $59, or $49 on annual billing. It's built around saving ads into boards and sharing them with a team, which makes it a common ad swipe file for agencies.

The appeal is that saving and sharing happen in one step, so you skip the manual drive-plus-index work. The trade-off is a monthly cost and a dependency on one tool. If you ever leave, plan how you'll export what you saved.

Option 4: An exported ZIP with a swipe board and CSV

The Meta Ad Library has no download button and no permanent saving. When an advertiser pauses an ad, it vanishes from the library, and so does your reference.

For grabbing a competitor's whole library at once, I use our free extension, the Meta Ad Library downloader. Its bulk mode collects every running ad from a search into one ZIP, and each export includes an index.html swipe board (search by hook, CTA or advertiser, play the ads, copy the text) plus a CSV of every ad. Files are named by advertiser and date.

That ZIP drops straight into a shared drive, and the CSV pastes into Sheets as a starting index. It's a snapshot rather than a live board, so treat it as a monthly capture, not your whole system. The manual alternatives are in our guide to downloading Facebook Ad Library videos.

How should a shared swipe file be organized?

Organize by the questions your team actually asks when briefing. In my experience those are about hook, angle and format, far more than about brand.

1. 1
   SaveDownload the ad before it gets paused.
2. 2
   Nameadvertiser_date_format_hook, every time.
3. 3
   TagHook, angle, format, offer in the index.
4. 4
   ReviewWeekly, owner prunes and flags winners.
5. 5
   BriefEvery review ends with one brief.

A few tagging rules that saved me grief:

Use a fixed tag list. Decide your angle tags up front: price objection, before and after, comparison, founder story, social proof, problem-agitate. Free-typing tags leads to "social proof", "reviews" and "testimonials" all meaning the same thing.

Write the hook out in words. Don't just tag "strong hook". Type the actual first line. Search only works on words.

Record longevity. Note the "Started running on" date. An ad running for months is usually a winner, because advertisers keep paying only for what works. That one column separates proven ads from pretty ones.

For deeper structure ideas, see how to organize a swipe file.

Who should own the team swipe file?

One person. Not "the creative team", not "everyone". One named owner.

Shared files rot because everyone adds and nobody removes. The owner doesn't save every ad. Their job is to keep the tags consistent, merge duplicates, and run the review.

In an agency, I've had this rotate monthly between strategists. It works as long as the handover is explicit and the owner's name is written at the top of the index.

What does a weekly swipe file review look like?

Thirty minutes, same day each week, with whoever is briefing creative next.

1. The owner filters the index to ads added this week.
2. The team marks each one keep, cut, or needs tags.
3. Check older "keep" ads in the Meta Ad Library: still running, or paused?
4. Anything still running after many weeks gets flagged as a proven reference.
5. End with at least one brief written from the file.

That last step is the one teams skip. A swipe file with no briefs coming out of it is just storage.

How do you keep a shared swipe file from rotting?

Rot looks the same everywhere: hundreds of ads, half untagged, files called "final_v2.mp4", and nobody sure which ones mattered.

What prevents it:

• Cap intake. Each person saves their best few ads per week, not everything they scrolled past.
• Prune on a schedule. Once a quarter, archive anything nobody has used in a brief.
• Keep one source of truth. If files live in the drive and the index lives in Notion, never let a second copy start in someone's desktop folder.
• Fix names on save. Renaming later never happens.

Our broader take on what belongs in the file is in the Facebook ads swipe file guide.

FAQ

How do you share an ad swipe file with your team?

Keep the ad files in one shared folder with a strict naming convention, and maintain one searchable index in Notion, Google Sheets or a board tool like Foreplay. Assign one owner who runs a short weekly review.

What is the best tool for a team swipe file?

For small teams, a shared drive plus a Notion or Sheets index is free and works well. Agencies that want saving and sharing in one place often use Foreplay, which starts from $59 or $49 on annual billing.

How should a team swipe file be organized?

Organize by hook, angle and format rather than only by brand, since those are the questions people ask when briefing. Use a fixed tag list and record the date each ad started running.

How do you stop a swipe file from getting messy?

Give it one named owner, cap how many ads each person adds per week, and prune on a schedule. Name files correctly when you save them, because nobody renames them later.

Can you share a swipe file for free?

Yes. A shared Google Drive or Dropbox folder with a Notion or Google Sheets index costs nothing. Downloading ads from the free Meta Ad Library keeps references after advertisers pause them.