
Cloudinary does not invalidate signed URLs by default, even when an asset replacement requests cache invalidation. A previously signed address can therefore keep showing old content. Check the exact URL and account configuration, then have the backend generate the approved new-version address or arrange supported signed-URL invalidation.
Key Takeaways
- Replacing stored content and clearing every cached delivery path are different operations.
- Signed URLs have a documented invalidation exception.
- Use the SDK and the documented signing contract to generate the intended revision URL.
Separate the stored revision from the observed URL
Cloudinary's invalidation documentation says delivered versions can remain cached after an overwrite, rename or deletion. It documents invalidate:true for supported operations, but specifically notes that signed URLs, with or without versions, are not invalidated by default. Signed-URL invalidation requires a service request.
Keep the exact old and intended new rendition identities in a private note. Record whether the URL includes a version and whether the account uses a legacy invalidation configuration. Do not assume every environment follows the same URL-invalidation table.
Repair the revision path deliberately
- Verify that the stored replacement is the intended approved image.
- Compare the actual URL the page requests with the expected rendition, including its version and signature.
- Check whether invalidation was requested for that replacement.
- Ask the implementation owner whether the observed signed URL is covered by the account's supported invalidation configuration.
- Where the implementation uses versioned delivery, generate the complete new-version URL through the backend.
- Verify the direct response before examining a downstream page or sharing-platform preview.
Use the SDK and Cloudinary's documented signing contract when generating the intended revision URL. This guide does not infer whether a version-only change alters signature validity. Inspect the actual returned image to establish which revision is delivered.
A hypothetical corrected product tile
Suppose a client corrects the visible package label. The asset library shows the correction, but the shop still requests a previously signed tile URL. The proposed diagnostic compares that direct response with the stored replacement.
If the direct address is stale, revising the page's caption cannot fix it. If the direct address is current but one social preview is stale, the unresolved stage has moved downstream.
Acceptance and boundaries
Record the public-page reference, privately held signed rendition identity, observed direct image and review timestamp. Use a clean session to distinguish an additional local browser cache from the CDN observation.
The shared-link preview guide covers page metadata, asset responses and downstream previews. This guide adds the provider's signed-URL invalidation exception. Invalidation does not erase copies already downloaded or caches outside Cloudinary's network, and no fixed refresh deadline or successful invalidation test is claimed.
Related tasks
- Why Does a Shared Link Still Show My Old Image After I Updated the Page?
- Why Does Google Still Show My Old Product Image After I Upload a New One?
- Can I Use a Temporary AI Download Link as My Product Feed Image URL?
Sources and scope
- Cloudinary: Invalidate cached media assets on the CDN: Cached content can outlast replacement; supported invalidate requests; signed URLs are not invalidated by default; versioning and configuration-specific invalidation boundaries.
- 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.