Cloud Storage & File Transfer
Your cloud storage is already full of video. Start publishing from it.
Connect VideoNest to wherever your finished video lives — S3, Google Drive, Dropbox, or any FTP server. VideoNest syncs your content, you associate metadata, and publishing automations handle the rest.
Works with
Supported storage
Every major bucket, drive, and server.
VideoNest connects to all major cloud storage platforms. Choose the ones your production team already uses — no migration required.
Google Drive
Link a folder and VideoNest imports on a schedule or on demand. The natural handoff after post-production for most teams.
View integration →
Amazon S3
Point VideoNest at a bucket. It ingests directly, picks up sidecar metadata files, and stays in sync as new files land.
View integration →
Dropbox
Connect a folder and VideoNest monitors it. Drop a file in and it's ingested automatically — no extra steps needed.
View integration →
OneDrive
Sync video from Microsoft OneDrive into VideoNest. Works across personal and business accounts via OAuth.
View integration →
Box
Common in enterprise media workflows. VideoNest monitors a Box folder and ingests new files as they arrive.
View integration →
Backblaze B2
Cost-effective S3-compatible object storage. VideoNest connects via the B2 native API or S3-compatible endpoint.
View integration →
Wasabi
S3-compatible hot cloud storage. VideoNest ingests from Wasabi buckets directly — same setup as Amazon S3.
View integration →
FTP / SFTP
Connect to any FTP or SFTP server. Common in broadcast workflows where encoders or NLEs deliver files directly.
View integration →How it works
Connect once. Publish from anywhere.
VideoNest sits on top of your existing storage. You don't move files — you give VideoNest a window into them.
Connect your storage
Authenticate with OAuth, drop in API credentials, or paste FTP details. VideoNest stores the connection securely and monitors for new files.
VideoNest ingests and tags
New files are detected automatically. VideoNest pulls them in, extracts or maps metadata from sidecar files, and adds them to your library — ready to publish.
Publishing automations take over
Based on the tags and rules you've configured, VideoNest distributes to your CTV channels, podcast feeds, website, and news syndication partners automatically.
Your storage stays in place. VideoNest doesn't migrate your files or change your existing workflow. It reads from your storage, ingests what it needs, and handles everything after that. Your bucket, drive, or server is untouched.
Common workflows
Who uses cloud storage sync.
NLE finishes render → FTP delivers → VideoNest publishes
Editors export to a shared FTP server. VideoNest monitors it, picks up the file, and kicks off publishing to every configured destination automatically.
Upload to Drive → VideoNest syncs → live everywhere
Teams drop finished content into a shared Google Drive folder. VideoNest ingests on a schedule, applies standard metadata, and routes to all active channels.
Backfill an existing S3 archive into VideoNest
Thousands of archived videos in an S3 bucket can be ingested in bulk. VideoNest maps metadata from sidecar files or applies defaults, making the whole archive publishable.
Box or OneDrive as the editorial handoff point
For organisations already on Microsoft 365 or Box, VideoNest connects directly. No new tools for the editorial team — VideoNest handles the publishing layer.
Related features
After you've synced
Sync & Import →
Full detail on how VideoNest monitors, ingests, and processes files from connected sources.
Bulk Upload →
Uploading directly from local storage or a one-time batch? Bulk upload handles files that aren't in a cloud source.
Distribution →
Once video is in VideoNest, publishing automations distribute to CTV, podcast, news, and social automatically.