# Asset URL max length (how to link IPFS)

**URL:** <https://forum.algorand.co/t/asset-url-max-length-how-to-link-ipfs/3054>\
**Category:** General\
**Tags:** asa\
**Created:** [April 19, 2021, 4:52pm UTC](https://forum.algorand.co/t/asset-url-max-length-how-to-link-ipfs/3054 "2021-04-19T16:52:02Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![jannotti](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/jannotti/32/688_2.png) [@jannotti](https://forum.algorand.co/u/jannotti)\
**Post date:** [May 12, 2021, 12:59am UTC](https://forum.algorand.co/t/asset-url-max-length-how-to-link-ipfs/3054/9 "2021-05-12T00:59:59Z")

</div>

You could weigh in here: [TEAL 4 Epic · Issue #1950 · algorand/go-algorand · GitHub](https://github.com/algorand/go-algorand/issues/1950)

But honestly, there isn’t a lot of nuance to this particular conversation - I think everyone has come to realize that 32 bytes is too small. The current intention is to expand the limit to 96 bytes. That seems to allow a bit of breathing room beyond the hashes that are commonly used on ipfs.

---

_[View the full topic](https://forum.algorand.co/t/asset-url-max-length-how-to-link-ipfs/3054)._