All posts

NFT marketplace development in 2026: how to build one, what it costs

How to build an NFT marketplace in 2026: marketplace types, Seaport vs custom contracts, royalties and ERC-721C, indexing, lazy minting, payments, compliance, cost and timeline.

By , CEO & Founder at 23studio

Published 11 min read

NFT marketplace development in 2026: how to build one, what it costs

NFT marketplace development in 2026 means building four things: order and settlement contracts (usually on top of Seaport rather than from scratch), an indexer that tracks every listing and transfer, a frontend with wallet and card payments, and an admin layer for curation and compliance. A focused MVP for one niche typically costs $40,000 to $120,000 and takes 8 to 14 weeks, audit included.

This post covers which type of marketplace still makes sense, how the contracts work, how royalties are enforced today, the indexing and payment stack, compliance, and a cost and timeline table by scope. We start with the uncomfortable part: the market.

Is it still worth building an NFT marketplace?

Only if you pick a niche with real buyers. Generic "trade any NFT" marketplaces are a bad bet in 2026, and the numbers show why.

Demand moved to marketplaces where the NFT is a receipt for something people already want. Tokenized trading cards are the clearest case. Courtyard, which vaults physical cards and issues an NFT per card on Polygon, did over $78 million in volume in August 2025, and Collector Crypt on Solana reported about $1.3 billion in cumulative volume by June 2026. Buyers there care about the card, the grading and the redemption. The chain is plumbing.

So the question to answer before writing code is: what does a buyer get, and why would they buy it on your marketplace instead of OpenSea?

Types of NFT marketplaces

TypeExamples of what's tradedWhat makes it hardWho should build it
Open marketplaceAny collection on a chainLiquidity, aggregation, spam, wash tradingAlmost nobody in 2026
Curated or creator platformArt drops, editions, musicCuration, primary sales, creator toolingBrands, communities, art platforms
RWA and collectiblesVaulted cards, watches, wine, certificatesCustody, redemption, KYC, insuranceCompanies that already handle the physical asset
Ticketing and accessEvent tickets, membershipsResale caps, scanning at the door, fiat checkoutPromoters, venues, ticketing companies
In-game itemsSkins, characters, landGame integration, anti-bot, item economyGame studios (see blockchain game development)

The last three have something in common: the marketplace is part of a product people use for other reasons. That is where we'd put money. If you want the background on what an NFT does and doesn't give a holder legally, read NFTs in Web3: digital property, marketplace contracts, RWAs first.

How to build an NFT marketplace, step by step

  1. Pick the niche and the asset model. What is tokenized, who issues it, can it be redeemed, are resales allowed and at what price.
  2. Pick the chain. For EVM, Base, Polygon and Ethereum mainnet are the usual choices. Solana has its own standards and tooling. Gas per trade and where your buyers already hold funds matter more than throughput claims.
  3. Design the contracts. Token contracts (ERC-721 or ERC-1155), the exchange protocol, royalty policy and any escrow or redemption logic.
  4. Build the indexer. Listings, sales, transfers, ownership and metadata in a database your frontend can query.
  5. Build the frontend and checkout. Wallet connection or embedded wallets, card payments, listing and offer flows.
  6. Add admin and compliance tooling. Curation, takedowns, KYC where needed, sanctions screening, reporting.
  7. Test, audit, launch on a testnet, then mainnet. Run a closed beta with real sellers before opening up.

The rest of the post goes through the parts where teams get stuck.

Smart contracts: Seaport vs a custom exchange

A marketplace needs an exchange contract that matches a seller's signed order with a buyer's payment and moves the NFT and the money atomically. You have two options.

Build on Seaport. Seaport is OpenSea's open-source order protocol. Sellers sign orders off-chain (EIP-712), you store them in your backend, and the buyer submits the order to the Seaport contract, which is already deployed and audited on major EVM chains. It supports listings, offers, collection-wide bids, bundles, partial fills for ERC-1155, and split fees. Seaport 1.6 added hooks: zone, contract and item hooks that let your own contract run checks or logic when an order is fulfilled. OpenSea still calls hooks experimental, so test them hard.

Your marketplace becomes a "zone" with its own fee recipient, order book and rules. You can restrict fulfilment to your frontend, require KYC for certain collections, or add allowlists through a zone contract.

