# Storing metadata hash of length more than 32

**URL:** <https://forum.algorand.co/t/storing-metadata-hash-of-length-more-than-32/1633>\
**Category:** General\
**Created:** [May 9, 2020, 12:06pm UTC](https://forum.algorand.co/t/storing-metadata-hash-of-length-more-than-32/1633 "2020-05-09T12:06:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![emg110](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/emg110/32/3996_2.png) [@emg110](https://forum.algorand.co/u/emg110)\
**Post date:** [August 28, 2021, 10:28am UTC](https://forum.algorand.co/t/storing-metadata-hash-of-length-more-than-32/1633/3 "2021-08-28T10:28:09Z")

</div>

Another way without using note field which belongs to transaction context, would be converting IPFS CID to 32 bytes strings that fits both metadatahash and url fields (although on 2.7.1 URL is extended to 96 bytes).  
[ipfs2bytes32 GitHub repository](https://github.com/emg110/ipfs2bytes32)  
[ONLINE DEMO](https://emg110.github.io/ipfs2bytes32/)

In more complex scenarios URL (96 bytes since 2.7.1) can hold ASA service endpoints which are actually URls and metadatahash field can hold onto IPFS CID (which can be converted to 32 bytes and fits now).

---

_[View the full topic](https://forum.algorand.co/t/storing-metadata-hash-of-length-more-than-32/1633)._