> For the complete documentation index, see [llms.txt](https://docs.3q.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3q.video/user-guide-new-ui/modules/multi-cdn.md).
# Multi-CDN
The Multi CDN module allows you to manage CDN profiles for content delivery across different providers. CDN profiles define how video content is distributed and can be configured globally or for specific projects.
{% hint style="info" %}
The available CDN providers and profile options may depend on the account configuration and booked modules. Access to the Multi CDN module is controlled by user permissions. Users who do not have the required rights may not see the module or may have limited access to create and manage CDN profiles.
{% endhint %}
This module is designed to support flexible delivery strategies, allowing content to be routed through different CDN providers depending on geographical, operational, or project-specific requirements.
From the Multi CDN area, users can:
* View existing CDN profiles
* Create new CDN profiles
* Assign profiles globally or to individual projects
* Select the CDN provider used for delivery
* Review provider recommendations and usage guidance
The Multi CDN module is available from the main navigation under **Modules**.
***
### CDN Profile Overview
The Multi CDN overview displays all configured CDN profiles in a structured table.
Each row represents one CDN profile and includes the most relevant information:
* Thumbnail or provider preview
* Unique profile ID
* Profile title
* Assigned project
* CDN provider
* Creation date
The list supports sorting and filtering, making it easier to manage multiple CDN configurations.
Available tabs include:
* **All CDN Profiles**\
Shows all CDN profiles available in the account.
* **Global CDN Profiles**\
Shows CDN profiles that are available across all projects.
* **Project Specific CDN Profiles**\
Shows CDN profiles assigned to individual projects only.
At the top of the list, the following controls are available:
* **Search** to find CDN profiles by name or related metadata
* **Project filter** to narrow the list to a specific project
* **Provider filter** to filter profiles by CDN provider
* **Add CDN Profile** to create a new CDN configuration
***
### Creating a CDN Profile
To create a new CDN profile:
1. Open **Modules** in the main navigation.
2. Select **Multi CDN**.
3. Click **Add CDN Profile**.
4. The **Create Notification** side panel opens.
5. Enter a **Title** for the CDN profile.
6. Optionally add a **Description**.
7. Select a CDN **Provider**.
8. Define the profile availability.
9. Save the profile.
The new CDN profile will appear in the overview after creation.
***
### Provider Selection
When creating or editing a CDN profile, a CDN provider must be selected.
Available providers include:
* **3Q**
* **Akamai**
* **Wangsu**
The provider selection determines which CDN infrastructure is used for content delivery.
The interface also provides additional provider information to help users choose the most suitable CDN for their use case.
Provider guidance includes:
* **3Q**\
Optimized for performance in Europe and North America.
* **Akamai**\
Recommended for global delivery scenarios without a specific geographical focus.
* **Wangsu**\
Optimized for performance in China.
This information is displayed in the **Multi-CDN Provider** information panel and can be used as guidance when configuring delivery strategies.
***
### Availability
CDN profiles can be configured with different availability scopes.
Available options are:
* **Available in All Projects**\
The CDN profile can be used across all projects in the account.
* **Only Available in One Project**\
The CDN profile is assigned to a specific project only.
Use global availability for general delivery configurations that should be reused across projects. Use project-specific availability when a CDN setup is only required for a particular project, customer, region, or use case.
***
### Project-Specific CDN Profiles
When a CDN profile is limited to a single project, the project assignment defines where the profile can be used.
This is useful for workflows where individual projects require different delivery configurations, for example:
* Regional streaming requirements
* Customer-specific CDN setups
* Dedicated event or livestream configurations
* Testing alternative CDN providers
* Separating production and internal delivery workflows
Project-specific profiles are listed under the **Project Specific CDN Profiles** tab.
***
### Global CDN Profiles
Global CDN profiles are available across all projects in the account.
They are useful when the same CDN configuration should be reused consistently for multiple projects.
Typical use cases include:
* Standard account-wide CDN delivery
* Default delivery configuration
* Shared fallback profiles
* Common delivery strategies for multiple teams or departments
Global profiles are listed under the **Global CDN Profiles** tab.
***
### Managing Existing CDN Profiles
Existing CDN profiles are displayed in the Multi CDN overview.
From the list, users can review:
* Profile title
* Assigned project
* Selected provider
* Creation date
Depending on user permissions, existing profiles can be opened and adjusted.
Changes to CDN profiles may affect content delivery behavior. For this reason, provider and availability settings should be reviewed carefully before making changes in production environments.
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.3q.video/user-guide-new-ui/modules/multi-cdn.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.