Skip to main content

Copy image in another folder



  • Roee Ben Ari

    Hi Pierre, as folders are included within the public ID, renaming it will move the image from one folder to the other.
    For more information:

  • Yevgen Kubichka

    Old post, but it was about copying, not renaming.

    Is there a way to copy an image?

  • Raya Straus

    Hi Yevgen,

    We currently don't support copying. The best option in such a case would be to re-upload the image with the same public id to a location of your choice. 


  • Riley O'Brien

    +1 for being able to copy an image :)

  • Pawel Wisniewski

    +1 same here

  • Ben Collier

    +1 - Re-uploading images quickly becomes too time-consuming at scale. 

  • David Grant

    +1 - Is there a reason why duplication is not available? A unique 'tag' is better/easier perhaps??

  • Shirly Manor

    In order to provide better feedback, we will need to know more information about your use-case that required duplications.
    You might want to try our collection feature that is a dynamic way to create groupings of assets, regardless of their folder structure.
    You can read more about it [here](

    Please note, the sharing and permissions functionality in the collection is relevant only for multiple user accounts, which is supported from the Advanced plan and higher.

  • Valentino Pereira

    It's 2021, is there a copy asset feature yet?

    Use case: I have versioning on my application where client maintains multiple versions of video galleries, so whenever the client creates a version of the gallery, the assets in the original gallery get duplicated for use in the new versioned gallery - in this new gallery the assets can be freely managed like deleted, renamed etc. without affecting the original gallery.

    Requesting for cloudinary's input asap!

  • Stephen Doyle

    Hi Valentino,

    The quickest UI option for duplicating an existing original asset so that it's accessible via another, different public_id is still to re-upload the same image with a new public id.

    Because you can upload files using a URL, you can copy the first asset's original URL from Media Library, specify the new public_id to use via the upload widget, then paste the original asset's URL in the 'web address (url)' option.

    For the benefit of others who need to do this in the Media Library, the current steps in June 2021 look like this:

    Step 1:

    Step 2:


    In your case specifically, because you're performing bulk operations, the API is the recommended method for this because you're working with multiple files at once.

    From what you've said about what you're doing, I'd also suggest that a more scalable solution may be to store each asset only once and to use your own database or metadata in the Media Library to track which assets are in which 'version' of a gallery.

    Using our product gallery widget for example, you could tag all assets in v1 of a "gallery" with `gallery123v01` and then use that tag in the gallery widget or a client-side asset list, if applicable. Then when a new version of the gallery is crated, you can upload any new/missing assets and tag all the selected assets for the new version with `gallery123v02`, and so on...

    Also, as Shirly said in an earlier comment, we'd be interested to hear more about use-cases for saving multiple copies of the same original asset so we can share the details with our product team for consideration.

    Deliberately creating duplicates is not something we're asked about often because it uses additional storage, and usually it's the opposite: its very common for developers using our transformations features to store a single copy of an asset and use transformations to deliver derived (transformed) copies of that asset depending on where the asset is being used), and for customers using our DAM for their asset management to want only a single definitive copy of each asset for use in their other workflows.


  • Gabe

    It is wild that this feature doesn't exist.  Could definitely use it because we want to let people clone galleries that can be fully isolate from one another. 

  • Tia Esguerra

    Hi Gabe, 

    If you want to open a feature request for this, you can open a support ticket here: 

    In the body, explain your use case for this feature in as much detail as possible, and also the level of importance for you. Then if our team decides to implement this in the future, we could let you know when that happens. 

    Kind Regards, 


  • Cornelius Carstens

    Hi Tia,

    I just submitted a feature request via the roadmap for exactly this.

    Use case is the prototyping phase of the creation of asset delivery pipelines for generative visual systems that run in multiple instances where we need to work flexibly with test content without losing tags/metadata.

    Feel free to reach out if you have questions about the use case.



  • Tamara Yulevich

    Hi Cornelius, 

    In order to provide better feedback, we will need to know more information about your use-case. Could you please open a new private ticket here and elaborate some more?




Post is closed for comments.