Nifty Gateway Closure Leaves NFT Owners to Pay Storage Costs

Nifty Gateway, a marketplace owned by Gemini, closed in January and provided an exit plan that included a bulk withdrawal tool and a promised migration of metadata and media to Arweave. The company extended its withdrawal window to April 23 and stated it would continue hosting some legacy metadata. Some files remained hosted on Nifty Gateway’s own servers and migration outcomes are not fully known.

Most Ethereum NFTs use the ERC-721 standard to record who owns a token on the blockchain while pointing to metadata stored off-chain. That metadata typically contains a link to an image or video file. Wallets combine the token record, the metadata and the linked media to display an NFT. Transferring a token changes only the blockchain record; it does not move the media file, take over the server that hosts it, or pay for ongoing storage.

Distributed storage systems are used as alternatives but require active retention. The InterPlanetary File System (IPFS) locates content by its data rather than by a web address, allowing multiple computers to serve the same file. IPFS nodes can delete cached content unless someone “pins” the file to force retention. Pinning can be done by a collector running a node, by a paid pinning service, or by another provider, and it requires whoever pins the file to cover ongoing costs.

Gateways that fetch IPFS content can fail even when files still exist elsewhere, so a missing image may indicate a gateway problem rather than permanent loss. If no node retains the data at all, no gateway can restore it. Other approaches include storing media directly on a blockchain or using networks such as Arweave that fund longer-term storage through up-front payments. Each model shifts the source of risk to different systems: a single company’s servers, a blockchain’s continued operation, or the economic incentives that keep storage providers running.

The financial model for many NFT projects has created a timing gap between one-time sales and ongoing care. Selling an NFT generates immediate revenue, while preserving the associated media requires continuous tasks: storing files, checking that they remain accessible, updating software, and planning for successors when a provider stops operating. Responsibility for those tasks falls to marketplaces, collectors, artists or third-party custodians depending on how a project is built.

Conservators and technical staff raised similar concerns as the market expanded. Preserving a still image generally involves copying and storing the file, while interactive or installation pieces can require recreating software environments and documenting how components interact. Past restorations of artworks built on obsolete systems have required rebuilding the environments that make them run.

Collectors who want visible artwork over the long term can run their own nodes, pay pinning services, store media on long-term networks, or keep local copies of files. Making duplicate copies does not transfer ownership of a token, but copies can preserve the visual element if the original host disappears. Artists and collectors who manage archival work take on the technical and financial duties that hosting services previously handled.