Write a custom exchange. It makes sense when the trade isn't a plain swap: redemption of physical items, price caps on ticket resales, auctions with unusual rules, or in-game items that must check game state. It's also common on non-EVM chains.

Our default: start with Seaport plus a thin zone contract, and only write custom settlement for the logic Seaport can't express. Every custom line of exchange code is audit scope, and an exchange holds approvals over every user's NFTs, so a bug there is the worst kind of bug.

Auctions

English auctions (rising bids, fixed end) are usually off-chain bids with on-chain settlement. Seaport handles them as offers the seller accepts. Fully on-chain auctions with escrowed bids cost more gas and need extra care: refunds that can be blocked by a malicious bidder, last-second sniping (add time extensions), and reserve prices.

Royalties in 2026: what actually gets enforced

EIP-2981 only lets a contract report a royalty amount. Paying it is up to the marketplace, and after the 2022 to 2023 royalty wars most venues made royalties optional.

Enforcement now comes from the token side. ERC-721C, from Limit Break, makes the NFT contract check every transfer against a validator. Transfers through operators that are not on the creator's allowlist revert. OpenSea supports ERC-721C enforcement since April 2024. When a creator turns it on, sales of that collection are limited to OpenSea and marketplaces built on Limit Break's Payment Processor.

What that means for you:

  • If your marketplace issues its own collections, you can deploy them as ERC-721C and allowlist your exchange, so royalties or resale rules hold everywhere the token can trade.
  • If you want to list other people's ERC-721C collections, your exchange must be on their allowlist, or trades will revert. Integrating Payment Processor is one route.
  • For ticketing and RWA, transfer restrictions matter more than royalties. The same mechanism stops tickets being resold on venues that ignore your price cap.

Restricting transfers has a cost: it limits where holders can sell. Be upfront with buyers about it.

Indexing

Your marketplace page is a database query. Listings, floor prices, sale history, owner portfolios, traits and activity feeds all come from an indexer that reads contract events and stores them in Postgres or similar. Reading this from RPC at page load is too slow and gets expensive fast.

What you need to index:

  • Transfer events for every collection you support, to know current owners
  • Order events from the exchange (fulfilled, cancelled, counter incremented) to mark listings invalid
  • Metadata fetched from token URIs, with retries and a cache, because IPFS gateways are slow and URIs change
  • Off-chain orders, which never hit the chain until filled, so they live in your own order book

The tricky part is stale listings. A seller lists on your marketplace, then sells the same NFT elsewhere. Your listing must disappear when the transfer lands, or buyers hit failed transactions. Reorgs and backfills are the other two classic failure points. We compare managed subgraphs, Ponder and fully custom pipelines in blockchain indexers: The Graph vs custom. For a marketplace with its own collections, a Ponder or subgraph indexer is usually enough. Aggregating many collections across chains pushes you toward a custom pipeline or a data provider.

Lazy minting

Lazy minting means the creator signs a voucher off-chain (an EIP-712 message with the token data and price), and the token is only minted when the first buyer pays. The buyer's transaction mints and transfers in one go and covers the gas.

It lowers the barrier for creators, which matters for curated and creator platforms. The catches:

  • Vouchers must include a nonce and expiry, and the contract must track redeemed vouchers, or one voucher can be replayed.
  • The signer key that authorizes vouchers is a high-value secret. Keep it in a KMS or HSM, not an environment variable.
  • Until minting, the "NFT" lives only in your database. If your service disappears, so does the item. Tell creators.

Payments and checkout

Crypto-native buyers pay in ETH, WETH or USDC from their own wallets. Everyone else needs a card. In 2026 the standard setup is:

  • Embedded wallets created at signup by email or social login, so a new buyer gets a wallet without installing anything. Our post on account abstraction covers gas sponsorship and batching, which make first purchases a single click.
  • Card checkout through an NFT checkout or onramp provider that buys the NFT on the user's behalf and delivers it to their wallet.
  • Stablecoin pricing for RWA and ticketing, so the price doesn't move between listing and sale.

Card payments for NFTs come with chargeback risk and provider KYC rules. Budget time for the provider's onboarding review.

Compliance

