
A Cloudinary private original does not automatically make every thumbnail private. By default, the private delivery type protects the original while derived versions are public. Authenticated delivery protects both, but its derivatives must be generated ahead of time. Choose the delivery contract before sending a sensitive client image.
Key Takeaways
- Private and authenticated are different delivery types.
- Protecting an original is separate from controlling derivative creation.
- A signed address is not recipient-specific access control by itself.
Map the original and the required derivatives
Cloudinary's access-control documentation states that private originals require a signed URL while transformed versions are publicly accessible by default. Strict Transformations can control which new derivatives are created; it should not be confused with making every existing derivative inaccessible.
For authenticated assets, both original and transformed files require a signature or another applicable access token. The documentation also says you cannot create authenticated transformations on the fly: eager generation during upload or update is required.
Choose a sample-based verification plan
- List the master and each intended proof size, crop and watermark.
- Record the actual resource type and delivery type for the sample asset.
- Identify which files should be publicly available and which require restricted access.
- Have the authorized implementation owner configure the appropriate delivery model in a test workflow.
- For authenticated delivery, generate the required eager variants and retain their corresponding signed URLs.
- Check intended authorized delivery and unsigned access separately for the original and each proof.
Use an expendable, non-sensitive sample for these checks. Publishing a private client's photograph merely to learn the difference would defeat the purpose of the review.
A hypothetical portrait-proof matrix
| File | Intended availability | Evidence to collect |
|---|---|---|
| High-resolution master | Restricted | Authorized delivery and failed unsigned access |
| Small approved marketing tile | Public if separately approved | Correct public derivative and content |
| Confidential client proof | Restricted | Signed delivery plus derivative-readiness check |
This matrix is an editorial planning example, not a report that any account passed.
Understand what a working link proves
An authenticated crop that fails may be absent because it was never eagerly generated. Re-signing arbitrary new crop syntax does not create it. Conversely, a working public private-type thumbnail may reflect documented default behavior rather than an account breach.
Cloudinary warns that a shared signed URL can be used by anyone holding it. If the requirement concerns particular people, sessions or time windows, examine the service's applicable access-control features with the implementation owner.
The review-link closure guide explains another boundary: closing server access does not recall an ordinary downloaded copy. Accept this workflow only when the intended original and derivative paths match their documented access policy; do not claim copy prevention.
Related tasks
- Does Revoking a Review Link Remove the Images Someone Already Downloaded?
- Can I Use a Temporary AI Download Link as My Product Feed Image URL?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- Cloudinary: Media access control: Strict transformation identity and 404 behavior; private versus authenticated originals and derivatives; eager-only authenticated transformations; final-URL signing and signature-mismatch errors; limitations of shared signed links.
Documentation-based editorial guidance. All scenarios, worksheets and acceptance checks are hypothetical or proposed. No hands-on test, account operation, benchmark, measured search demand, AI-citation rate or platform acceptance is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.