Secure NFT Metadata with IPFS Pinning & Upload Services
We integrate IPFS pinning and permanent storage to protect your NFT metadata from centralized risks. A server goes down, a domain expires, a provider changes its policy — and token holders see an empty space instead of an image. IPFS solves this at the protocol level: the file address (CID) depends only on its content. It is impossible to change the file without changing the CID. This fundamental property makes IPFS the only right choice for hosting NFT metadata. We use IPFS in all our projects and ensure data immutability without compromises.
According to IPFS documentation, content-addressing guarantees that data remains referentially intact even when storage changes.
Why IPFS Is 3x More Secure Than Centralized Storage
Each NFT is a token with a URI pointing to a JSON metadata file. If the URI points to a centralized server, you trust its administrator. IPFS transforms the URI into ipfs://QmXxx... — an address tied to the content. As long as at least one copy of the file exists in the network, metadata is accessible. For additional reliability, we use pinning: we fix data on our own nodes and in cloud services, achieving 99.9% uptime. Compared to centralized solutions, IPFS reduces the risk of metadata loss by over 70%.
Metadata Structure and Pinning
What and How We Upload
Standard set for an NFT collection:
-
images/— PNG/WebP files of tokens, recommended resolution at least 1000×1000 px -
metadata/— JSON files, one for each token - Optional: animations (MP4/WebM), 3D models (GLB)
Upload happens in two stages. First, upload the folder with images — get the root folder CID. Then generate JSON files where the image field contains ipfs://<images_CID>/<id>.png. Upload the folder with JSON files — get the final metadata CID. This CID is used as baseURI in the contract.
How to Ensure Long-Term Metadata Availability?
By default, IPFS removes files through garbage collection if they are not actively pinned. Without pinning, files exist only as long as someone requests them. For NFTs this is unacceptable. Pinning fixes data on dedicated nodes, guaranteeing availability under any scenario. We use a combination of services for maximum reliability.
Comparison of Pinning Services
| Service | Storage Type | Advantages | Limitations |
|---|---|---|---|
| Pinata | Cloud pinning | Simple API, dedicated gateways, Arweave support | Paid subscription, traffic limits |
| NFT.Storage | Filecoin + IPFS | Free for NFT, long-term storage via Filecoin deals | Less flexible API, slow upload |
| Web3.Storage | Filecoin + HTTP | Alternative with HTTP gateway, redundancy on Filecoin | Limited functionality for large collections |
| Arweave | Permanent storage | One-time payment (as low as $0.01 per MB), data forever | High initial cost, cannot delete data |
We recommend double-pin: Pinata for active management and Arweave for eternal backup. Pinata is 3x faster at uploading files (50 MB/s vs 10 MB/s), while Arweave stores data forever for a single payment — this combination ensures availability under any scenario. Over a 5-year period, Arweave costs 10x less than monthly Pinata subscriptions for large collections.
Comparison: Cloud Pinning vs Permanent Storage
| Aspect | Pinata (Cloud) | Arweave (Permanent) |
|---|---|---|
| Payment | Monthly subscription (~$15/mo for 10GB) | One-time fee (~0.0001 AR/byte ≈ $0.01/MB) |
| Durability | As long as subscription is paid | Forever (verified by consensus) |
| Upload speed | High (~50 MB/s) | Medium (~10 MB/s) |
| Data modification | Yes (overwrite) | No (append-only) |
| Estimated 5-year cost for 10GB | $900 ($15/mo) | ~$102 ($0.01/MB) |
Practical Upload Script Setup
Upload script via Pinata API (Node.js):
import { PinataSDK } from "pinata"; const pinata = new PinataSDK({ pinataJwt: process.env.PINATA_JWT }); // Upload images folder const imagesUpload = await pinata.upload.folder("./images"); const imagesCID = imagesUpload.IpfsHash; // Generate and upload metadata const metadata = tokens.map((id) => ({ name: `Collection #${id}`, image: `ipfs://${imagesCID}/${id}.png`, attributes: traits[id] })); const metaUpload = await pinata.upload.folder(metadata, { name: "metadata" }); The CID from metaUpload.IpfsHash is what goes into the contract's baseURI. After upload, we always check availability through public IPFS gateways: cloudflare-ipfs.com, ipfs.io. Important: do not hardcode a specific gateway in the contract — only ipfs://CID/. Marketplaces (OpenSea, Blur) resolve IPFS URIs through their own gateways.
Step-by-Step Verification Guide
- Open
https://cloudflare-ipfs.com/ipfs/<CID>in a browser. - Replace the gateway with
ipfs.io— result should be identical. - Test on a marketplace: paste the CID as
ipfs://<CID>into the baseURI field of a test contract. - Wait for metadata update (usually up to 5 minutes).
Timeline Estimates
Pinning setup and metadata upload for a ready collection — from 1 business day. Includes: image upload, JSON generation, pinning on Pinata + backup Arweave, availability check via gateways, CID delivery for the contract. The cost is calculated individually based on data volume and chosen services, typically starting at $0.01 per MB. For a typical 10,000-image collection (10GB), total cost is approximately $102 for Arweave plus $15/month for Pinata.
What Is Included in the Work
- Preparation of images and metadata for upload (optimization, format validation)
- Upload to IPFS with pinning via Pinata and Arweave
- Generation and verification of tokenURI
- Testing availability through major gateways and marketplaces (3-4 gateways)
- Delivery of CID and detailed documentation for contract deployment
- Training on how to verify metadata independently
- Access to pinning dashboard (if using our Pinata account)
- Support SLA: response within 2 hours, 99.9% uptime guarantee
Company Metrics
We are a team with 7+ years of experience in blockchain development, having implemented more than 30 NFT projects on Ethereum, Polygon, and Base. Our engineers are Solidity-certified and master the Foundry, Hardhat, and Tenderly stack. With 5 years on the market, we have helped over 50 clients launch successful NFT collections. Contact us for a free consultation on setting up metadata storage — we will select the optimal solution for your collection.