Skip to main content

How to integrate IPFS with Ethereum

Updated on
Aug 18, 2023

9 min read


It can be costly to store massive files on a blockchain mainnet, and this is where decentralized file storing systems like IPFS can come in handy. Sometimes, NFTs use IPFS as well. In this guide, we’ll cover how we can integrate IPFS with Ethereum.

What is IPFS?

The web that we use today is mostly centralized; Even the data stored on the cloud is centralized and is controlled by giant cloud providers. Imagine if the servers of Wikipedia were to go down; this can leave us with a significant loss of knowledge. Centralization doesn’t seem to be a good thing, so why do we keep using it? That’s because we want our pages, images, and other content to load fast with very little latency and in high quality. While using a centralized server, content delivery speed can be regulated. Plus, there was no foolproof alternative until IPFS. IPFS (short for InterPlanetary File System) is a file storing and sharing system appropriate for the next generation of the Internet; Web3. IPFS is a versioned file system at its core, which can store files and track versions over time, much like git. IPFS also defines how a file moves over the network, making it a distributed file system. It is very flexible and works with several transport layer protocols like TCP, uTP, UDT, QUIC, TOR, and even Bluetooth.

How does IPFS work?

Whenever someone wants to download a file from the internet, the user has to query the exact address of the file, which is mostly the IP address of a remote server called location-based addressing. But what if the server is down? That person won’t get the file. There can be another user who has already downloaded a copy of that file before, but still, the computer wouldn’t be able to grab that from another user. To fix this problem, IPFS uses content-based addressing instead of location-based addressing. Instead of saying where to find the file, you just say what file is to be found.  Every file uploaded with IPFS is associated with a unique hash, so when someone wants to download the file, they can query the network for the file hash, and someone from the IPFS network will provide it to the user. IPFS has built-in security as the hash of the requested file and supplied/downloaded file can always be verified. Another benefit of using hashes is avoiding duplication. When multiple users try to upload the same file, it will only be accepted once, making the network very efficient. 

IPFS and Ethereum

Blockchains like Ethereum provide us with timestamping data, which makes tampering with that data almost impossible, but to store a file on Ethereum can be very expensive given the amount of processing the Ethereum blockchain has to do, whereas the content-based addresses that IPFS returns are 46 bytes in size which is a tiny amount considering the size of files. So it is cheaper to publish a file on IPFS and store their content-based address on the Ethereum blockchain. In the following example, we’ll publish an image to IPFS, store its hash in a smart contract, and retrieve/view that image using ethers.js and QuickNode.

Publishing a file on IPFS

Our first step here would be to install IPFS and publish our file to IPFS. You can download and install IPFS CLI  based on your Operating system by following the installation guide in IPFS docs, creating a project directory, and changing the directory.

Open your terminal/cmd and Initialize the IPFS repo.

$ ipfs init

Now, open another window for your terminal/cmd and start the IPFS daemon. This will act as your local IPFS node.

$ ipfs daemon

Move your desired image into the project directory(image.jpg here) and go back to the previous terminal/cmd window, and publish the image to IPFS using:

$ ipfs add image.jpg

On success upload, it must give an output similar to this.

Save the generated hash, as we’ll need it to retrieve the image in the later steps.


Getting test ETH

Now that we’ve published our file on IPFS, let’s store its hash on Ethereum using a smart contract.

We’ll deploy our contract on the Ropsten testnet. To get started, you will need the Metamask browser extension to create an ETH wallet and some test ETH, which you can get by going to the Ropsten faucet. You'll need to select Ropsten Test Network on your Metamask wallet and copy-paste the wallet address into the text field in the faucet, then click Send me test Ether.

Deploying our contract

Head over to the Ethereum Remix IDE and make a new Solidity file, for example - ipfs.sol

