It is an imperative need. If you move your folder all the links are broken!
2 Likes
I was skeptical and Iâm really surprised that it really works 
Bumping this so that it doesnât die.
It has been years! Markdown should gracefully accept HTML where possible.
I donât want to use the ![[img.png]] syntax, since it wonât render in in my markdown->html pipeline.
I canât use the syntax, since
- it doesnât work for relative paths in Obsidian, so I have to edit elsewhere to be able to see the images;
- I canât specify only height and let width derive from aspect ratio; and
- the
|widthor|widthxheightsyntax is ignored by my â html pipeline anyway.
So, I want to have a real <img src="img.png" style="height: 210px"> syntax that works as it does in Typora and python-markdown.
Itâs little papercuts like this that drive me away from all-inclusive siloing apps like Notionâdonât make me do it Obsidianâs way; just permit as much as possible.
(Also, the security concerns for doing have never been explained in a believeable way.)
4 Likes
If a feature request isnât closed, it isnât dead â you donât need to bump. (Adding new info is fine, of course!)
+1
Absolutely critical to the using formatted embedded images/videos (dimension adjustments, alignments) within an Obsidian document while keeping them cross-compatible with other devices and future proof. Specifying the absolute path causes the image path to now be device specific, breaking the document on other devices. This is a huge pitfall to the acclaimed future-proof nature of Obsidian, if the images/videos embedded within a document breaks as soon as it is used on another device.
I plead the devs to consider this a bug, rather than a feature, and sort this out as quick as possible.
4 Likes
It has been more than 2 years, and this problem still hasnât been solved.
1 Like
Appreciate this can be resolved quickly.
1 Like
Ran into this problem today
+1
would greatly appreciate it if this is fixed
Html raw tags are very ugly and the very last resort if literally nothing else has worked.
Better to pick some plugins, imo
+1
would greatly appreciate it if this is fixed
For me that plugin didnât work. What worked for me is the solution from stormsc to put the image into a âdivâ instead of an âimgâ. Unfortunately it only shows up in reading mode but it is still a good solution.
<div src="image.png" class="internal-embed"></div>
Addition: What I wanted was to have an image link to another page and I changed my approach to use another solution that has been mentioned here then keeping that page in reading mode for the link to work. Though I understand this wonât be a solution for everyone.
[![[Image.png|400]]](<OtherPage>)
Raw HTML is ugly and goes against the spirit of markdown, but at least it keeps the note files more universally usable outside of Obsidian. For which reason Iâm against solving this with plugins.
Actually, if that âgoes against the spirit of markdownâ is important, then Iâd argue that a better solution is regular markdown image syntax with relative paths allowed, extended to allow for video embeds in a simple way if the extension is a video one.
1 Like
+1
would greatly appreciate it if this is fixed
Temporary hack that Iâve been using is embedding images in Base-64 encoding.
There are online web-utilities that you can do this in the browser from. If you prefer to not upload images to these sites, you can use the command-line as well. See https://stackoverflow.com/questions/16918602/how-to-base64-encode-image-in-linux-bash-shell or https://stackoverflow.com/questions/65577255/encode-to-base64-a-specific-file-by-windows-command-line.
Once itâs been converted you just create your image tag in Obsidian:
<img height="400px" width="400px" src="data:image/jpeg;base64,YOUR_BASE64_TEXT_HERE" />
Just replace âimage/jpegâ with âimage/pngâ if itâs a PNG image. This method has the added bonus of consolidating all your images in the note file itself. However, this will fudge with your character and word count significantly (if that matters, I wouldnât recommend this method).
Cheers.