In a sense, I agree with you. The thing about bug vs feature request from a dev POV is because this is not a corner case to be fixed, this is a whole new system to be implemented. I understand from the user POV this is a bug.
I would go as far removing relative path mode until this is done or adding warning as you suggested.
Yes I think a warning would be good enough. Removal of relative path mode might break other people’s workflow and I wouldn’t want to see that either.
I totally agree with and recognize that it might require a substantial amount of work to implement that properly. But when it’s done it really would be awesome, because if it is paired with markdown link mode, it makes it super easy for a lot more markdown editors to play nicely with the files we create using Obsidian.
Hmm, where are we on this feature ? I make a test today and seeing that moving files to sub-level will auto change the relative path, but then moving up to parent-level will not. HOWEVER tho, in obsidian it still show the correct attachment in preview mode, even the link is now broken. This is pretty dangerous behavior as it causes data corruption and it’s very annoying to recover it. Any comment ?
I just want to confirm that this bug is still present - moving a file’s location when it has a relative link within results in no change in the links within the document itself. (Links TO the document are updated, just not WITHIN the document.) I am using v0.12.15. Thank you for your attention to this!
I’m also waiting for a fix.
unfortunately the developers do not consider this a serious problem.
besides, only the relative path is the “FUTURE-PROOF FORMAT” (as in the program description)
because it is supported by other applications(Typora, etc)
Is there any plan to at least add the warning inside Obsidian’s Settings > Files & Links > New link format?
I think this is a really dangerous setting if people are not inspecting the behaviors carefully, particularly because that those incorrect links (corrupted data) can still be interpreted correctly by Obsidian itself but obviously not other editors. This means that people might not even notice their data has been/is/will be corrupted, for a workflow that seems to work well within and only within Obsidian itself.
I acknowledge that this might not be fixed (or implemented, per dev’s POV) in the near future. But I feel the lack of warning when the devs are aware of the issue is inappropriate, especially when Obsidian bills itself as future-proof.
Please let me know if I’m missing anything, and I apologize if the warning is mentioned somewhere, or if the issue has been resolved.
Still，no solution…
it really bugs me.
Hi team, just broke links on about 700 files because there was no indication that this would happen. A fix would be really nice 
EDIT: huh! looks like closing & relaunching Obsidian updated all the links, actually!
Not a fix, but you can use this tool to find broken links and correct them manually, if there aren’t many:
Any news on this bug? With v0.15.9 the bug is still there. Maybe someone can explain me why this bug is so difficult to fix!?
Just wanted to confirm that this problem still persists in 0.15.9. As others have pointed out, a fix to this is essential to make Obsidian notes truly portable to any other markdown-based system.
I recently reorganized my Obsidian folder without knowing about this bug and disabled dozens of internal links.
You seem to have let this bug go unchecked for 2 years, do you have any plans for improvement?
I use Obsidian to create Markdown Wiki’s and the relative linking feature is a big reason why I use this tool.
Hope this feature/ bug is implemented/ fixed soon. Its been more than 2 years since this was reported (now we are at v1.1.15) and not sure is this even on the list of things to be implemented/ fixed.
As a interim solution it would be great if Obsidian would show some sort of warning which indicated that when using relative path it is possible for the links to break sometimes.
I was wondering if there was an update on plans to fix this bug? Thanks!
While I appreciate that this is a not-intuitive, valuable, feature request from the dev team’s perspective, and I understand that implementing this will take time and from what I can read here, it is not a priority. This is all understandable, even when it’s not ideal for me.
But I would urge and appreciate if the team could 
add a warning or notes directly inside the software so users are aware of the current limitation when they configure their Obsidian, where important notes are created with effort and time. This will certainly take some time of the dev team, but presumably much less than actually implementing this feature.
I don’t want to be rude, sound criticizing, or nag – but you have also suggested adding some warning since two years ago. Adding the warning will really do good for many of your users. I am curious if there’s any concern that I have overlooked about adding the warning. If so, it would be helpful if you wouldn’t mind sharing so we know why this warning message has yet to be added.
At the very, very least it should be mentioned in the help docs. Currently the docs don’t even mention the relevant option.
The help docs have a GitHub where issues can be posted, and even pull requests if you feel up to it (but definitely read the README before doing that). There’s a link to it in the “Contributing” section at the bottom of the help homepage. GitHub - obsidianmd/obsidian-help: Help documentation for Obsidian.
I just discovered the existence of this bug after spending the weekend reorganizing my vault.
As @CawlinTeffid notes, it should at “very least” be mentioned in the documentation. That would have spared me a lot of time and effort.
Guess I will revert back to my old vault structure (thankfully I save my work religiously) until this bug is dealt with. I don’t have the time nor the inclination to review every single work-related link.
It’s disappointing as Obsidian is my workhouse, and as time evolves so does my workflow and my ideas of how it should be implemented. It seems as if I’m now stuck with a vault structure that is no longer to my liking nor as efficient as I would like it to be.
I’m still having this problem on ubuntu 22.04 obsidian 1.5.3v