Uploading a video

Turn a recording you already have into a ramble.

You can turn a recording you already have into a ramble: a phone screen capture, a Loom, anything with you talking over it. An upload goes through the same reading as a live recording and ends at the same kind of link.

Where it is

The upload page is at ramble.sh/upload. The home page doesn't link to it on purpose. Recording is the main way to use Ramble, and an upload box next to the record button invites screen captures with nobody talking, which have nothing to say.

Who can upload

On ramble.sh you need to be signed in. If you aren't, the page sends you to sign in and then back to the upload. The free rambles that browsers get for recording don't cover uploads. See Account.

The phone app can upload too, but it is in private testing only.

What makes a good upload

  • There has to be narration. Ramble works from what you say. A video with no audio track is refused with the message "That video has no audio track". A video where nobody describes a problem has no findings.
  • Talk the way you would in a live ramble. Say what you do, what you expected and what happened.
  • Up to ten minutes. The length of the audio is the length of the ramble. A longer file is refused, and the message names the limit.
  • Up to 250 MB by default. The page shows the limit it is using, and tells you right away if your file is over it ("That file is 312 MB. The limit is 250 MB."). If a file won't read, export it again, for example as an MP4, and upload that.
  • A screen you can see. Some screens are recorded black on purpose, such as private browser tabs, banking apps and protected video. Findings from black stretches rest on your words alone and have no screenshot. See Troubleshooting.

Pressing the upload button means you agree to the Terms and the Privacy Policy.

What happens next

  1. The file uploads. Keep the page open until the progress bar finishes. If the upload doesn't arrive in one piece, nothing is kept and you can try again.
  2. Ramble reads it. The results page shows the step it is on: decoding, transcribing, then distilling findings. Reading an upload usually takes one to five minutes. You can close the page and come back to the link later.
  3. The findings appear on the same page, the same as for a live recording. See Your ramble.

Ramble sends the audio to a speech-to-text service for the transcript, and the video to the AI model that finds the findings. Ramble keeps your original file on the server so a failed reading can be retried, and deletes it with the ramble. It is never served through a ramble's link.

An upload can't answer a record request from your agent. Record those live.

If Ramble restarts while you upload

Ramble restarts when it is updated. What happens depends on how far your upload got:

  • The whole file had arrived. Ramble picks the upload up again by itself and reads it. You don't have to do anything, and the page keeps showing the ramble as being read.
  • Only part of the file had arrived. The ramble is marked failed, with a message that the upload didn't finish arriving. The phone app sends the file again by itself. From a browser, upload the video again.
  • Ramble couldn't pick it up by itself. The page says the video is safe on the server and shows Retry. Press it.

A service Ramble depends on can also fail while reading an upload. The page then says so and shows Retry, which reads the saved video again.