One month down in 2025: How are your resolutions coming along? Check out how to get back on track here.
Forum Discussion
Shared link keeps changing when clicking and dragging a replacement file into Dropbox desktop
In the past, when you clicked and dragged an item from your computer into your dropbox, it would keep the original shareable link. Seems that now when you do this it creates a new link. How do I stop this? Evertime I click/drag a file I have to send everyone who needs that access the new link.
- Jay
Dropbox Staff
Hi PBDonations, thanks for messaging the Community.
It can depend on how the original file is updated on your computer. If the file is deleted and then recreated, this would result in the old link being deleted.
The guaranteed method to keep the existing link is to upload the files to the Dropbox site in the same location as that file.
If you have any further queries, feel free to message back.
Hi PBDonations! I'm on the Product team for Shared Links, I'd love to understand more about how you're encountering this issue. Do you mind providing the steps you've taken? Has the item never been in Dropbox before? Are you moving it from one dropbox folder to another dropbox folder? At what point in the step are you sharing it and when are you informed everyone who needs the link needs a new one?
I use drop box to share the most recent version of a document.
A version of the document exists within dropbox.
I do any edits on the document on my personal computer. Once done, I select it and click/drag it over to drop in the dropbox. In the past, it would replace the document and keep the same shared hyperlink, but now it creates an entirely new one.
I'd update a bunch of files at the same time this way on a monthly basis usually.
I'm now using MS OneDrive instead. The issue doesn't exist with there system.
Having the same issue. Very important to be able to overwrite files without making a new one. The sharing links are sent out and posted to various places and this would be a huge headache if this option is no longer viable. Were you able to resolve this?
