Why AIOZ Pin's 'Unlimited Pinned Files' Isn't Really Free
"Unlimited pinned files" shows up in marketing copy across the IPFS pinning space, AIOZ Pin included, and it's technically accurate in a narrow sense: there's no hard cap on how many files you can pin. What it doesn't tell you is what happens to your bill once you cross a threshold, and that threshold is real, specific, and worth knowing before you plan a large collection around the word "unlimited." This article covers exactly where the free allowance ends on AIOZ Pin and how that compares to what "unlimited" means at two competitors making the same claim.
TL;DR:
- AIOZ Pin's first 40,000 pinned files are free, then $0.10 per additional 1,000
- "Unlimited" means no hard technical ceiling, not that pinning itself is free forever
- Pinata and Filebase both removed hard pin-count caps too, but describe the same underlying reality differently
What "Unlimited" Actually Means Here
On AIOZ Pin, per its own payment documentation, the first 40,000 pinned files are free. After that, each additional 1,000 pins costs $0.10. There is no point at which the system refuses to pin more files, which is the literal claim "unlimited" is making, but it stops being free well before most people would assume "unlimited" implies. The How AIOZ Pin Billing Works breakdown covers this alongside storage and bandwidth; this article focuses specifically on the pin-count piece, since it's the one most likely to get misread from marketing copy alone.
Running the Actual Math
$0.10 per 1,000 additional pins works out to $0.0001 per file past the free threshold, cheap on a per-file basis, but worth seeing at real collection sizes. A 10,000-item NFT collection stays entirely within the free 40,000-file allowance, no pin-count charge at all. A 100,000-item collection crosses the threshold by 60,000 files, adding $6 to your bill. Even a 500,000-file archive only adds $46 in pin-count charges beyond the free tier. For nearly every real project, pin count is the smallest line item on an AIOZ Pin bill, storage and bandwidth dominate the cost well before pin count does, which is worth knowing so you don't over-plan around a cost that's rarely the actual constraint.
Why Pin Count Is Billed Separately From Storage At All
It's worth asking why AIOZ Pin tracks pin count as its own line item instead of folding it into storage cost the way file size already is. The two dimensions genuinely measure different things: storage cost scales with bytes, a single 5GB video costs the same to store as five thousand 1MB thumbnails at the same total size, but that single video is one pin, while the five thousand thumbnails are five thousand separate records the pinning layer has to track, list, and serve individually. A large NFT collection is the clearest case where this distinction actually matters: the total data volume might be modest, but the pin count is high, thousands of small asset-and-metadata pairs rather than a few large files. Billing pin count separately is what lets AIOZ Pin's storage pricing stay purely byte-based while still accounting for the real operational cost of tracking a large number of individually addressable pins.
How Competitors Describe the Same Reality
Pinata's own blog announced removing hard pin-count caps on its paid plans, moving to usage-based pricing instead, similar in spirit to AIOZ Pin's model, no wall you hit, but usage still costs money past what's included. Filebase goes further on its Pro plan specifically, listing "Unlimited" pinned files with no stated additional per-pin charge at all, different from AIOZ Pin's $0.10-per-1,000 structure past 40,000. The word "unlimited" is doing different work in each case: for AIOZ Pin it means no hard cap but a real marginal cost, for Filebase's Pro plan it appears to mean no additional charge tied to file count specifically, separate from the storage volume you're still paying for regardless of pin count.
Checking Your Own Pin Count Before It Surprises You
Rather than estimating where a project sits relative to the 40,000-file threshold, the actual count is one call away. From the Node.js SDK, getPinList() returns your pins with pagination, and the response's total count is the number that matters here. From the CLI, pinning list-pins --limit=1 returns a response that includes the same total alongside a single result, cheaper than pulling every record just to count them. Checking this once before a large batch upload, an NFT collection mint, a bulk migration from another provider, tells you exactly how much of the free allowance is left, rather than finding out after the fact from a bill that includes a pin-count line item you didn't expect.
What Actually Constrains You
Since pin count rarely drives the bill, storage and bandwidth are what to model out before committing to a provider. If you're mainly asking "will I run out of pins," the honest answer on AIOZ Pin is no, and the cost of going over is small enough not to be the deciding factor. The real planning question is closer to "how much data am I storing and serving," which the AIOZ Pin vs Pinata comparison works through with real numbers at different usage levels.
Frequently Asked Questions
Does AIOZ Pin actually have unlimited pinned files? There's no hard technical cap, so in that sense yes, but it's not free past the first 40,000 files. Additional pins cost $0.10 per 1,000.
How much would a 100,000-file NFT collection cost in pin charges on AIOZ Pin? About $6, since the first 40,000 files are free and the remaining 60,000 cost $0.10 per additional 1,000.
Is pin count usually the biggest cost on AIOZ Pin? No. Storage and bandwidth, both billed at $20 per TB, dominate the bill for almost any real project. Pin-count charges are typically a small fraction of total cost, if they apply at all.
Do other pinning services also claim unlimited pinned files? Yes. Pinata removed hard pin-count caps on its paid plans, and Filebase advertises unlimited pinned files on its Pro plan, though the underlying cost structure differs between providers.
At what point does AIOZ Pin start charging for pinned files? Past the first 40,000 pinned files. Below that threshold, pin count adds nothing to your bill regardless of how many files you pin.
Related Reading
- How AIOZ Pin Billing Works: Storage, Bandwidth, Pins - the full billing picture this pin-count detail fits into
- AIOZ Pin vs Pinata: IPFS Pinning Service Compared 2026 - a real cost comparison where storage and bandwidth, not pin count, decide the outcome
- Best NFT.storage Alternatives in 2026 (Featuring AIOZ Pin) - practical context for NFT collections weighing pinned-file limits across providers
References
Related Content
How IPFS Splits Files: Fixed vs. Content-Defined Chunking
IPFS defaults to 256 KiB fixed-size chunks, but also ships Rabin and Buzhash content-defined chunkers. Here is why the choice affects deduplication.
Anatomy of a CID: Decoding an IPFS Identifier
An IPFS CID is not a random string. It encodes a version, a codec, and a hash algorithm plus digest. Here is how to decode a real CID piece by piece.
How IPFS Shards Large Directories: The HAMT, Not a B-Tree
IPFS does not use a B-tree for large directories. It uses a HAMT, a Hash Array Mapped Trie. Here is exactly how it shards a folder once it outgrows one block.
How to Resize Images on AIOZ Pin Using URL Parameters
AIOZ Pin image resizing happens straight in the gateway URL, no upload step or separate service. Here is every img- parameter, with real srcset examples.
How x402 Payments Weight AI Agent Reputation on ERC-8004
x402 payments let ERC-8004 weight a paid AI agent interaction more heavily than free work in its reputation score. Here is exactly how that link works.
How to Automate NFT Pinning with the AIOZ Pin NFT API
AIOZ Pin NFT API calls pin an asset and its metadata as two tracked pins under one record. Here is how to automate it directly over REST, no SDK needed.