Exporting video
Export clips and collections for download or editing.
On this page
Exporting downloads your clips as video files — individual MP4s, a reel, or a zip bundle of both — so you can use them outside cliply: in a presentation, a messaging app, a broadcast package, or a personal archive. Every entry point opens the same export panel; only what's pre-filled changes.
There are two ways it can run. If the video lives in cliply's cloud, a server export does the work and emails you when it's ready. If you're working from a video file on your own computer, your browser cuts it directly — nothing is uploaded, no credits are spent, and you get the files as fast as your machine can write them.
What you can export
| Export type | What you get |
|---|---|
| Individual clips | One MP4 file per clip, trimmed to in/out points |
| Reel per tag | One reel per tag per source video, clips in start-time order |
| Combined reel | One reel per source video with every selected clip, in start-time order |
| Bundle as .zip | A single archive containing everything you exported |
Reels render per source video — if your selection spans more than one video (including a collection built from several videos), you get one reel per video rather than a single cross-video reel, and clips always play in start-time order. A collection's curated clip order isn't honored yet.
With a reel selected you can also turn on Reel cover to open each reel with a 3-second branded title card — your title, an optional subtitle, and the brand picked in the watermark selector (club logo, custom image or text, or the cliply mark). A live preview shows the card as you type, and per-tag reels stamp their tag name on the card's corner chip.
You can also turn on Frame-accurate cuts to re-encode each clip instead of a fast stream copy — useful if you need a consistent format/bitrate across clips pulled from different source videos. Exporting exactly one clip skips the individual/reel/zip choices entirely: one clip is always one file, so the panel collapses to just this toggle.
How to export
Open the export panel
There are three entry points:
- Workbench: click the scissors icon on a clip row to export that clip alone, or select multiple clips and use Export in the bulk bar. To export the whole video, click the scissors chip in the toolbar or Export clips in the ⋯ menu — if a deck is active, its tags come pre-selected.
- Collections: open a collection's ⋯ menu and choose Export clips, or click the export button in the collection viewer header.
- Exports page (
/dashboard/organization/exports): click Export, then pick a video or collection from the drawer. Search or filter by project to find it — only sources with exportable clips are listed.
Choose what to export
For a whole video or project, pick the tags to include. For a collection, every exportable clip is included automatically — embedded clips (YouTube/Vimeo) are skipped, and a summary shows how many of the collection's clips can be exported. Exporting a single clip skips this step.
Set the output
Turn on Individual clips for one file per clip, and pick a Reel option (none, Reel per tag, or Combined reel) for a compiled video too. Add Bundle as .zip to get everything in one archive, and Frame-accurate cuts to re-encode each cut. For a single clip, this step is just the Frame-accurate cuts toggle.
Start the export
The panel names the total before you press anything — "25 credits for 2.5 min of footage" — and the button repeats it. A selection spanning several matches becomes one job per match, so the total is the sum of those jobs, not the footage times the rate.
Click Export. The credits are taken then, a background job is queued, and you'll be notified when it's ready to download. On the desktop app, export runs locally using FFmpeg instead of queuing a server job.
If the panel shows Cut on this device instead, the video file is on your computer and your browser will do the work — see below.
Download
The email and the bell notice both open the Exports page (/dashboard/organization/exports) with that job already expanded. You can also get there yourself and expand any finished job's row to see the file count, total size, the options used, and the expiry date above the download list.
Cutting on this device
When the video you're working from is a file on your own computer — one you opened from disk, or a recording you made in cliply and never uploaded — the export panel offers Cut on this device instead of queuing a server job. Your browser reads the file, cuts the clips and hands you the results. Nothing leaves your machine.
It offers the same choices as a server export: individual clips, a reel per tag or one combined reel, everything bundled as a .zip, and the tag badge, coach notes, club watermark and telestrations burned into the picture. Collections work too, including ones built from several matches.
Pick what you want, then click Cut & download
You'll be asked where to put the files first — where to save the .zip, or which folder to write them into if you turn the bundle off. Choose the destination before the cut starts; the browser only allows that prompt right after your click.
Leave the tab open
The cut runs in this tab, not on a server, so closing it stops the export. There's no job to come back to and nothing appears on the Exports page — these files go straight to your downloads.
A few things behave differently from a server export:
- Cuts start at the nearest earlier keyframe unless you turn on Frame-accurate cuts, which re-encodes and is slower. Any burned-in content turns it on automatically.
- A reel spanning several matches is rebuilt at one frame size so it plays as a single video. That means re-encoding every clip in it — expect minutes rather than seconds. A reel whose clips share one video stays fast.
- Some files can't be read. Formats from professional cameras (ProRes, DNxHD) have no browser support. The panel checks your files as it opens and names any it can't read, leaving their clips out — the desktop app handles any format.
- Older browsers can't do everything. Frame-accurate cuts and burned-in content need video encoding, which Chrome, Edge and Safari 16.4+ have. Elsewhere you still get keyframe cuts, and the panel says so.
Plan requirements
| Export feature | Plan required |
|---|---|
| Cut on this device | Solo and up |
| Server clip export (video files) | Club or Enterprise |
| Server reel compilation | Club or Enterprise |
Cutting on your own device is available from Solo up. Server-side export and reel compilation require Club or Enterprise — and if the video is on your computer, the panel offers the local cut alongside the upgrade prompt rather than only the prompt. On the desktop app, export runs locally and has no plan requirement — see Working offline for details.
The export worker runs from a datacenter IP address that YouTube and Vimeo block, so clips sourced from either service can never be exported server-side. If you're playing your own copy of the match on top of that source, your browser can still cut it — the file is right there, and the worker is not the one doing the work. Without a local copy, use the desktop app, which runs FFmpeg locally on your own network. A generic media-URL source only exports server-side if the file is actually reachable by the worker — in practice, that currently means archive.org links.
If you never uploaded the video, there's nothing in the cloud for the worker to cut. The panel says so and offers the local cut instead — or upload the video first if you want the server to handle it.
Exporting does not use any AI credits, regardless of plan.
When an export fails
A job that ends as Failed, Canceled or Expired keeps its row. Expand a failed one to read what went wrong in terms you can act on — a source that was deleted, a video that only ever existed on someone's laptop, a file we couldn't read — and use Run again to queue the same clips with the same options. Canceled and expired jobs offer Run again too; on an expired one it re-renders the files the retention sweep deleted.
Credits are returned automatically when a job fails for good, and Run again charges the new job like any other export. Only the person who asked for the export, or an organization owner or admin, can run it again.
A failure emails the requester and posts a bell notice, the same as a success does.
Cancel stops a queued export outright, and a running one as soon as it finishes the clip it is on — either way the credits come back and no files are produced. If the export had already finished, the app says so rather than pretending it stopped.
Retention and limits
Exported files are automatically deleted 30 days after completion — download them before then, or re-export later if you need them again. You can also delete a finished export manually at any time (cancel it first if it's still running).
Download links are signed and expire after 1 hour, but they refresh automatically each time you reopen the export panel or the Exports page — the underlying file isn't gone, only the link needs refreshing.
Each organization can have at most 50 active export jobs running at once. This is an abuse guard, not a plan limit — it resets as jobs finish.
File naming
Local cuts use the same names, so a clip exported either way lands as the same file.
| Output | Naming pattern |
|---|---|
| Individual clip | {clip-name-or-tag}-{index}.mp4 |
| Per-tag reel | {tag-label}-reel.mp4 |
| Combined reel | combined-reel.mp4 |
| Zip bundle | Archive containing clips/ and reels/ folders |
Names are lowercased and stripped to letters, digits and dashes. Accents and ñ are folded rather than dropped, so "Córner corto" lands as corner-corto.mp4 and "Ñandú" as nandu.mp4.
Selecting tags rather than an ad-hoc clip list makes per-tag reels straightforward — each tag becomes its own reel automatically, with clips in start-time order.