Back

Blog details

AIOZ Pin Free Pins: 40,000 Files, Then $0.10 per 1,000

AIOZ Network
4 min readAugust 08, 2026
aioz-pinpricingexplainer
AIOZ Pin header image reading First 40,000 Pins Free, Then $0.10 per 1,000

AIOZ Pin pins your first 40,000 files free. After that, each extra 1,000 pinned files costs $0.10, and there is no cap on how many you can pin. A 100,000-file NFT collection adds about $6. Storage and bandwidth, not pin count, drive most of your bill.

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 Does "Unlimited Pinned Files" Mean on AIOZ Pin?

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.

How Much Do Extra Pins Cost?

$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 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 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 Drives Your AIOZ Pin Bill Instead?

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 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.

References

We only send updates when meaningful changes ship, and you can unsubscribe anytime

Related Content

blog thumbnail

ERC-1155 Metadata on IPFS: The ID Substitution Rule

ERC-1155 metadata on IPFS breaks when filenames ignore the {id} rule. Here is the exact 64-character format, a working folder layout, and the per-token option.

6 min readOctober 21, 2026
blog thumbnail

AIOZ Pin Rate Limits: API, Public, and Premium Gateways

AIOZ Pin rate limits in one place: 180 requests per minute for the API, 15 per CID on the public gateway, and no predefined limit on premium gateways.

6 min readOctober 19, 2026
blog thumbnail

IPFS Pin Stuck on Pinning? What Each Pin Status Means

IPFS pin stuck on Pinning? Here is what Pinning, Pinned, and Failed mean on AIOZ Pin, why big directories can sit there, and how to read a pin's real state.

6 min readOctober 16, 2026
blog thumbnail

Why IPFS Used to Give You Different CIDs for the Same File

Two identical files, three IPFS tools, three different CIDs. Here is why that happened for years, and how IPIP-0499 made content addressing deterministic.

5 min readOctober 14, 2026
blog thumbnail

AIOZ Pin MCP Server Setup: llms.txt and 11 Tools Guide

AIOZ Pin MCP server setup has two paths: llms.txt lets a super intelligence assistant read the API, the MCP server lets it call 11 tools. Here is each one.

6 min readOctober 12, 2026
blog thumbnail

AIOZ Pin Pricing: The Complete Cost Breakdown

AIOZ Pin bills three flat rates against a token wallet, with no tiers to pick between. Here is what storage, bandwidth and pinned files cost, with examples.

5 min readOctober 09, 2026