# Arc-19 url ipfs + pinata vs ipfs + arweave

**URL:** <https://forum.algorand.co/t/arc-19-url-ipfs-pinata-vs-ipfs-arweave/7738>\
**Category:** ARCs\
**Tags:** asa\
**Created:** [August 29, 2022, 10:23pm UTC](https://forum.algorand.co/t/arc-19-url-ipfs-pinata-vs-ipfs-arweave/7738 "2022-08-29T22:23:48Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![StephaneBarroso](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/stephanebarroso/32/3186_2.png) [@StephaneBarroso](https://forum.algorand.co/u/StephaneBarroso)\
**Post date:** [August 30, 2022, 1:12pm UTC](https://forum.algorand.co/t/arc-19-url-ipfs-pinata-vs-ipfs-arweave/7738/3 "2022-08-30T13:12:08Z")

</div>

Hey,

I am with Patrick on this.  
For me, the best way is to create a new ARC referencing the ARC-19

You will need to explain why use Arweave instead of ipfs, and add something like this:

`template-ipfsarweave://{ipfscid:<version>:<multicodec>:<field name containing 32-byte digest, ie reserve>:<hash type>}`

It is an idea worth pursuing.

---

_[View the full topic](https://forum.algorand.co/t/arc-19-url-ipfs-pinata-vs-ipfs-arweave/7738)._