Skip to navigation
Delivery

CDN settings

Setup custom CDN CNAME, cache duration, search engine indexing behavior, or even bring your own CDN.

Find your project’s CDN domain

Every project has one or more CDN domains. Find them in the dashboard or in the URLs that the APIs return.

In the dashboard

  • Settings › Delivery › CDN domain names: lists every domain that serves the project’s files, each with a copy button. This is the project’s subdomain on ucarecd.net and, if your project has them, a custom CNAME, the legacy ucarecdn.com domain, and the secure domain for signed URLs. Open Delivery settings.
  • Files › file details › CDN URL: open any file and click Copy URL to get its full CDN URL.

In API responses

The APIs don’t return the domain as a separate field. File and group URLs in their responses start with it:

Note: API responses use the domain the project currently serves files from: a custom CNAME, ucarecdn.com, or the *.ucarecd.net subdomain. It may not match the subdomain in the Delivery tab. For example, projects that still have the legacy domain get ucarecdn.com URLs.

Custom CDN CNAME

Use your own domain for CDN links to your files stored with Uploadcare.

By default, files are delivered from your project’s subdomain on *.ucarecd.net.
Accounts created before September 4, 2025 can continue using the legacy global domain ucarecdn.com, and also have their project’s subdomain available in the Delivery tab of project settings.

By setting a Custom CDN CNAME, the file URLs can use cdn.mycompany.com instead.

Depending on your plan, you can connect Uploadcare CDN to your domain or subdomain with the Certainly TLS certificate. Custom plans let you bring your own certificate.

Pick a domain name you want to use (e.g., cdn.mycompany.com), contact us and let us know about your choice.

We’ll tell you the domain name your CNAME should point to, e.g. mycompany.ucarecd.net.

Add a CNAME record to your DNS zone, e.g.: cdn.mycompany.com CNAME mycompany.ucarecd.net

We’ll issue an SSL certificate on our end, so you don’t need to provide your one. Then we’ll set things up on our side. It usually takes 1-2 business days. Once everything is set up, and DNS changes propagate, you will need to use new URLs with your domain name.

Configure your widgets to return proper URLs, e.g.:

UPLOADCARE_CDN_BASE = "https://cdn.mydomain.com";

Replace hostname in URLs of already uploaded files served by your app. We recommend having an easily configurable setting over the hard-coding hostname of your URLs.

CAA record

In some cases, in addition to the CNAME record, you may also need to add a CAA record to your DNS zone.
A CAA record specifies which certificate authorities (CAs) are allowed to issue TLS certificates for your domain.
Using CAA records is recommended as a best practice. See CAA record — Wikipedia for details.

If your domain does not have any CAA records, no action is needed: Uploadcare can issue a certificate automatically.
If your domain already has CAA records, you should explicitly allow Certainly, otherwise certificate issuance may fail.

Example:

0 issue "certainly.com"

If you are not sure whether your domain already has CAA records or which CA to authorize, please contact us.

Cache duration

By default, uploaded files are cached for up to one year. When a file is deleted, its cached versions are automatically invalidated across the CDN. Invalidation is normally near-instant, though propagation can occasionally take longer. Contact us if a deleted file’s cached version is still being served after some time.

Search engine indexing

Uploadcare adds response headers that tell search engines not to index the content of files in your project to increase the privacy of your and your user’s data. You can toggle this behavior separately for each project in the Dashboard.

File indexing by search engines is disabled by default.

Bring your CDN

If you depend on a specific CDN infrastructure or are under contract, you can use your current CDN with our platform. Schedule demo with us.