
The short answer: there are two ways to put a CDN to work. The whole site: the domain points at the CDN (through its nameservers or a DNS record), and all the site’s traffic passes through it. Files only: the site still goes straight to the server, and only images, CSS, JS, videos and downloads come from another address, usually a subdomain such as cdn.yourdomain, which the CDN fetches from the origin. Both are valid; what changes is what you touch and what can break. We do not sell a CDN: what follows applies to whichever CDN you choose, on an account of your own, opened directly with that provider.
The two side by side
| Aspect | Whole site | Files only |
| What changes in DNS | The nameservers, or the site’s record, point at the CDN. | Only a new subdomain (a CNAME to the CDN). Everything else stays. |
| Stays out, but you must check the mail records do not go through the CDN. | Not touched. | |
| Protection and filtering | For everything, pages and admin login included. | For the files only. The site and the login still go straight to the server. |
| HTML caching | Possible, with rules. | No: files only. |
| What changes on the site | Nothing in the addresses. | File addresses switch to the subdomain (a plugin or a CMS setting). |
| Certificate | The CDN issues one for the domain; the server’s stays. | The subdomain needs a certificate at the CDN. |
| If the CDN fails | The whole site is affected. | Images and styles go missing, but pages still arrive. |
| Undoing it | Put the nameservers or records back: switching the CDN off. | Turn off the address rewriting on the site. |
Setting up a files-only CDN
|
|
|
|
|
|
| A CDN of this kind only holds what the server holds. Delete an image from the site and it disappears from the CDN once its lifetime runs out. Do not confuse this with moving files to external storage: then they are no longer on your hosting and no longer in the account backups. If you do that, backing those files up becomes your job: making and keeping your own backup. |
| How to choose: if the site itself is fast and the weight is in photographs and files, files only is enough, and you leave the nameservers alone. If you also want protection in front of everything and the server address hidden, go for the whole site. Either way, optimise images first (image optimisation and WebP) and measure before and after (testing whether it made a difference). |
|
Deciding between the two and want a second opinion? Tell us the site address and where your visitors are. Open a support ticket |
RECOMMENDED PRODUCT Web hosting with cPanel Domain and SSL included, daily backups and the panel you already know. from $6.60/mo (3-year plan, with coupon) See plans |











