> ## Documentation Index
> Fetch the complete documentation index at: https://gcore.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrate CDN resource with Concrete5

Before you take any steps please back up your files and database. The plugin works only with default CMS pattern. If you manually changed CMS patterns, the plugin might not help you.

Create a [CDN resource](/cdn/getting-started/create-a-cdn-resource/create-a-cdn-resource) before you start with integration.

Install one of [Concrete5](https://concrete5.org) CDN extensions. Here are 3 of a large number of available extensions:

* [CDN Manager](https://concrete5.org/marketplace/addons/cdn-manager)
* [Content Delivery Network (CDN)](https://marketplace.concretecms.com/marketplace/addons/content-delivery-network-cdn/)
* There's also a [CDN package for ?oncrete5](https://github.com/concrete5/concrete5/pull/771) that allows you to transfer your static files to CDN. The package is free

During or after the installation of an extension, you need to type in the CNAME that you specified in the [Gcore Customer Portal](https://portal.gcore.com/cdn/resources/list). Ensure that your [CNAME record has been configured](/cdn/cdn-resource-options/general/create-and-set-a-custom-domain-for-the-content-delivery-via-cdn) in a proper way before using it for integration (e.g., *cdn.site.com*).

Integration has been completed! We highly recommend you to check the HTML code of your web page to ensure that URLs have been rewritten properly from your original ones to CNAME from the Gcore Customer Portal.

To do that press **F12** or open Developers Tools in your browser, choose the Network tab and refresh the page. All static files should have your CNAME in URLs.