Upload Time vs Video Processing Time: What Each Status Means

The current Save Replay interface uses one Uploading label for two consecutive phases. First, a browser worker prepares the chosen start-to-end range as a clip. The prepared file is then transferred to storage. The progress display combines that work into one user-facing stage.

Keep the tab open and the device awake throughout this stage because both preparation and transfer depend on the active browser session. Closing the page, locking a mobile device, losing the connection, or cancelling the job can prevent completion. The original source remains on the device, and the upload path sends the prepared selection.

Once the server confirms the prepared upload, the interface changes to Processing and reveals the share controls. At that point, the transfer has finished. Save Replay can continue preparing the clip for browser playback on the server while the sender copies the watch URL or leaves the page.

An early visitor can open that same URL while processing continues. The watch page reports that the clip is getting ready, then uses the same address when playback becomes available. The sender does not need to create a second link after the status changes.

Upload duration can include local preparation speed and the network transfer of the prepared bytes. Source codecs, clip length, device performance, browser support, output size, upstream bandwidth, connection changes, and retries can all affect that stage. A duration estimate cannot cover every combination reliably.

Processing duration begins after transfer and depends on the work required to produce playable output. Ready is the terminal success state shown after Save Replay detects that the clip can be watched. Treat preparation, transfer, and processing as separate intervals when diagnosing a delay; a fast network result does not predict how long every other stage will take.