Paste the following code into your new Solidity script:

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.3;
contract IPFS {
string ipfsHash;

function sendHash(string memory x) public {
ipfsHash = x;

function getHash() public view returns (string memory) {
return ipfsHash;

Explanation of the code above: 

Line 1: Specifying SPDX license type, which is an addition after Solidity ^0.6.8. Whenever the source code of a smart contract is made available to the public, these licenses can help resolve/avoid copyright issues. If you do not wish to specify any license type, you can use a special value UNLICENSED or simply skip the whole comment (it won’t result in an error, just a warning).

Line 2: Declaring the solidity version.

Line 3: Starting our contract named IPFS.

Line 4: Declaring a var ipfsHash of type string to store our file’s hash.

Line 6-8: Declaring a function sendHash() of type public means it can be accessed from outside of this function by other contracts and programs. It takes a string x as input and stores the value of x to the ipfsHash variable.

Line 10-12: DEclaring a function getHash() also to type public and mutability view, which means it can only view, not modify the Ethereum blockchain’s state and returns the hash stored in the variable ipfsHash.

Compile the smart contract and deploy it using injected Web3 (make sure to select Ropsten testnet on Metamask before compiling the contract). Approve the transaction from metamask.

Locate your contract under the “Deployed Contracts” section in Remix, expand the deployed contract, and paste the hash (which we obtained in the above section after publishing our file to IPFS) in the input field near the sendHash button and click on sendHash; approve the transaction from Metamask.

Once the transaction is completed, our hash will be stored in the deployed contract. To verify, click on getHash, and it must output the hash of the file.

Copy and save the contract’s ABI from the compile tab and The contract’s address from the copy button under the deployed contract section. We'll need it later.

Learn more about ABI and how it’s generated in this guide on ABI.

Now, let’s see how we can retrieve the hash from the Ethereum blockchain and view the image using the hash.

Set Up Your QuickNode Ethereum Endpoint

To query the Ethereum blockchain, we will need access to an Ethereum node for that we could use pretty much any Ethereum client, such as Geth or OpenEthereum (fka Parity). Since that is a bit too involved to fetch a single hash from a contract, we'll just grab a free endpoint from QuickNode to make this easy. We’ll need a Ropsten endpoint to get data from the chain as we’ve deployed our contract on the Ropsten testnet. After you've created your free Ethereum endpoint, copy your HTTP Provider endpoint:

A screenshot of the Quicknode Ethereum endpoint Getting Started page with an HTTP link and WSS

You'll need this later, so copy it and save it.

Installing dependencies

We’ll use ethers.js to write a short script to interact with our deployed smart contract and access our image using IPFS gateway and hash. Then we’ll use a package called browserify to use our node.js script in the browser.

We’ll install ethers and browserify using npm (Node Package Manager), which comes with node.js; learn more about ethers.js in the guide on How to connect to Ethereum network with ethers.js. Open your terminal/cmd and run the following command.

$ npm i ethers

Now to install browserify and one of its dependency.

$ npm i browserify
$ npm i uniq

The most common issue at this step is an internal failure with `node-gyp`. You can follow node-gyp installation instructions here.

Note: You will need to have your python version match one of the compatible versions listed in the instructions above if you encounter the node-gyp issue. 

Another common issue is a stale cache; clear your npm cache by simply typing the below into your terminal:

$ npm cache clean

If everything goes right, ethers and browserify will be installed.

Viewing the file stored on IPFS

Step 1: ipfs.js and bundle.js

Create a js file in your project directory called ipfs.js and copy-paste the following in it:

var ethers = require('ethers');
var provider = new ethers.providers.JsonRpcProvider(url);
var abi = [
"inputs": [
"internalType": "string",
"name": "x",
"type": "string"
"name": "sendHash",
"outputs": [],
"stateMutability": "nonpayable",
"type": "function"
"inputs": [],
"name": "getHash",
"outputs": [
"internalType": "string",
"name": "",
"type": "string"
"stateMutability": "view",
"type": "function"
var contract = new ethers.Contract(address,abi,provider);

contract.getHash().then((result) =>{
document.getElementById("btn").onclick = function () {
location.href = ""+result;

Go ahead and replace `ADD_YOUR_ETHEREUM_NODE_URL` with the ropsten HTTP provider and `CONTRACT_ADDRESS_FROM_REMIX` with the address of the deployed contract from the above section.

Explanation of the code above:

Line 1: Importing the ethers library.

Line 2: Storing our Quicknode’s URL in the url variable.

Line 3: Instantiating new ethers.providers.JsonRpcProvider instance and storing it in provider.

Line 4: Storing the contract address in the address variable.

Line 5-32: Storing the ABI we got from the previous step in the abi variable.

Line 33:Initializing a contract instance in ethers and connecting to our deployed contract using the address,abi, and provider.

Line 35: Calling the getHash method of our contract, which returns the hash of the image stored in the contract.

Line 36-38: Creating onclick event listener on the ‘btn’ div of our HTML page, which we will create after this and adding our ipfs gateway with the hash as the hyperlink, so when the div is clicked, it will redirect to the image.

Now, save the file and use the browserify package to use the script above on our HTML page.

$ browserify ipfs.js -o bundle.js

Step 2: index.html

Following is a very basic index.html file that will help to view our image in the browser.

<!doctype html>

<html lang="en">
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>IPFS with Ethereum</title>
#btn {
position: absolute;
top: 50%;
left: 50%;
margin: -100px 0 0 -150px;
font-size: 400%;
font-family: serif;
text-decoration: underline;
text-decoration-style: double;
color: #65b7ff;
cursor: pointer;

background-color: #ffedf3;

<div id="btn">View Nyan</div>

<script src="bundle.js"></script>

Explanation of the code above.

Line 1-7: Necessary basic HTML tags.

Line 8: Giving a title to our HTML page.

Line 9-26: Some CSS to make the webpage look a bit presentable.

Line 30: Creating a Div with id btn and adding View Nyan text to it.

Line 32: Adding our bundle.js file from the previous step to our HTML page.

Now, open the index.html file in your web browser, and If you used the above CSS. It must look something like this:

Click on View Nyan, and it will take you to the original Image which we published on IPFS.


So now that you know how to integrate IPFS and Ethereum, you can do cool projects like document versioning, verification systems, and more.

Subscribe to our newsletter for more articles and guides on Ethereum. If you have any feedback, feel free to reach out to us via Twitter. You can always chat with us on our Discord community server, featuring some of the coolest developers you’ll ever meet :)

Share this guide