Skip to main content

Retaining the exact URL when a file is replaced with the same filename.



  • Official comment
    Akshay Joshi

    Hi Matt,
    Cloudinary automatically adds the version to URLs and this cannot be changed through configuration.  You can safely strip off the version token from the URL to access the asset.  For example: is the same as .  Maybe you can try the following (assuming you are using our upload APIs to upload from the browser):
    - Upload the new version of the asset
    - Get the version assigned to it from the upload response.  The version string is available in the response as 

     "version": nnnnnnnnn,

    See for a sample response. 
    - Programmatically Strip off the version in the url that is returned in the response and use it in your app.

    "secure_url": "",


  • Eric Pasos

    Hi Matt,

    The version of an image in the Media Library is the timestamp of when your was last updated (e.g., v1366687335), and you may remove it from your delivery URL (see Cloudinary does not require the version component to be present in URLs, and it can be removed if you don't want to use that when building your URL.

    For example:

    Hope this helps.

  • Matt Broad

    Hi Eric,

    Thank you very much for the reply and link. Please could you or anyone confirm which settings need to be applied?

    I have tried changing the ' Invalidate versioned URLs: Enable this if you use URLs with the version component, e.g. ' and many other settings but the timestamp remains. Also, is there a way to reset all settings to default? I've tried many other them in attempt to get this working.

    Thank you


  • Matt Broad

    Hi Akshay,

    Thank you very much for your reply. We're uploading through the web interface and currently we are not using the API. Images are therefore just called by their URL. I think from what you've described this means we cannot remove the version from the URLs

    As per your example, when the URL is like this
    we want to call a URL like this 

    We wish to do this so we can replace the file e.g. sample.jpg with a new one by the same name. We want to do this by uploading through the web interface and overwriting or deleting the existing sample.jpg

    Please confirm if this can be achieved without the API, else we will need to use another provider.

    Thank you


  • Danny Valentine

    Hi Matt.

    The inclusion of an asset's version number is entirely optional, and you can remove it from your delivery URL if you wish. It's worth bearing in mind though that because the updated asset will have the same URL, users  of your site/application may need to refresh their local cache before they see any changes.

    If your question is more around how you can get a versionless URL directly from the Media Library, we can make a change to your account that will update your Manage page to show separate Transform, Embed and Download buttons like so:

    Upon clicking the embed code button, you'll be given the option to include or exclude the version number:

    I've made a short video starring my cat that demonstrates everything I've said above, which I'll provide below. In this video I use an upload preset that is configured to keep the filename intact and overwrite any existing assets. I upload cat.jpg, get the image URL without a version number and then visit it in my browser. I then upload a different image called cat.jpg, open the same URL as before, and once I refresh, I see the updated image.,q_auto/versioning.mp4

    Please let us know if you'd like us to make the change on your account so you can see a versionless URL within the Media Library, or if you'd prefer to just omit the version number manually.

    Looking forward to hearing back from you.


  • Matt Broad

    Hi Danny,

    Thank you very much for this detailed reply. The video was also very helpful. I may return to request the versionless URL.

    Have a good day.


  • tolulope

    Hi, i faced this issue too, but if i rip of the versioning, and try to access the url, i get the old asset instead of the new one

  • Eric Pasos


    As it is possible that the image without the version is still being cached in our CDN, you may need to perform an invalidation process through the Explicit API (i.e., with parameter invalidate=true) by using one of our SDKs or the Command-line interface (CLI). For example:

    cld uploader explicit public_ID type=upload invalidate=true

    In case it still does not purge the old image copy, please help to open a support ticket here ( and provide the image URL so we investigate further on the case.



Post is closed for comments.