# 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:** 1\
**Showing post:** 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!

---

_[View the full topic](https://meta.discourse.org/t/markdown-base62-image-name-vs-full-img-path/81653)._