Move your pinned IPFS data to Filecoin

Same CIDs, a fraction of what pinning services charge, and an onchain receipt you can verify yourself.

Give this line to Claude Code, Cursor, or any coding agent. It reads the runbook, works through your list, and reports back what landed. The first thing it will ask you for is the list of CIDs to migrate, so have one ready or paste yours into the checker and copy the prompt it builds with your CIDs already in it.

Migrate my IPFS data to Filecoin: read https://filecoin.cloud/ipfs2filecoin/migrate.md and follow it.

It signs from a key you provide and can spend up to your deposit, so use a wallet kept for this migration and nothing else.

How it works

Four steps, and the first two are free.

  1. Hand over the list

    Paste a list here to see what you are dealing with, or let your agent pull it straight from your pinning service, whose dashboard and API list every pinned CID. Checking costs nothing.

  2. Read and measure

    Each CID is fetched from a public gateway and its Filecoin piece identifier computed. Nothing is uploaded anywhere and nothing is charged.

  3. Fund it, once

    Deposit USDFC and approve spending, from a wallet you keep for this migration. Deposit what the run needs, because that amount is also the most anything can spend.

  4. Migrate

    Your machine streams the data straight to two storage providers, and the adds are committed onchain in batches. You get explorer links and a summary of everything that landed.

Why move to Filecoin warm storage

Your data keeps working the way it does today. What changes is the price, the proof, and who owns it.

  • Your CIDs do not change

    Nothing is re-chunked. Every CID stays byte-identical and keeps resolving from any public IPFS gateway, so existing links, IPNS names, and NFT metadata keep working exactly as they do today.

  • A fraction of pinning-service pricing

    $2.50 per TiB per month per copy, two copies by default. You pay storage providers directly, streamed per epoch, with no plan tiers and no minimum commitment.

  • Proof, not a dashboard

    Storage providers prove possession onchain on a schedule. You get a receipt with transaction links, and you can verify any piece yourself at any time without asking anyone.

  • Your wallet owns it, not an account

    No signup and no vendor account to lose. The data set belongs to your wallet address and payment streams from your wallet straight to the providers. Reading your data never depends on your key, so the content stays reachable either way.

What it costs

Pinning services bundle an allowance into a monthly plan, then charge per gigabyte past it. Once you are past the allowance, which anyone migrating a real archive already is, the overage rate is your real cost.

One per line. Gateway URLs are fine, the prefix is stripped. Only the count is measured, never the list.

  • Free, no wallet required
  • No list-size limit
  • 1016 MiB per item
  • Runs in your browser
  • Never sent anywhere

  • Filecoin Warm Storage

    2 copies included

    Storage, per TB per month
    $4.55
    Egress
    Read by CID from any IPFS gateway

  • Filebase

    Pro plan overage

    Storage, per TB per month
    $15.00
    Egress
    $0.015 / GB

  • Pinata

    Fiesta plan overage

    Storage, per TB per month
    $35.00
    Egress
    $0.080 / GB

  • Pinata

    Picnic plan overage

    Storage, per TB per month
    $70.00
    Egress
    $0.100 / GB

Filecoin Warm Storage is $2.50 per TiB per month per copy at two copies. Other rates are the published list overage rates from Filebase and Pinata. Filecoin includes two replicas; the other services do not publish a replication factor, so the comparison is conservative.

Estimate your deposit

Storage is prepaid for a period rather than billed monthly. Enter roughly how much you hold and for how long; it runs in your browser.

Total across everything you are storing, not per CID. 1 TiB is 1,024 GiB, and 1 GiB is 1,024 MiB.

Based on $2.50 per TiB per month per copy, plus a flat $0.024 per data set per month, across 2 copies. Gas is separate, so you also need a small amount of FIL. A deposit funds a rate rather than a term: storing more data later spends the balance faster and moves your funded-until date earlier. The exact deposit is shown before you approve it.

Nobody should migrate an archive by clicking

Real migrations run unattended, so that is the path this is built around. Check a list for free, get your account funded in one pass, then hand the work to your agent or to us.

Ask your agent to do it

Give this line to Claude Code, Cursor, or any coding agent. It reads the runbook at /ipfs2filecoin/migrate.md, works through your list, and reports back what landed.

Migrate my IPFS data to Filecoin: read https://filecoin.cloud/ipfs2filecoin/migrate.md and follow it.

It signs from a key you provide, and a key that can sign on your account can draw against its balance, so your deposit is the ceiling. Use a wallet you keep for this purpose, holding what this migration needs and nothing else. Never give a main wallet's key to something running unattended.

Talk to us

For sources that are not reachable from the public IPFS network, or to agree capacity and timing before a run over 500 GiB. That is coordination, not a ceiling: the agent path has no cap on how many CIDs it migrates.

Tell us about your data

What this does not do

The things worth knowing up front, so nothing surprises you halfway through a run.

Your source has to be publicly readable
Each CID has to be retrievable from the public IPFS network; the migration fetches it through a public gateway that serves verifiable content. Private pinning accounts, authenticated endpoints, and custom storage are not reachable this way, so those go through the contact form.
1016 MiB per item
Individual assets larger than 1016 MiB cannot be moved yet, because splitting them would change their CID and that is the one thing we will not do. Large sets of small items are fine.
Past 500 GiB, talk to us first
Not a ceiling: there is no cap on how many CIDs an agent or the command line can migrate. But a run that size is worth agreeing with storage providers up front, so capacity and timing are arranged before you start rather than discovered partway through.
Filecoin uses its own identifier underneath
Filecoin tracks storage under its own piece identifier. You never need it to read your data, because retrieval is always by your original CID, and what the run hands you is the data set ids and the transaction links to verify onchain.
Unreachable CIDs are reported, not hidden
If a CID cannot be fetched from any gateway you provided, the run names them and counts them, and they stay recorded so a later run can retry them. A count you can act on beats a silent partial success.

Frequently asked questions

Find out what your archive costs before you move it

Checking is free and needs nothing but a list. You get a real number and the one line that hands the job to your agent.

Check my list freeTalk to us instead