Uploadcare custom S3 storage disables CDN transformations

TL;DR

Test a transformation URL right after switching storage backends.

Steps

1. Choose custom storage only when company policy requires files in your own bucket, and accept the loss of CDN operations. If you need transformations, keep Uploadcare storage and back up to S3 separately. Test a transformation URL right after switching storage backends.

When to use

You are seeing this: Choose custom storage only when company policy requires files in your own bucket, and accept the loss of CDN operations. Use this skill when you run into "Uploadcare custom S3 storage disables CDN transformations".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Official docs (Uploadcare glossary): you can connect your own S3 bucket as custom storage so uploaded files land there instead of Uploadcare servers, but Uploadcare CDN features will not be available. That includes image transformations and adaptive delivery via CDN URL operations. Agents that wire custom storage and keep building transformation URLs get unprocessed originals.

Verified resolution: Choose custom storage only when company policy requires files in your own bucket, and accept the loss of CDN operations. If you need transformations, keep Uploadcare storage and back up to S3 separately. Test a transformation URL right after switching storage backends.

Source URL: https://github.com/textpain/graveyard/blob/HEAD/uploadcare-docs/old-docs/start/glossary.mdx