Image path parsing error

Before opening a new bug report, please search the forum for duplicates and follow the Troubleshooting Guide.

  • We only consider bugs that are reproducible in the sandbox vault or a vault with no third-party plugins/no css snippets/default theme.
  • For Linux, we only accept bug reports that are reproducible with our Appimage or Snap package under Gnome or KDE.
  • Developer issues with the API should go here
  • Themes and Custom CSS issues should go here
  • Translations issues/improvements should be posted here
  • Obsidian Clipper Bugs should be posted here
  • Obsidian Importer Bugs should be posted here

Once you’ve done the above, delete everything above this line.

Steps to reproduce

Image path parsing error.

When adding an image from a local disk to the editor, the image path in the editor does not match the actual image path.

Video_2025-09-02_102325.zip (1.3 MB)

Best solution:
When adding an image from a local disk to the editor, you should provide an option for the user to retain the full image path, for example.
![](F:\Document Collection\images\2025-09-01_155149.png)
You should provide an option for the user to retain a partial image path, for example.
![](images\2025-09-01_155149.png)

In addition, a new error was discovered:
The image path \images\2025-09-01_155149.png does not contain a space, but Obsidian incorrectly adds a space %203 to the path ![](2025-09-01_155149%203.png), making the image path very difficult to understand.

If you want to rename an image, it’s best to use the following:
![](2025-09-01_155149_1.png)
![](2025-09-01_155149_2.png)
![](2025-09-01_155149_3.png)


The above image naming method is the most standard, standardized, and easiest to understand image naming convention.

Did you follow the troubleshooting guide? [Y/N]

Y

Expected result

Best solution:
When adding an image from a local disk to the editor, you should provide an option for the user to retain the full image path, for example.
![](F:\Document Collection\images\2025-09-01_155149.png)
You should provide an option for the user to retain a partial image path, for example.
![](images\2025-09-01_155149.png)

In addition, a new error was discovered:
The image path \images\2025-09-01_155149.png does not contain a space, but Obsidian incorrectly adds a space %203 to the path ![](2025-09-01_155149%203.png), making the image path very difficult to understand.

If you want to rename an image, it’s best to use the following:
![](2025-09-01_155149_1.png)
![](2025-09-01_155149_2.png)
![](2025-09-01_155149_3.png)


The above image naming method is the most standard, standardized, and easiest to understand image naming convention.

Actual result

![](2025-09-01_155149%203.png)

Environment

Win10 19044 x64
August 26, 2025
1.9.12 Desktop

Additional information

I don’t see a bug here.

And how do you do this exactly?

It looks like you are importing into the vault not linking an external file

The description and video clearly explain the problem.

Well I don’t understand it