# Markdown base62 image name vs. full \<img\> path?

**URL:** https://meta.discourse.org/t/markdown-base62-image-name-vs-full-img-path/81653
**Category:** Support
**Created:** [February 27, 2018, 12:34pm UTC](https://meta.discourse.org/t/markdown-base62-image-name-vs-full-img-path/81653 "2018-02-27T12:34:40Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![filip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/filip/32/70415_2.png) [@filip](https://meta.discourse.org/u/filip)
#### Post date: [February 27, 2018, 12:34pm UTC](https://meta.discourse.org/t/markdown-base62-image-name-vs-full-img-path/81653/1 "2018-02-27T12:34:40Z")

</div>

Hi,

An image uploaded through pasting has a markdown tagged address :

```
![image|302x124](upload://
1UTkm8uk9wWYvKeuEgiTXMJIuTG.jpg)

```

which seems to use the shorter base62 filename [as discussed here.](https://meta.discourse.org/t/quick-image-resizing-and-markdown-image-dimensions/66812/34)

But, using the base62 in a direct link does not work. Should it?

```
https://forum.imade3d.com/uploads/default/original/1X/
1UTkm8uk9wWYvKeuEgiTXMJIuTG.jpg

```

The absolute image path still seems to be the old hex encoding, as this does work:

```
https://forum.imade3d.com/uploads/default/original/1X/
0d708ae22e111a1046c958d7049e31881cc21ca4.jpg

```

* * *

How can I reconcile the two? How does this work?  
Is there any setting to switch back to using the hex encoding in the md tags?

I like to cross-post images from my discourse forum on my website, and this makes it difficult to get the cross-postable URLs.

Thanks!

---

<div class="post-metadata">

### Author: ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [February 27, 2018, 1:05pm UTC](https://meta.discourse.org/t/markdown-base62-image-name-vs-full-img-path/81653/4 "2018-02-27T13:05:27Z")

</div>

> [@filip](#):
>
> But, using the base62 in a direct link does not work. Should it?

No, that’s currently not possible.

> [@filip](#):
>
> How does this work?  
> Is there any setting to switch back to using the hex encoding in the md tags?

The Markdown engine converts the short filename into an actual HTML link that points to the file. I’m sorry, it’s not possible to switch back to the previous behavior.

The easiest solution is to copy the URL of the image after posting.

---

<div class="post-metadata">

### Author: ![filip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/filip/32/70415_2.png) [@filip](https://meta.discourse.org/u/filip)
#### Post date: [February 27, 2018, 1:57pm UTC](https://meta.discourse.org/t/markdown-base62-image-name-vs-full-img-path/81653/5 "2018-02-27T13:57:24Z")

</div>

Blimey. 😿  
Thanks for the response.

This means that what was great is broken for me now, and I don’t see any easy solution. (Devoid of a lot of clicking.)

I like to host my images in discourse so that when I post on wordpress, and it links back to discourse via wp-discourse plugin, there’s no duplicate image storage.

If I figure something out, I’ll report.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [June 8, 2024, 12:37pm UTC](https://meta.discourse.org/t/markdown-base62-image-name-vs-full-img-path/81653/6 "2024-06-08T12:37:45Z")

</div>

This topic was automatically closed after 2293 days. New replies are no longer allowed.