> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://mediakind.ferndocs.com/mkio/how-to/content-management/add-an-asset-in-mkio/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://mediakind.ferndocs.com/_mcp/server. # Create an asset An asset in MK.IO is a container for your media content: it groups your video, audio, subtitle files, and encoding outputs together and links them to a location in your cloud storage (Azure Blob Storage or Amazon S3). You create an asset first, then add content to it. You need at least one storage account connected before creating assets. See [Connect cloud storage](/mkio/getting-started/connect-cloud-storage). ## Steps ### Go to Assets Navigate to **Assets** in the left sidebar and click **+ Create Asset**. ### Choose a source * From a storage account: Creates an asset linked to your cloud storage. Use this when pointing to existing files or creating an empty location for new files. * From local files: Uploads files from your device and creates the asset in one step. See Upload from your device. ### Fill in the details | Field | Description | | ------------------- | ------------------------------------------------------------------------------------------------- | | Storage account | The connected Azure or S3 account where this asset’s files will live | | Storage container | The container (Azure) or bucket (S3) name. Use lowercase letters, numbers, and hyphens. | | Storage directory | Optional subfolder path within the container | | Asset name | The display name you will see in MK.IO | | Description | Optional notes | | Upon asset deletion | Whether deleting the asset also deletes files from storage. You cannot change this setting later. | ### Create Click **Add**. The asset is created and linked to the storage location you specified. If you point to an existing container and the asset appears empty, the container name may be misspelled or the wrong storage account selected. The field is case-sensitive. See [Verify your assets](/mkio/how-to/content-management/verify-your-assets-in-mkio) for troubleshooting. ## Next steps Once the asset exists, add content and prepare it for streaming: [](/mkio/how-to/content-management/add-an-asset-in-mkio/reference-existing-storage) ### Content already in Azure or S3 Point an asset at existing cloud storage, find the container name, and troubleshoot empty assets. [](/mkio/how-to/content-management/add-an-asset-in-mkio/import-files-from-your-device) ### Upload from your device Upload files from your computer directly into the asset. [](/mkio/how-to/content-management/verify-your-assets-in-mkio) ### Verify the asset Confirm files and tracks are visible before publishing. [](/mkio/how-to/content-management/add-an-asset-in-mkio/import-your-ams-assets) ### Migrating from AMS? Reference existing AMS asset containers without re-encoding. ## Automate asset management Use the [Assets API Guide](/platform/how-to/media/assets) to create assets, reference source files, retrieve tracks, and manage asset lifecycle operations through the Media API. ## Docs - [Bulk import your AMS assets](https://mediakind.ferndocs.com/mkio/how-to/content-management/add-an-asset-in-mkio/bulk-asset-migration-from-ams-storage.md) - [Import your AMS assets](https://mediakind.ferndocs.com/mkio/how-to/content-management/add-an-asset-in-mkio/import-your-ams-assets.md) - [Reference existing cloud storage content](https://mediakind.ferndocs.com/mkio/how-to/content-management/add-an-asset-in-mkio/reference-existing-storage.md) - [Upload files from your device](https://mediakind.ferndocs.com/mkio/how-to/content-management/add-an-asset-in-mkio/import-files-from-your-device.md)