English
English
Appearance
English
English
Appearance
How files persist on the IPFS network and why pinning matters.
IPFS nodes have limited storage. To manage disk space, they periodically run garbage collection — a process that removes cached data that hasn't been explicitly marked as important. Without intervention, a file you uploaded could be cleared from the network within hours.
Pinning tells an IPFS node: "keep this file permanently — don't garbage-collect it." A pinned file stays on the node's storage indefinitely, ensuring it remains available on the network.
Local pinning means running your own IPFS node and pinning files to it. You're responsible for uptime, storage, and network connectivity. If your node goes offline, your files become unavailable.
Remote pinning (what IPFS.NINJA provides) means a managed service pins your files on infrastructure that's always online. You get the permanence of pinning without running your own node.
TIP
Every file uploaded through IPFS.NINJA is automatically pinned to our IPFS cluster. No additional steps needed — your files are persistent from the moment of upload.
If you delete a file from your IPFS.NINJA account, we unpin it from our nodes. The file may still be accessible if:
Over time, without any node pinning the CID, the file will be garbage-collected from the network entirely.
You don't have to upload a file through IPFS.NINJA to pin it. If content already exists on the IPFS network — uploaded by someone else, or by you through another service — you can pin it to your account by providing its CID.
When you pin an existing CID, our cluster:
This is useful for:
See the Pinning API docs for endpoint details.