PLEASE NOTE: FTP in MediaSilo has been retired as of July 1st, 2021. Any current connections will cease uploading as of that date.
We strongly recommend that all customers set up new FTP connections using Shift FTP prior to July 1st. You do not need to be migrated to Shift in order to use Shift FTP, and any files uploaded via Shift FTP to MediaSilo-linked projects will synchronize back to MediaSilo for users to annotate, share, download, or perform any other actions as usual.
You can use 3rd party FTP software clients (Cyberduck, Filezilla, Transmit, Vantage etc) to upload to MediaSilo. We also support FTPS using TLS.
As with all FTP transfers, you are limited only by your local connection and the limitations inherent in the FTP protocol. Speed is entirely dependent on available bandwidth and latency from your geographic location, and can, therefore, vary greatly. This is out of our control and can vary from as little as 200 kbps or less to as high as 6 Mbps.
For FTP uploads, MediaSilo supports one upload connection at a time to ensure ingest into our system. Each FTP clients handles concurrent upload settings differently, so please contact support if you have questions.
With a stable connection, you should be able to get 4GB or larger files transported. We cannot accept folders containing assets — only the assets themselves, but you can select multiple files at once or use a "select all" key-command to upload a group of files at once.
Our FTP is a catch server and the "Remote" directory reflects the root project folders within MediaSilo that you have access to. Your files only stay on the catch server for a few minutes before being copied off into our system. DO NOT modify or create folders from the 3rd party side, as they will not exist in MediaSilo (nor any assets you've uploaded into them). If you are concerned if a file is successful, simply go to your MediaSilo account to check.
Basic File Specifications
- Don't use special characters (such as quotes, ampersands, etc.) in the filename.
- Make sure the file has a valid extension, such as .mov, .avi, etc.
- Don't try to upload folders (unless archived as a .zip).
- For more detailed file specifications, click here.
- We suggest for larger files that your client be in Active mode
- Queue uploads for maximum performance, only allow 1 connection at a time, this is faster than trying to upload multiple files simultaneously
- Make sure Ports 40,000 to 50,000 are unblocked for transport verification
- If you are using an FTP proxy to get through a firewall make sure it is configured correctly
- File names should have no spaces or apostrophes
- Never upload to the root directory, always upload to a specific project.
- Check to make sure your file type is an accepted format. Files not listed will be deleted from the FTP and will not go into MediaSilo. For example, we will not ingest executable files (.exe). Any file placed in a .zip can be uploaded.
- Be sure your Connection Timeout is disabled
- Host: ingest.mediasilo.com
- Username: Combine your username and hostname as one word, example:
- Username: Bob
- Hostname: mycompany.mediasilo.com
- FTP user: bobmycompany
- Password: Remains the same password as your MediaSilo log in.
- Port: 21
In Vantage, the Deploy action is controlled by a service in Vantage called Transport. And the Session Limits for each service in the Vantage domain can be set in the Vantage Management Console under Services.
Before the Session Limits can be edited, the service must be placed into Maintenance Mode. To limit the number of FTP sessions to 1 (Deploy actions configured for FTP delivery), the Session Limit should be lowered to 1.
If you have multiple servers in their Vantage Array, you will need to remove the Transport service on all other machines from the Vantage Domain. This can also be done via the Services section of the Vantage Management Console.
Filezilla Sample Connection