What this tool does
Paste an NFT contract address plus a token id, pick a chain, and we read the metadata straight from the blockchain. The server calls the contract's tokenURI (for ERC-721) or uri (for ERC-1155), follows the link (HTTPS or IPFS), and shows the image, name, description, and traits in one panel.
There is no API key and no wallet connect. You also get a copyable tokenURI, the full raw JSON, and one-click links to OpenSea and the block explorer.
How to use it
- Paste the NFT contract address in the first field. It must be `0x` followed by 40 hexadecimal characters (the standard EVM address format).
- Type the token id in the second field. Most collections start at `1` or `0` and count up. You can also paste a hex id like `0x1a3b` if you copied it from a marketplace.
- Pick the chain the NFT lives on. The same contract address never appears on two chains, but a project may have parallel deployments on Polygon, Base, Arbitrum, Optimism, or BSC.
- Click "Look up". The server detects whether the contract is ERC-721 or ERC-1155, reads the on-chain link, and downloads the metadata file (8 second timeout).
- Look at the image preview on the left and the description plus links on the right. The image is loaded through our proxy so hotlink-protected gateways do not block it.
- Scroll to the attributes table to see traits like "Background: Aquamarine" or "Mouth: Bored Unshaven". They are sorted by trait name for predictable order.
- Use the copy buttons on the tokenURI row and the raw JSON box if you need the exact strings for your own script, indexer, or audit notes.
- Click "OpenSea" or "Explorer" to open the token on a marketplace or the block explorer for that chain.
When this is useful
Six common situations where reading NFT metadata pays off:
- Verifying that a contract address actually points at the collection you think it does: paste the address you found in Discord or a tweet and check the name, image, and OpenSea link match the project.
- Debugging your own NFT contract before mint: confirm the tokenURI you set in the contract resolves correctly through IPFS and that your JSON parses on the first try.
- Auditing a metadata document before buying: see the exact attributes the contract returns, not the marketplace's filtered view. Some collections list traits the marketplace hides.
- Comparing the same token id across copies and forks: derivative contracts often keep the original tokenURI structure, so a quick lookup tells you whether a clone reuses the same JSON or substitutes its own.
- Backing up the image and metadata for your own NFT: copy the resolved IPFS gateway URL, pin it to your own IPFS node, and you no longer depend on the project's pinning service staying online.
- Building a dashboard, gallery, or indexer: pull canonical name, image, and traits from the source once, cache them, and stop scraping marketplace HTML for data that already lives on chain.
Related tools: token info lookup, ENS resolver, multi-chain address activity, crypto address validator, gas tracker.
Questions and answers
An NFT is a row in a smart contract that ties a unique number (the token id) to a piece of metadata: usually a name, a description, an image, and a list of traits. The contract guarantees that exactly one wallet owns each token id at a time and that ownership history is publicly visible on the blockchain. The image itself is not stored on the blockchain. The contract just stores a link to a metadata file (often on IPFS), which in turn links to the image. That is why this tool needs two steps: read the on-chain link, then fetch the file it points to.