https://livekit.io logo
Join Slack
Powered by
for livekit recording, where does the recording fi...
# ask-ai
v
for livekit recording, where does the recording file go to and how i can view it
t
Thanks for reaching out, Justin. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I’m responding to your question about where LiveKit recording files go and how you can view them. Short answer • Recordings go to the storage destination you configure when starting egress (for example, an S3/GCS bucket). LiveKit does not keep recordings by default. • When an egress finishes you’ll receive an 
egress_ended
webhook that contains the final file location (or backup info if an upload failed). You can use that URL to download or view the file. Where recordings are stored • Cloud storage upload: If you configured egress with cloud storage (S3, GCS, etc.), the recording is uploaded directly to that bucket. Example S3 configuration when starting egress:
Copy code
Output: &livekit.EncodedFileOutput_S3{
  S3: &livekit.S3Upload{
    AccessKey: "key",
    Secret:    "secret",
    Bucket:    "bucket",
    Region:    "bucket region",
  },
}
• Backup storage: If the cloud upload fails and backup egress is enabled, LiveKit saves the recording to a backup storage bucket for up to 7 days. The backup location is included in the 
egress_ended
webhook. How to view/download recordings 1. Check the 
egress_ended
webhook event for the recording URL or backup manifest. The webhook payload contains the file location (and 
backupStorageUsed: true
if backup was used). 2. If backup was used, fetch the 
manifestLocation
in the webhook. The manifest is a JSON listing files and their temporary download URLs. 3. Use the provided URL(s) to download or stream the file from your configured bucket or from the backup URL. Important notes • LiveKit doesn’t store recordings by default; files go to your configured destination. • Backup recording URLs are temporary (valid for 7 days). • Backup recordings are visible in the LiveKit Cloud dashboard under egress session details (the Destinations section) where you can copy the file URL. If you’d like, I can help with next steps — pick one: • Walkthrough how to set up S3/GCS uploads for egress (show the config you need). • Show an example of the 
egress_ended
webhook payload and where to find the file URL. • Help check a specific egress session if you can share the egress ID or webhook payload (or tell me how you started the recording). Sources: Universal Egress | Backup Egress Recordings | Security | LiveKit
v
can it go to azure storage container
t
Thanks — I’m responding to your question about whether LiveKit recordings can be saved to an Azure Storage container. Short answer • Azure Blob Storage / Azure Storage containers are not explicitly listed as a supported egress destination. LiveKit’s egress supports uploading to cloud storage buckets (S3/GCS examples are shown) and other destinations like RTMP and WebSocket, but Azure Storage is not mentioned. What you can do next • If you need recordings in Azure, two practical options: ◦ Upload from your own backend: Configure egress to write to an S3/GCS bucket (or use backup egress), then have a backend job copy the files from that bucket to your Azure container. ◦ Use a transfer service or gateway: Use an S3-compatible gateway or tool that writes to Azure Blob Storage (many third‑party tools provide S3-to-Azure bridging). If you’d like, I can: • Walk through how to configure S3/GCS output for egress. • Show how to read the 
egress_ended
webhook and use the manifest URL to download backup files for transfer. • Help outline a small script or lambda function to move files from S3 to Azure Blob Storage. Which option would you prefer or do you want to share how you currently start egress (egress config or egress ID) so I can give a more concrete example? Sources: Universal Egress | Backup Egress Recordings | Azure OpenAI TTS plugin guide | LiveKit Documentation
6 Views
Open in Slack
PreviousNext
Powered by