# Connecting your DApp to IPFS
**URL:** https://forum.algorand.co/t/connecting-your-dapp-to-ipfs/2197
**Category:** Uncategorized
**Created:** [November 12, 2020, 9:53pm UTC](https://forum.algorand.co/t/connecting-your-dapp-to-ipfs/2197 "2020-11-12T21:53:31Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@ryanRfox](https://forum.algorand.co/u/ryanRfox)
#### Post date: [November 12, 2020, 9:53pm UTC](https://forum.algorand.co/t/connecting-your-dapp-to-ipfs/2197/1 "2020-11-12T21:53:31Z")
Does your DApp need to store arbitrarily large files? This solution explains [integrating IPFS with Algorand](https://developer.algorand.org/solutions/securely-share-files-algorand-ipfs/) so your DApp may gain access to this decentralized storage network.
Let us know how your DApp is making use of IPFS in the thread below.
---
### Author:  [@emg110](https://forum.algorand.co/u/emg110)
#### Post date: [August 28, 2021, 10:21am UTC](https://forum.algorand.co/t/connecting-your-dapp-to-ipfs/2197/2 "2021-08-28T10:21:52Z")
Hi Ryan, how about converting IPFS CID to 32 bytes strings that fit 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).
---
### Author:  [@Albatros](https://forum.algorand.co/u/Albatros)
#### Post date: [January 13, 2024, 11:24pm UTC](https://forum.algorand.co/t/connecting-your-dapp-to-ipfs/2197/3 "2024-01-13T23:24:14Z")
Hello I like this so much