FARMFix a video upload that fails or will not play
Find whether the problem is file selection, transfer, library saving, URL access, encoding or delivery to the phone, with specific checks for each stage.
“The video upload failed” can describe several different problems: the browser rejected a file, the transfer stopped, the library entry was not saved, a public URL could not be fetched, or the phone app could not decode the finished file. The remedy depends on the first stage that failed.
Start in Videos and check whether the intended asset already exists. A lost browser confirmation does not always mean the upload failed, and uploading again before checking can create duplicate library items.
Find the first failed stage
| Stage | Successful result | If it fails, investigate |
|---|---|---|
| Local source | File plays correctly on your computer | Export, incomplete file or source corruption |
| File selection | Correct file appears in the browser's queue | Supported type, size and selected file |
| Transfer | Upload completes | Local connection, expired session or server error |
| Library save | Asset appears in Videos | Save result, page refresh and duplicate check |
| Library playback | Preview plays with expected sound | Encoding, incomplete transfer or source access |
| Phone preparation | Publishing workflow can use the asset on its target phone | Phone connection, app readiness or transfer step |
| Social publication | Correct post exists on the account | Platform/task outcome rather than library upload |
If the failure is already at the last two stages, preserve the library asset and use publishing troubleshooting. Re-uploading a healthy source is unlikely to fix a phone login problem.
Check the original file first
Open the exact source you selected. Watch the beginning, a middle section and the end, and listen to its audio. Confirm its file size is plausible and that it is an exported video, not an editor project or a download that has not finished.
PhoneFarm accepts MP4, MOV, M4V and WebM in the uploader. A filename extension is not a conversion: changing .mov to .mp4 leaves the encoded contents unchanged. If a file was exported with unusual settings, return to the editing project and produce a standard compatible export for the intended platform.
Check the size limit currently displayed in Upload from your computer. If the source exceeds it, reduce the export size using appropriate resolution, duration or bitrate settings and review the new result. Avoid repeated blind compression that makes text or product details unreadable.
If the file never starts uploading
Confirm that the file appears in the selected list and that you have chosen Add to library. Selecting or dropping a file only queues it; it does not complete the upload.
Read the validation message before changing anything. A type or size rejection should be addressed in the file. A sign-in problem should be addressed in the PhoneFarm session. Neither requires a new cloud phone.
If you selected the wrong file, remove it from the queue and choose the correct export. When several files are queued, review each filename and size so an unsupported item is not hidden among valid ones.
If transfer stops partway through
Check whether your computer's connection was interrupted or the browser tab was closed. Note the visible error and whether any files were already saved. Reload the library and look for the intended title before retrying.
For a large batch, start by retrying one missing file. This distinguishes a batch-specific problem from a source that consistently fails. If one file fails every time while other files succeed, compare its size and export settings with a working file.
If many unrelated files fail in the same way, check the dashboard session and local connection. Record the error and time. A repeated storage or service error is useful to support; repeatedly generating differently named copies of the same video usually is not.
If a public video URL will not import
The Public video URL must be retrievable as video content. Check these common problems:
- It is a webpage URL. A page with an embedded player may return HTML rather than the video file.
- It requires a login. A link that works in your signed-in browser may fail for PhoneFarm.
- It expired. Temporary signed links have an access window; a stale link cannot be retrieved later.
- It requires an extra click or access request. A file-sharing page is not always a directly accessible media resource.
- It points to a different version. Confirm the actual video behind the link, not just its title.
Use a stable direct video link that is appropriate to share with the service, or upload the file from your computer. Do not publish private material to an unrestricted host solely to work around a URL import issue.
If the asset exists but its preview is broken
Compare the library preview with the local source. If both are broken, repair the export. If the local source plays but the browser preview does not, the encoding or remote source may be the issue.
A video container can hold different video and audio codecs. Two .mp4 files can therefore behave differently in a browser or on a phone. A standard re-export from your editor is a better diagnostic than renaming the extension.
If the image plays but sound is absent, check whether the original export contains the intended audio and whether playback is muted. If audio drifts out of sync, inspect the source timeline and export settings. Keep the failing original so you can compare it with the corrected version.
Give the corrected export a new version name and play its saved preview after uploading. Then select that new asset for future publishing. An already prepared job may still reference the older asset; uploading a correction does not automatically revise every existing selection.
Handle a partially successful batch
Suppose six files were selected, four were added and two failed. List the four saved items and retry only the other two after correcting their issue. This prevents identical assets from multiplying in the library.
If the result screen is unclear, compare filenames, titles and previews. Do not delete an uncertain item merely to make the list look clean while a task may still reference it. Resolve which asset belongs to the planned work first.
What to send to support
Include the file extension and size, whether the local file plays, whether the library entry exists, the visible error, time and whether other files upload successfully. For URL imports, explain whether the link is public, direct and time-limited without sharing private access tokens in a general message.
If the asset is confidential, start with the technical details and a redacted screenshot. Ask for the appropriate transfer route if support needs the original file. Do not include account credentials or proxy passwords; they are not needed to identify a video decoding problem.
After the fix, play the saved library preview and repeat the publishing step only if that step was also affected. The normal upload walkthrough describes the complete successful path.