const response1 = await channel.sendImage(
file1,
file1.name,
file1.type,
undefined,
// Optional
{
onUploadProgress: (e) => {
const pct = e.total ? Math.round((100 * e.loaded) / e.total) : 0;
console.log(`Image upload: ${pct}%`);
},
},
);
const response2 = await channel.sendFile(
file2,
file2.name,
file2.type,
undefined,
// Optional
{
onUploadProgress: (e) => {
const pct = e.total ? Math.round((100 * e.loaded) / e.total) : 0;
console.log(`File upload: ${pct}%`);
},
},
);
await channel.sendMessage({
text: "Check these out",
attachments: [
{
type: "image",
asset_url: response1.file,
thumb_url: response1.file,
},
{
type: "file",
asset_url: response2.file,
title: file2.name,
},
],
});Image and File Uploads
Stream Chat allows you to upload images, videos, and other files to the Stream CDN or your own CDN. Uploaded files can be used as message attachments, user avatars, or channel images.
Stream's UI SDKs (React, React Native, Flutter, SwiftUI, Jetpack Compose, etc.) handle file uploads automatically through their message composer components. The upload process, progress tracking, and attachment handling are built into these components. Use the methods described on this page only if you need custom upload behavior or are building a custom UI.
Uploading Files to a Channel
Files uploaded to a channel can be attached to messages. You can either upload a file first and then attach it to a message, or let the SDK handle the upload when sending a message with attachments.
Uploading Standalone Files
Files not tied to a specific channel can be used for user avatars and channel images, i.e. stored in the image or image_url field of a user or channel object.
Like channel attachments, standalone Stream CDN URLs expire (see Access Control and Link Expiration). They are refreshed automatically only when stored in the image or image_url field of a user or channel object, which are re-signed when the user or channel is retrieved (e.g. when querying users or channels). A Stream CDN URL kept anywhere else (a different custom field, your own database, etc.) is not refreshed and stops working once it expires. For those use cases, do not use the Stream CDN.
const { file: imageUrl } = await client.uploadImage(
imageFile,
imageFile.name,
imageFile.type,
undefined,
// Optional
{
onUploadProgress: (e) => {
const pct = e.total ? Math.round((100 * e.loaded) / e.total) : 0;
console.log(`Image: ${pct}%`);
},
},
);
// Example: use the image URL as a user avatar
await client.partialUpdateUser({
id: userId,
set: { image: imageUrl },
});Deleting Files
Delete uploaded files to free storage space. Deleting a file from the CDN does not remove it from message attachments that reference it.
// Delete from channel
await channel.deleteFile(fileURL);
await channel.deleteImage(imageURL);File Requirements
Images
| Requirement | Value |
|---|---|
| Supported formats | BMP, GIF, JPEG, PNG, WebP, HEIC, HEIC-sequence, HEIF, HEIF-sequence, SVG+XML |
| Maximum file size | 100 MB |
Other Files
| Requirement | Value |
|---|---|
| Supported formats | All file types are allowed by default. Different clients may handle certain types differently. |
| Maximum file size | 100 MB |
Configuring Allowed File Types
Stream allows every extension and MIME type by default. Your app can be configured to be more restrictive through file_upload_config and image_upload_config:
| Setting | Effect |
|---|---|
allowed_file_extensions | Only these extensions are accepted. Everything else is rejected. |
blocked_file_extensions | These extensions are rejected. Everything else is accepted. |
allowed_mime_types | Only these MIME types are accepted. Follows the type/subtype format. |
blocked_mime_types | These MIME types are rejected. |
size_limit | Maximum accepted size in bytes. 0 falls back to the 100 MB default. |
Set them in the Dashboard under Chat Overview > Upload Configuration, or with the App Settings endpoint.
Uploads Rejected by Your Configuration
Upload restrictions live on the app, not on the device. A client SDK cannot read or change them, so the same limits apply to every upload from every SDK, and a client integration has to handle the rejection rather than prevent it.
Rejection happens at upload time, before the message is sent. The upload call fails and returns no attachment URL, so the message never gets the attachment. Handle the failure and tell the user which rule they hit. A file over the size limit returns HTTP 413 with Stream code 22, listed in API error codes.
If your app restricts uploads, mirror the same rules in your own file picker. Users get immediate feedback instead of waiting for an upload to fail.
Access Control and Link Expiration
Stream CDN URLs include a signature that validates access to the file. Only channel members can access files uploaded to that channel.
| Behavior | Description |
|---|---|
| Access control | URLs are signed and only accessible by channel members |
| Link expiration | URLs expire after 14 days |
| Automatic refresh | Message attachment links are refreshed when messages are retrieved (e.g., when querying a channel). Standalone uploads are refreshed only when stored in image / image_url on a user or channel object, and re-signed when that user or channel is retrieved. |
| Manual refresh | Call getMessage to retrieve fresh URLs for expired attachments |
To check when a link expires, examine the Expires query parameter in the URL (Unix timestamp).
Image Resizing
Append query parameters to Stream CDN image URLs to resize images on the fly.
| Parameter | Type | Values | Description |
|---|---|---|---|
| w | number | Width in pixels | |
| h | number | Height in pixels | |
| resize | string | clip, crop, scale, fill | Resizing mode |
| crop | string | center, top, bottom, left, right | Crop anchor position |
Images can only be resized if the source image has 16,800,000 pixels or fewer. An image of 4000x4000 pixels (16,000,000) would be accepted, but 4100x4100 (16,810,000) would fail.
Resized images count against your storage quota.
Using Your Own CDN
All SDKs support custom CDN implementations. Implement a custom file uploader to use your own storage solution.
messageComposer.attachmentManager.setCustomUploadFn(async (file) => {
const result = await customCDN.upload(file);
return { file: result.url };
});