Manage storage locations
Storage locations are destinations where your cloud recordings are saved. You can manage these locations using the Video SDK account web portal or the Video SDK BYOS Storage APIs.
You must add at least one storage location to use BYOS. You can add multiple locations, but only one can be set as the default at any time. You may switch the default location whenever needed. Use the ellipsis (three dots) next to each storage location for additional options.
Delete a storage location
To delete a storage location:
- Click Manage Storage.
- Click the ellipsis next to the storage location you want to delete and choose Delete.
Things to consider when deleting
- If you have only one storage location, it is automatically set as the default and cannot be deleted. Add and assign a different default location before deleting it.
- As a best practice, clarify to customers that deleting a storage location also removes its associated access keys or IAM role authorization. If a cloud recording is currently being processed, Zoom may be unable to upload files because the permissions are no longer valid. To avoid incomplete uploads, delete storage locations during off-peak hours.
Manage cloud recordings
Use the cloud recording APIs to manage, play, and download BYOS recordings. The APIs provide complete and consistent control over BYOS recordings, while the Zoom web portal offers limited functionality for BYOS and may not reflect the full state of your storage bucket. Download the recording from the location in the external_storage_url value.
Manage BYOS recordings with APIs
Do not use the Recordings page to manage or view files hosted externally via BYOS. Use the cloud recording APIs or your S3 bucket directly.
Cloud recordings consist of two components:
- Metadata (thumbnail, title, recording details) stored in the Zoom web portal
- Recording files stored in your S3 bucket
BYOS recording file types
When BYOS is enabled, Zoom uploads the following file types to your S3 bucket depending on your recording settings.
- MP4 - Video file of the recording.
- M4A - Audio-only file of the recording.
- TIMELINE - Timestamped file of the recording in JSON format. To generate this file, enable the Add a timestamp to the recording setting in your recording settings. The time displays in the host's timezone from their Zoom profile.
- TRANSCRIPT - Transcription file of the recording in VTT format.
- SUMMARY - Summary file of the recording in JSON format.
- CHAT - TXT file containing in-session chat messages sent during the session.
Storage format
Zoom stores BYOS recording files in S3 in the following format:
Buckets/{bucketName}/cmr/byos/{YYYY}/{MM}/{DD}/{GUID}/cmr_byos/
Zoom web portal BYOS limitations
We do not recommend that you manage BYOS recordings directly in the Zoom web portal, as the portal displays and controls only the metadata stored in Zoom, not the actual files stored in your S3 bucket.
For example, when you click the ellipsis next to a BYOS recording and choose Delete, Zoom deletes only the metadata and playback functionality from the web portal. The recording file in your S3 bucket remains intact.
You can restore metadata from the trash within 30 days to re-enable playback in the Zoom portal. After 30 days, or if you permanently delete the metadata, Zoom cannot restore it, and playback in the portal will no longer be available. This behavior matches how cloud recordings work for Zoom Meetings.
Effects of disabling BYOS or deleting storage locations
-
Toggling BYOS off Zoom removes all BYOS storage location configurations and deletes all associated recording metadata from your Recordings page. Files stored in S3 are unaffected.
-
Deleting a storage location When you delete a storage location, Zoom removes the associated metadata from your Recordings page but does not delete the files in your S3 bucket. The files remain accessible in S3 but cannot be played through the Zoom web portal.
Both actions result in permanent metadata removal. If you later re-add the same storage location, Zoom cannot reconstruct the playback experience in the web portal.