NFT marketplaces are lightly regulated compared with exchanges, but not unregulated.

  • MiCA excludes unique, non-fungible crypto-assets from most of its rules, but large series of identical NFTs can be treated as fungible crypto-assets. Fractionalized NFTs almost certainly are. Get a legal opinion if you issue editions in big numbers.
  • RWA marketplaces add consumer law, custody, insurance and sometimes securities law, depending on what the token represents and whether returns are promised.
  • Sanctions screening of wallets is expected by payment partners in practice.
  • AML. High-value art and collectibles marketplaces can fall under AML rules in some jurisdictions (the EU's AML rules cover art trading above set thresholds). Check with counsel before launch.
  • Content moderation. You need takedown processes for stolen art, impersonation and IP claims.

How much does it cost to build an NFT marketplace?

Ranges below include design, contracts, indexer, frontend, admin and an external audit. They assume EVM and Seaport-based settlement.

ScopeWhat's in itCostTimeline
PoCOwn collection, fixed-price listings on Seaport, basic indexer, wallet connect, testnet$15,000 to $35,0003 to 6 weeks
MVPOne niche, listings and offers, lazy minting or primary drops, embedded wallets, card checkout, admin panel, audit$40,000 to $120,0008 to 14 weeks
ProductionMulti-collection, auctions, ERC-721C or custom transfer rules, analytics, KYC flows, multiple chains, second audit$120,000 to $300,000+4 to 8 months

Public market ranges line up: a 2026 breakdown by Debut Infotech puts an NFT marketplace at $50,000 to $120,000, and we show how that compares with other project types in our blockchain app development cost guide. You can get a ballpark for your own scope from our cost calculator.

What pushes the cost up:

  • Custom settlement logic instead of Seaport. Expect more contract code and a longer audit.
  • Physical assets. Custody, redemption flows, shipping, insurance and the legal work around them often cost more than the software.
  • Multi-chain support. Each chain adds contracts, indexer config and testing. Solana is a separate codebase.
  • Aggregation of other marketplaces' listings, which means more indexing and order-format handling.
  • Fiat checkout and KYC integrations, plus the provider review time.

Running costs to plan for: RPC and indexer hosting, metadata and image storage (IPFS pinning plus a CDN), checkout provider fees, monitoring, and moderation staff.

Frequently asked questions

How long does it take to build an NFT marketplace?

A focused MVP takes 8 to 14 weeks in our planning, including an audit. A production marketplace with auctions, multiple chains and RWA flows takes 4 to 8 months. Audit queues and payment provider onboarding often decide the launch date more than development does.

Should I use a white-label NFT marketplace?

It can work for a quick test of demand. The trade-off is that the contracts, the order book and the user data usually belong to the vendor, and the hard parts of a niche marketplace (redemption, transfer rules, checkout) rarely come in the box. We compare the options in white label DeFi: build vs buy, and the logic is similar for NFTs.

Can I still enforce royalties in 2026?

Partly. EIP-2981 royalties are optional on most venues. ERC-721C lets a creator restrict transfers to approved marketplaces, which enforces royalties on OpenSea and Payment Processor based venues, at the cost of blocking sales elsewhere.

Which blockchain is best for an NFT marketplace?

It depends on where your buyers are and how cheap each trade must be. Polygon and Base are common for consumer and RWA marketplaces because fees are low. Ethereum mainnet still suits high-value art. Solana has a strong collectibles scene of its own.

How do NFT marketplaces make money?

Mostly through a fee on each sale, usually a low single-digit percentage. Primary sales, featured placements, premium creator tools and redemption or vaulting fees add revenue. In niche marketplaces, the fee on the underlying asset business tends to matter more than trading fees.

Do I need KYC for an NFT marketplace?

For an art or collectibles platform with crypto-only payments, often not at the user level, though sanctions screening is expected. For RWA, high-value items and fiat payments, KYC is usually required by your payment partners or by law. Ask counsel in your target markets.

Build your marketplace with us

We build NFT products end to end, from ERC-721C collections and Seaport zones to indexers and checkout. We also built ParrotLink, which sends tokens and NFTs as a link over SMS or email. If you have a niche in mind, see our NFT development services or tell us what you're building and we'll help you scope it.

Keep reading

Ready when you are

Tell us what you are building and where you are stuck. You get a reply from an engineer and a scoped estimate for a PoC, MVP or full launch. We reply within 24 hours, usually the same business day.

23stud.ioWeb3 and blockchain development studio. Advice, development, team extension or complete project delivery.
Copyright © 2026 23stud.io. All rights reserved