
Adding a crop, watermark or delivery flag after a Cloudinary URL has been signed can invalidate its signature. Generate the signature from the final transformation and public ID, then distribute that complete URL. Reusing the old signature with a modified path is not a supported way to authorize another rendition.
Key Takeaways
- A delivery signature covers transformations as well as the public ID.
- Build the complete rendition first and sign it server-side.
- A signed link does not by itself prevent recipients sharing it.
Separate a signature mismatch from a missing asset
Cloudinary's access-control guide documents that changing transformations in a signed URL can produce a 401 response. For authenticated media it can report Unauthenticated access in x-cld-error; with Strict Transformations, the error can identify a transformation that is not allowed.
Capture the status and error text privately, together with a redacted description of the change. Never paste a complete client URL or signing secret into a public support post. A missing asset, wrong delivery type or unavailable authenticated derivative still needs its own check.
Rebuild and sign the intended rendition
- Keep the original successful link as evidence, without editing its string.
- Write down the desired final public ID, delivery type and full transformation chain.
- Have the authorized backend generate that final URL through Cloudinary's signing-capable SDK.
- Keep the API secret on the server; do not move signing into public browser code.
- Replace the application's reference with the newly generated complete URL.
- Fetch the result through the intended recipient path and inspect the crop, watermark and response.
For authenticated assets, signing alone does not create an arbitrary new derivative on demand. The documentation requires transformed assets to be generated ahead of time using eager transformations. Confirm that prerequisite before treating another 401 or delivery failure as a signing-code defect.
A hypothetical watermarked proof
A studio has a working signed portrait crop. Someone appends a logo transformation to protect the proof and retains the old signature. The proposed repair is to define the watermarked proof as the final rendition, generate any required eager derivative and obtain its matching signed address.
A pass means that the delivered file contains the approved mark and framing. It does not mean the recipient cannot copy the picture or forward the address. Cloudinary explicitly warns that exposing a signed URL lets anyone holding it access the asset.
Close the delivery record
Keep the approved rendition specification with the private implementation record, rather than using the URL as an editable design recipe. The temporary-link guide covers a different decision: whether controlled delivery is suitable for a publicly crawled product feed.
If the new URL still fails, compare delivery type, derivative readiness and the exact backend inputs. Do not weaken access controls as a substitute for identifying the failed stage. No signing or delivery test is claimed here.
Related tasks
- Can I Use a Temporary AI Download Link as My Product Feed Image URL?
- Does Revoking a Review Link Remove the Images Someone Already Downloaded?
- Keep a Lightroom Watermark Readable Across Different Crops
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.