> This page is for version v1.3 (default).
> For other versions, use one of these documentation indexes:
> - v1.3 (default): https://docs.twelvelabs.io/v1.3/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.twelvelabs.io/llms.txt.

## Asynchronous upload validation

The platform now processes every upload asynchronously. When you create an asset with [direct uploads](/v1.3/api-reference/upload-content/direct-uploads) or [multipart uploads](/v1.3/api-reference/upload-content/multipart-uploads), the platform returns the asset immediately with the `status` field set to `processing`. The asset transitions to the `ready` status when it is available for use, or to `failed` when the file is invalid or corrupt. Poll the [Retrieve an asset](/v1.3/api-reference/upload-content/direct-uploads/retrieve) endpoint until the `status` field is `ready` before you use the asset.

**What changed**:

* **Polling now applies to every upload.** Previously, only public URL uploads larger than 200 MB returned `processing` and required polling; smaller uploads returned `ready` in the create response. Now, every upload returns `processing`, so you must poll before using any asset.
* **Invalid files now fail asynchronously.** Previously, an invalid or corrupt file returned an error at upload time. Now the upload succeeds, and the asset transitions to the `failed` status, which you detect by polling.

If your integration already polls the asset status until it's `ready`, as shown on the [Direct uploads](/v1.3/api-reference/upload-content/direct-uploads) and [Multipart uploads](/v1.3/api-reference/upload-content/multipart-uploads) pages or in the guides, no change is required. Otherwise, poll until the status of the asset is `ready` before you use it:

#### Python

```python
import time

asset = client.assets.create(method="url", url="<YOUR_VIDEO_URL>")
while asset.status == "processing":
    time.sleep(5)
    asset = client.assets.retrieve(asset.id)
if asset.status == "failed":
    raise RuntimeError("Asset processing failed")
```

#### Node.js

```typescript
let asset = await client.assets.create({ method: "url", url: "<YOUR_VIDEO_URL>" });
while (asset.status === "processing") {
  await new Promise((resolve) => setTimeout(resolve, 5000));
  asset = await client.assets.retrieve(asset.id);
}
if (asset.status === "failed") {
  throw new Error("Asset processing failed");
}
```

This change does not require an SDK upgrade.

## Technical metadata for assets

The [Retrieve an asset](/v1.3/api-reference/upload-content/direct-uploads/retrieve) and [List assets](/v1.3/api-reference/upload-content/direct-uploads/list) responses now include an object named `technical_metadata` with details read from the media file: the container format, per-stream video and audio properties, image properties, and derived attributes such as aspect ratio. The platform populates this object asynchronously after the upload completes.
To access this feature, upgrade your SDK to the latest version:

**`Python SDK`**

```sh Python SDK
pip install --upgrade twelvelabs
```

**`Node.js SDK`**

```sh Node.js SDK
npm install twelvelabs-js@latest
```

For details, see [Retrieve an asset](/v1.3/api-reference/upload-content/direct-uploads/retrieve) in the API Reference section, or the SDK reference for [Python](/v1.3/sdk-reference/python/manage-assets#retrieve-an-asset) and [Node.js](/v1.3/sdk-reference/node-js/manage-assets#retrieve-an-asset).

## Higher upload limits

* **Multipart uploads** now support local videos up to **10 GB** (previously 4 GB).
* **Image uploads** now support files up to **32 MB** (previously 5 MB), for both local files and public URLs.

These limits apply when you create an asset. Each model still enforces its own file size and duration limits. For details, see the [Upload and processing methods](/v1.3/docs/concepts/upload-methods) page.

Public video and audio URL uploads remain limited to 4 GB. This change does not require an SDK upgrade.