Войти
Moving a 3 GB video from one host to another normally means downloading it to your laptop and then uploading it again, which doubles the time and eats your data plan. With remote upload the file travels directly between servers, which usually have connections far faster than a home line. You can close the browser and come back later while the job completes.
This is also the quickest way to consolidate a library scattered across several sites, to pull in a recording a colleague left in a shared folder, or to move your content over from another video host when you switch.
The importer recognises a long list of sources and chooses the right method for each. Direct links to MP4 and M3U8 files work too, as long as the address is publicly reachable. Private, password-protected or login-only links cannot be fetched.
The behaviour you can rely on.
Cloud drives, mainstream video sites and many video hosting services are recognised automatically.
Transfers use the server connection, so a slow home line is no longer the bottleneck.
See each job in a list with its progress, retry failures and clear finished ones.
The dashboard flags a source that is currently failing so you do not waste time retrying it.
Add links programmatically and poll job status from your own scripts or workflows.
Premium accounts get a higher remote upload limit for large batches.
These providers are listed as supported in the upload page. The list is maintained live and a provider may be switched off temporarily if it breaks, so the dashboard always has the current status.
| Источник | What works | Заметки |
|---|---|---|
| Google Drive | Public files | Share the file with Anyone with the link first |
| Dropbox | Public shared files | Use the shared link, not the folder view |
| MEGA | Public file links | Handled through a bundled helper |
| YouTube | Videos you have the right to import | Subject to the platform rules and anti-bot checks |
| Vimeo, Dailymotion, Rumble, VK | Public videos | Resolved through a generic extractor |
| Pixeldrain, Mixdrop, Streamtape | Public file and video links | Plain share links |
| OK.ru, Mp4upload, Voe, Filemoon, StreamWish | Public video links | Availability can change with the site |
| Direct MP4 and M3U8 links | Any publicly reachable address | No login or signed expiry |
Only import material you own or have permission to copy.
Most failures come from links that are not truly public. Test the link in a private window. If it asks you to sign in, accept cookies or solve a challenge, the server will not be able to fetch it either. Links with a short expiry, such as signed URLs, should be submitted straight away.
Very large files may take a while, and the source host may throttle long transfers. If a job fails, restart it once before assuming the link is bad.
Everything the dashboard does can be scripted. The documented endpoint takes your API key and the URL, with optional folder and new title parameters, and returns a file code you can poll for status. See the video hosting API page for working examples, and the full reference in the API documentation.
Moving hundreds of videos from another host works best in batches. Collect the links in a spreadsheet, submit a few dozen at a time, and watch the slot count so the queue never overflows. Check a sample of finished videos for playback and subtitles before you submit the next batch, and keep the old host untouched until you have verified everything.
Importing a video does not change who owns it. Keep a note of permission when you move third-party content, and expect takedown requests to apply to the copy on FileHost.net just as they would anywhere else.
Many people arrive here with files sitting in another service. These pages explain what changes when you move them.
Paste your first link into the Remote Upload box and watch the server do the heavy lifting.
