Free NFT Metadata Viewer
View NFT metadata by contract address and token ID. Fetches token URI via JSON-RPC, resolves IPFS links, and displays image, traits, and collection info.
Updated
NFT Metadata Viewer
Fetch and display NFT metadata including image, attributes, and collection info from any ERC-721 contract.
NFT Lookup
Frequently Asked Questions
What is the NFT Metadata Viewer?
The NFT Metadata Viewer is a free online tool that view nft metadata by contract address and token id. fetches token uri via json-rpc, resolves ipfs links, and displays image, traits, and collection info.. It runs entirely in your browser with no installation or sign-up needed.
Which chains are supported?
Ethereum, Polygon, and BSC using public Ankr RPC endpoints.
How is metadata fetched?
The tool calls tokenURI() on the contract via eth_call, then fetches the metadata JSON (including IPFS links via public gateway).
Is it free?
Yes, completely free.
Does the NFT Metadata Viewer work on mobile devices?
Yes, the NFT Metadata Viewer is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.
Do I need to create an account to use this tool?
No account or registration is needed. Simply open the NFT Metadata Viewer in your browser and start using it immediately. There are no sign-up walls or usage restrictions.
How do I use the NFT Metadata Viewer?
Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.
Which browsers are supported?
The NFT Metadata Viewer works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.
Why does an NFT's traits look different here than on the marketplace?
Marketplaces like OpenSea display cached, indexed data that they refresh on their own schedule, so a recent metadata update, a re-pin, or a reveal can leave their listing stale for hours or days. This viewer reads closer to the source of truth: it calls the contract's tokenURI directly (or pulls fresh OpenSea API data for Ethereum) and then fetches the JSON that URI points to, showing you exactly what the blockchain pointer resolves to right now. If the traits here are correct but the marketplace shows old values, the marketplace cache simply hasn't caught up. If they differ in the other direction, the on-chain metadata may have changed or was never properly pinned. Paste the contract address and token ID to compare the live metadata against what any marketplace is showing.
What does it mean when the NFT image shows 'not available'?
That message means the viewer read the metadata but could not load the artwork the image field points to. The most common causes are a broken or moved image URL, an IPFS gateway that timed out, or metadata that was never properly pinned, so the link resolves to nothing. Because NFT images are often stored on IPFS, the tool automatically rewrites ipfs:// links into an https://ipfs.io/ipfs/ gateway URL that a browser can load, but if that gateway is slow or the content was unpinned, the image still fails. The raw token URI and JSON shown alongside the preview let you see the exact image link, so you can test it in another gateway or confirm the asset is genuinely missing. Look up the token here to see whether the image pointer itself is broken or just the gateway.
Why can't this tool find metadata for some contract addresses?
Lookups only work for contracts that implement the ERC-721 metadata extension, meaning they expose a standard tokenURI(uint256) function the viewer can call. A plain token contract, an ERC-20, or a non-standard collection without tokenURI returns nothing to decode, so no metadata appears. A second cause is the token ID itself: if that ID was never minted or has been burned, the contract has no URI to return. Finally, some metadata is hosted on IPFS or third-party servers that block cross-origin browser requests via CORS; in that case the token URI still displays but the JSON fails to load. When that happens, the block explorer link and raw URI give you a manual path to inspect the data. Enter a valid ERC-721 address and an existing token ID to get a clean result.
How does the viewer handle IPFS links in NFT metadata?
A large share of NFT metadata and artwork is stored on IPFS rather than a normal web server, and browsers cannot load a raw ipfs:// link directly. To solve this, the viewer automatically rewrites any ipfs:// reference into an https://ipfs.io/ipfs/ gateway URL, which is a standard web address a browser can fetch. It applies the same conversion to both the metadata JSON location and the image field inside that JSON, so artwork pinned to IPFS still renders in the preview. This is why you can paste a contract and token ID and see the image even when the underlying storage is decentralized. The original, unmodified token URI is still shown so you can see the true ipfs:// pointer. Look up any token to watch the IPFS link resolve into a viewable image and downloadable JSON.
What information is in an NFT's metadata JSON?
A standard ERC-721 metadata JSON follows a predictable shape. The name and description give the token a human-readable identity, the image field holds a URL to the artwork (frequently an IPFS link), and the attributes array lists trait_type and value pairs that define rarity, such as background, eyes, or hat. Optional fields like external_url and animation_url point to a project page or an animated or 3D version of the asset. This viewer parses that JSON and renders each piece for you: the image as a preview, every attribute as a labelled trait badge, and the full raw JSON for inspection, plus a one-click button to download the complete file as a snapshot. Seeing the rendered output beside the raw data makes it easy to spot a missing image or a malformed trait. Enter a contract and token ID to see the full metadata broken down.
Related Tools
Free Secure Password Generator
Generate secure, random passwords with customizable options. Free, fast, and works entirely in your browser with no sign-up required.
Free UUID/GUID Generator
Generate universally unique identifiers (UUIDs/GUIDs). Free, fast, and works entirely in your browser with no sign-up required.
Free QR Code Generator Online
Create QR codes for URLs, text, WiFi, and contacts. Customize colors, size, and error correction. Free, private — runs in your browser, no sign-up.
Free JSON Formatter & Validator
Format, validate, and beautify JSON data with syntax highlighting and error detection. Free, fast, and works entirely in your browser with no sign-up required.
About the NFT Metadata Viewer
The NFT Metadata Viewer is a free online tool for looking up everything a smart contract knows about a single non-fungible token. Paste a contract address and a token ID, choose a chain, and it fetches the token's metadata directly from the blockchain — the name, description, image, attributes, and the raw tokenURI the contract points to. It is built for collectors verifying what they own, developers debugging an ERC-721 mint, and anyone who wants to confirm that an NFT's on-chain pointer actually resolves to the artwork and traits it claims.
Unlike a marketplace listing, which can show cached or curated data, this viewer reads the source of truth. That makes it useful for spotting broken images, mismatched traits, or metadata that was never properly pinned.
What you can look up
You provide three things, and the tool handles the rest:
- Contract address — the ERC-721 collection address, validated to be a well-formed
0xaddress (40 hexadecimal characters). - Token ID — the specific token's numeric ID within that collection.
- Blockchain — Ethereum, Polygon, or BNB Smart Chain (BSC), queried through public Ankr RPC endpoints.
Once it resolves the token, you get the rendered image, the token name and description, every trait as a labelled badge, the original token URI, a link to the contract on the matching block explorer (Etherscan, Polygonscan, or BscScan), and a one-click button to download the full metadata as a JSON file.
How the lookup works
For Ethereum tokens, the viewer first queries the OpenSea API, which returns clean, normalized metadata for indexed collections. If that misses — or for Polygon and BSC — it falls back to reading directly from the contract. It encodes an eth_call to the standard tokenURI(uint256) function (selector 0xc87b56dd), decodes the returned string, and then fetches the JSON the URI points to.
A common snag is IPFS. NFT metadata is frequently stored on IPFS rather than a normal web server, so the tool automatically rewrites ipfs:// links into an https://ipfs.io/ipfs/... gateway URL that a browser can actually load. The same normalization is applied to the image link, so artwork pinned to IPFS still displays.
Reading the results
A complete ERC-721 metadata JSON typically follows a predictable shape:
- name and description — human-readable identity for the token.
- image — a URL (often IPFS) to the artwork.
- attributes — an array of
trait_typeandvaluepairs that define rarity, such as background, eyes, or hat. - external_url and animation_url — optional links to a project page or animated/3D asset.
Seeing the raw JSON side by side with the rendered preview makes it easy to diagnose problems. If the image area shows "not available," the image field is likely broken or the gateway timed out. If traits look wrong on a marketplace but correct here, the marketplace cache is stale. Downloading the JSON gives you a permanent snapshot to compare against later or attach to a support ticket.
Privacy and limits
There is no sign-up, no installation, and nothing you enter is saved on a server. The tool does, however, make live network requests on your behalf — to the chain's RPC endpoint, to the OpenSea API for Ethereum, and to IPFS gateways for the metadata and image. Those are public endpoints, and only the contract address and token ID you type are sent.
A few practical limits are worth knowing. Lookups only work for contracts that implement the ERC-721 metadata extension; a contract without tokenURI will return nothing to decode. Some IPFS or third-party metadata hosts block cross-origin browser requests via CORS, in which case the token URI still shows but the JSON may not load. When that happens, the explorer link and the raw URI give you a path to inspect the data manually.