File Exporting
Once your files have been processed, we can save the results to storage owned by you. Many of our customers have signed up for an S3 bucket, others prefer us to upload to their FTP server.
Over the last few years, developers have been steadily moving away from self-hosted or local systems when it comes to storing their data, and instead opting for the cloud. One important reason to move to the cloud is better protection of your data, particularly in the event of a natural disaster. This, of course, does mean you will need to set up cross-regional replication, but the cloud makes this easy.
It's predicted that the cloud storage market will grow to $88.91 billion by 2022, marking an enormous annual growth rate of 23.7% yet to be fulfilled. Billions of people and a myriad of companies are opting for online storage, because it’s comfortable, convenient, secure, and economical.
Transloadit can help companies transition by integrating with all major cloud providers. You can even run multi-cloud setups where each encoding result is saved on say, both AWS and GCP. Transloadit is happy to export to whatever storage suits you best.
Robots
At Transloadit, we call our features Robots because you can link them together to create encoding pipelines unique to your use case.
-
/azure/store
exports encoding results to Microsoft Azure -
/backblaze/store
exports encoding results to Backblaze -
/cloudfiles/store
exports encoding results to Rackspace Cloud Files -
/digitalocean/store
exports encoding results to DigitalOcean Spaces -
/dropbox/store
exports encoding results to Dropbox -
/ftp/store
exports encoding results to your FTP servers. This Robot relies on password access. For more security, consider our /sftp/store Robot -
/google/store
exports encoding results to Google Storage -
/minio/store
exports encoding results to MinIO buckets -
/s3/store
exports encoding results to Amazon S3 -
/sftp/store
exports encoding results to your own SFTP server -
/swift/store
exports encoding results to Openstack Swift buckets -
/vimeo/store
exports encoding results to vimeo -
/wasabi/store
exports encoding results to Wasabi buckets -
/youtube/store
exports encoding results to YouTube
Live demos
See our features in action through live demos and code samples, right here on our website:
- Export a video to YouTube
- Use Google Cloud Storage to store your results from Transloadit
- Encode a video, extract 8 thumbnails and store everything in an S3 bucket
- Apply a watermark to an image and store everything over SFTP
- Save your results to Dropbox
- Store uploaded files with Digital Ocean Spaces
- Store uploaded files in a Microsoft Azure container
- Store uploaded files in a Rackspace Cloud Files container
- Store uploaded files in an Amazon S3 bucket
- Store all uploaded files on an FTP server
- Copy files from Amazon S3 to Backblaze
- Copy files from Amazon S3 to DigitalOcean Spaces
- Copy files from Amazon S3 to Dropbox
- Copy files from Amazon S3 to FTP servers
- Copy files from Amazon S3 to Google Storage
- Copy files from Amazon S3 to Openstack Swift
- Copy files from Amazon S3 to Rackspace Cloud Files
- Copy files from Amazon S3 to SFTP servers
- Copy files from Amazon S3 to Vimeo
- Copy files from Amazon S3 to Wasabi
- Copy files from Amazon S3 to YouTube
- Copy files from Azure to Amazon S3
- Copy files from Backblaze to Amazon S3
- Copy files from Dropbox to Amazon S3
- Copy files from FTP servers to Amazon S3
- Copy files from Google Storage to Amazon S3
- Copy files from Openstack/Swift to Amazon S3
- Copy files from SFTP servers to Amazon S3
- Copy files from Wasabi to Amazon S3
- Copy files from Amazon S3 to Azure
- Copy files from Amazon S3 to MinIO
- Copy files from DigitalOcean Spaces to Amazon S3
- Copy files from MinIO to Amazon S3
- Copy files from Rackspace Cloud Files to Amazon S3
- Copy files from Webservers to Amazon S3
Related blog posts
- Renaming Some Robots April 7, 2010
- Support for Rackspace Cloud Files November 11, 2010
- Fixing Amazon S3 Bugs May 16, 2011
- New /s3/store Parameter May 26, 2011
- Releasing Our SFTP Robot and a New Homepage August 21, 2011
- Adding Support for Storage on YouTube January 25, 2012
- Two Small Feature Updates February 11, 2012
- Releasing Our FTP Robot May 29, 2012
- Introducing Our New /sftp/import Robot October 30, 2012
- Introducing the new /s3/import Robot July 17, 2013
- To Everyone Using the /youtube/store Robot July 11, 2013
- S3 Changes February 5, 2015
- Post Mortem: S3 Saving Incident February 17, 2015
- Support for Windows Azure and Softlayer November 18, 2015
- Powering major brands: How Transloadit supports Shuttlerock’s mission July 8, 2016
- How we secured a spot in thoughtbot’s toolkit May 19, 2017
- Publishing without boundaries: Supporting the vision of Cambridge University Press January 16, 2018
- Re-loadit: the /dropbox/store Robot December 12, 2018
- Re-loadit: the /google/store Robot March 1, 2019
- The /digitalocean/store Robot December 9, 2019
- The /azure/store Robot January 7, 2020