Skip to content
Documentation

RTC recordings

Make sure recording is included in the workspace’s RTC plan. Inform participants and obtain any consent required for your use case. Your application must provide its own visible recording indicator and consent experience.

Participants should already be publishing the tracks you want to capture when the recording starts. The current release captures those selected tracks; it does not automatically add new participants or tracks that start publishing later. A silent or empty session is not a useful recording test.

  1. Join an open room and publish the intended audio/video.
  2. Select Start recording in the call controls.
  3. Open Recordings to inspect the job. Use Refresh to reload status.
  4. Select Stop on the active recording when finished, or end the room.
  5. Wait until the job is ready, then use its track download buttons.

Leaving your own call is not the same as explicitly stopping the recording or ending the room. For integrations, use the recording API. To turn a recording’s audio into text, see transcription.

StatusMeaning
queuedThe start request was accepted
recordingCapture is active or starting
processingCapture ended and output is being finalized
readyTrack files are available for authorized download
failedCapture or processing did not complete successfully

Only one queued, recording, or processing job may exist for a room at a time. Do not treat a 202 start response or a successful stop request as completion. Use the recordings list or the signed recording.ready event.

The output is individual MKV tracks, not a single composed meeting video. Each track identifies its media kind, source, participant, size, and track ID. Playback support varies; use a compatible player or your own media-processing workflow when you need another format or a combined layout.

The current recording release limits capture to one hour and approximately 1 GiB per track. It does not automatically capture late-joining tracks.

Delete a recording with DELETE /v1/recordings/{recordingId}: it is sent to Trash, auto-deleted after 30 days, and you can restore it until then with POST /v1/recordings/{recordingId}/restore. A recording in Trash still counts against your recording storage. To remove it for good sooner, delete it from Trash with POST /v1/recordings/{recordingId}/purge: RTC answers 202 (status: "deleting"), the deletion finishes shortly and recording.purged follows.

CHAMPREP keeps recordings for your plan’s retention period; when it ends, the recording is sent to Trash the same way. On plans that include it, RTC also copies each finished recording to your own bucket, and those copies are never deleted by RTC. See delete a recording and bring your own storage.

Your backend uses a key with recordings:read to request a selected track’s download URL. The API checks the recording and key’s project access. It then returns an RTC-domain URL that expires after five minutes.

Anyone possessing this temporary URL may use it while it remains valid. It does not require a separate browser login. Deliver it only to a user your application has authorized, or stream the file through your own authenticated backend if you need every download tied to your application’s session.

  • Do not put download URLs in public pages, analytics, logs, or shared messages.
  • Fetch the URL exactly as returned rather than constructing an object path.
  • If it expires, request a new one after checking access again.
  • Revoking the issuing API key invalidates its outstanding download grants.
  • Downloading an authorized copy does not make that saved copy revocable.

Use webhooks to notify your application that processing is complete without repeatedly requesting download grants.