Overview

Storage holds the source videos you upload and the files Chunkify produces. By default, uploads, new video assets, and Transcodes use the Project's default storage. You can select another storage configuration for each one.

Temporary vs custom storage

Chunkify temporary storage lets you test without setting up your own bucket. Files stored there are deleted after 24 hours.

For production, connect your own Amazon S3, Cloudflare R2, or S3-compatible storage so you can keep your source videos and outputs long term. You control the bucket and file retention. For video streaming, configure a CDN for the bucket and add its base URL to the storage connection.

For browser uploads and playback, check the CORS rules on your bucket and CDN.

Source videos

Uploads use your Project's default storage unless you choose another storage configuration.

If the video is already in your bucket, you can create a Source from its object key. Chunkify reads the existing file without copying it.

The Source and video output can use different storage configurations.

Video asset outputs

Chunkify writes the HLS stream, poster, and timeline previews to the video asset's selected output storage. Any static renditions or captions you add later use the same storage.

The storage connection's output prefix and the video asset's folder template determine where those files go. See Output paths for the available settings.

Transcode outputs

Transcodes use the Project default output storage unless you override it. For your storage, provide a filename relative to its output prefix. Each request saves that prefix at creation.

See Transcode output paths. Existing Jobs API integrations have separate legacy path guidance.

Modify a storage setup

You can update your storage configuration: output prefix, CDN base URL, and credentials without creating a new one. A new output prefix does not move existing files or change a video asset's saved output folder. A new CDN base URL changes the URLs Chunkify returns for files already in the bucket, so check that the new hostname serves their existing object paths. See Output paths and CDN delivery before changing these settings.

To rotate credentials, replace the access key ID and secret access key together. Chunkify checks the replacement pair before saving it. Existing video assets and sources keep their storage connection, but work already in progress or signed URLs already issued may still use the old key. Keep that key active until those operations finish when possible.

Data transfer costs

Chunkify's charge for transferring processed outputs to your storage depends on the provider:

Storage provider	Chunkify transfer charge
Amazon S3	No additional charge
Cloudflare R2	$0.09 per GiB
S3-compatible storage	$0.09 per GiB

The S3-compatible rate also applies to providers behind custom endpoints. These charges cover transfer from Chunkify to your bucket, not playback from your CDN to viewers. Your storage or CDN provider may charge separately for storage, source reads, and delivery.