Your post-production pipeline, organized
Every video team hits the same wall: files too big for email, versions too messy for Drive, sign-offs too slow for production. Clipsilo is the warehouse layer between your edit suite and every downstream destination — with the plumbing video teams actually need.
5 GB per file · Multipart upload · SHA-256 dedup · Real approval workflow
5 GB
Max per file
SHA-256
Dedup hash
Batch
Manifest API
S3
Your bucket
The bottlenecks every video team fights
If you've ever watched a render finish and felt dread about what comes next — you're in the right place.
Large file transfer bottlenecks
A 3.5 GB ProRes master uploaded on hotel wifi takes two hours and fails at 97%. WeTransfer expires in seven days. Frame.io chokes on 4K. Your entire pipeline is hostage to whichever upload is still running.
Version control chaos
episode_03_v7_client_notes_v2_FINAL.mov. The AE swears v7b is newer than v7 but the timestamp says otherwise. Three assistants each downloaded different versions. Somebody is going to post the wrong one.
Platform re-encoding
YouTube takes 16:9 1080p H.264. Shorts wants 9:16 vertical. LinkedIn caps at 5 minutes. TikTok wants a different aspect. You're exporting the same cut six ways and juggling six uploaders.
Waiting for approval sign-off
The director watched at 2am. Says "looks good but the bass on the drop is off." What about the color? What about the last cut? You need a sign-off you can actually ship against — not a text message at 2:17am.
The plumbing video teams need
Not a general-purpose DAM. Not a consumer uploader. A real post-production warehouse.
Multipart upload for large files
Files over 100 MB automatically switch to multipart. Each chunk is uploaded in parallel directly to your S3 bucket using pre-signed URLs — bypassing our servers entirely. A failed chunk retries; your 4 GB ProRes master uploads at the full pipe speed without blocking the next one.
- Direct-to-S3 uploads (no transit through our servers)
- Resumable — recover from network drops automatically
- Parallel chunk upload for max throughput
SHA-256 deduplication
Every asset is identified by its content hash, not its filename. Upload the same episode cut twice? Clipsilo detects it, skips the second upload, and links the existing content object. Your bucket stays small. Your API calls stay fast. Your bill stays sane.
- One hash, one object — no duplicate storage
- Stable asset addressing for downstream pipelines
- Re-upload is idempotent and fast
Batch manifests for episode sets
Describe an entire season of episodes — master, trailer, shorts, social edits, stills — in a single JSON manifest. Clipsilo ingests the batch, attaches consistent metadata, and fires a single webhook when everything lands. Perfect for end-of-shoot wraps and campaign rollouts.
- JSON-manifest batch uploads
- Atomic batch completion events
- Batch-level approval states
Format support
Supports MP4, MOV, WebM, AVI — AWS S3 limits apply.
Plus audio (MP3, WAV, FLAC) and image assets (JPG, PNG, WebP, GIF, SVG). Stills, masters, proxies, and deliverables — all warehoused in the same system, all addressable by the same API.
Video
MP4, MOV, WebM, AVI
Audio
MP3, WAV, FLAC
Image
JPG, PNG, WebP, SVG
Max size
5 GB / file
Features video teams rely on
Built for people who ship cuts, not marketing decks.
Multipart upload
5 GB files upload in parallel chunks direct to S3. Resumable, retriable, fast.
SHA-256 deduplication
Content-addressed storage. Upload the same render twice, pay for storage once.
Batch processing
One manifest, one API call, one webhook. Ingest an entire season atomically.
Platform-specific metadata
Store YouTube title, TikTok caption, LinkedIn description — per asset, per destination. Distribute with the right copy every time.
The post-production workflow
From edit suite to destination platform, with approval baked in.
Ingest from edit suite
Export from Premiere, Final Cut, DaVinci, or Avid. Drag into Clipsilo or push via the API.
Tag with platform specs
Attach per-platform titles, captions, hashtags, thumbnails. Metadata is stored with the asset.
Client approval
Send a preview link. Client approves, requests changes, or rejects. Sign-off is timestamped.
Distribute to platforms
Push to YouTube, TikTok, Instagram, LinkedIn, and anywhere else — with the right metadata per destination.
Questions video teams ask
The practical answers to what post supervisors want to know.
How does the 5 GB file limit work — can I raise it?
Single files cap at 5 GB — a practical limit that covers most 4K episode masters and 1-hour ProRes cuts. If you need larger, we support chunked multi-file asset sets where one logical asset spans multiple 5 GB parts. Contact us if you regularly deliver 8K RED raw masters and we'll talk through options.
Does Clipsilo transcode my videos?
No — by design. We store your files as-is in your S3 bucket. If you need platform-specific formats (9:16 shorts, 1:1 square cuts, 720p for LinkedIn), export them from your NLE and ingest each as a separate asset. This keeps Clipsilo fast, cheap, and out of the creative pipeline. If there's demand we may add optional transcoding later.
Can I integrate with Premiere, Final Cut, or DaVinci?
Not with a native plugin yet — but our REST API is designed for pipeline scripts. Many teams wire up a post-export hook in their NLE or a Python script on their render farm that pushes new renders into Clipsilo automatically. Watch-folder patterns are straightforward with our ingestion API.
Where are my files actually stored?
In your own S3, Cloudflare R2, or Backblaze B2 bucket. Clipsilo stores the metadata layer (titles, tags, approvals, version history, SHA-256 references) and generates pre-signed URLs on demand. You keep control of the bytes, retention policy, and storage bill. We never egress your files through our servers.
What happens during a client approval session?
The client gets a preview URL. They can watch or scrub the asset in-browser (we generate efficient web-friendly previews). They hit approve, reject, or request changes, optionally leaving comments. The asset's approval state updates instantly, fires a webhook, and is stamped with a UTC timestamp plus the client email and IP. Full audit trail, retained indefinitely.
Stop losing Friday afternoons to file chaos
Start your 7-day free trial. Upload your first ProRes master in under three minutes.
7-day free trial · No credit card · Cancel anytime