Upload a recording and confirm it is playable

Prepare the original and internet

1
Stop recording safely, keep the camera powered and connect the App to it. Open the on-camera library and check the correct file, duration and team.
2
Configure camera Wi-Fi or, on a supported model, 4G. Run the camera's internet check; the phone having internet is not enough.
3
If the check cannot be completed, retry when the network is stable. Do not interpret a temporary check failure as a zero balance, a missing SIM or a lost video.

1
Select the recording and start upload once. Check that the task changes from waiting to uploading and that progress advances. Also check the upload percentage, transferred data size and estimated time remaining to see whether the task is progressing. The time estimate changes with actual network speed.
2
Keep the camera powered with a stable upstream connection. Larger recordings and higher bitrates usually take longer; signal strength alone does not predict upload speed.
3
If paused or failed, restore camera internet first, then use Continue or Retry only if offered for that task. If only Upload again is available, keep the original and follow that option rather than deleting the file.
4
For a task confirmed paused before a restart, reconnect, find the original task and resume it first. Do not upload the same file again.

After upload finishes, open the correct team's cloud library in the App or Hub. Processing is a separate stage; do not create duplicate uploads while processing is underway.
Only a successful playback check confirms the result is ready to watch. Check the expected duration and a few moments before relying on the cloud copy.
If another member can see the recording but you cannot, check account, team and permissions first. For persistent failure, send the recording name/time, current state, network type and sanitized screenshot to Ballr Support. Keep the camera original until the issue is resolved.

Complete

If your screen differs from this guide, check the camera model, App or firmware version, account role and organization service status.

Did this guide solve the issue?Send feedback