NFT metadata viewer and validator
An NFT on Ethereum or another EVM chain usually stores only a link on chain; the contract’s tokenURI() (ERC-721) or uri() (ERC-1155) returns a URL or an embedded data: URI that points to a small JSON document — the metadata. That JSON holds the name, description, image link and attributes that marketplaces display. This NFT metadata viewer renders that JSON as a card you can read, checks it against the de-facto metadata standard most marketplaces follow, and lists every ipfs:// and ar:// link with its HTTPS gateway equivalent.
It accepts plain JSON, base64, and the data:application/json;base64,… strings returned by fully on-chain collections, decoding UTF-8 correctly so emoji and accented names survive. Embedded images display immediately; remote images are fetched only when you press a button, so viewing metadata does not leak your IP address to an unknown server by accident.
Everything runs in your browser. The viewer is informational only and not investment advice; metadata says nothing about whether a token is authentic or valuable.
How to use the NFT Metadata Viewer
- Paste the metadata into Token metadata — the JSON itself, a
data:URI fromtokenURI(), or base64. Press Sample to see an example first. - Read the card: image, name, description, links and the attributes table with number, boost and date display types formatted.
- Check Validation for errors (red), warnings (amber) and confirmations (green).
- Choose an IPFS gateway to rewrite links; copy a single URL or the whole JSON with gateway URLs.
- For ERC-1155 metadata containing
{id}, type the Token ID to substitute it. - If the image is remote, press Load image to fetch it from the address shown.
NFT Metadata Viewer features
Decodes on-chain tokenURIs
Base64 and URL-encoded data:application/json strings are decoded with proper UTF-8 handling.
Schema checks
name, description, image, image_data, external_url, animation_url, background_color, attributes and display types are checked for the formats marketplaces expect.
Privacy-first images
data: images render at once; remote ones wait for your click and are requested without a referrer.
Gateway rewriting
Every IPFS and Arweave link anywhere in the JSON is listed with its HTTPS form for the gateway you choose, including your own.
ERC-1155 support
properties objects are shown and the {id} placeholder is replaced with the 64-character hex token ID.
The NFT metadata fields marketplaces read
ERC-721 and ERC-1155 themselves define only name, description and image (ERC-1155 adds decimals, properties and localization). The other fields come from a marketplace convention that the rest of the ecosystem adopted, which is why this page calls it the “common schema”.
| Field | Type | Notes |
|---|---|---|
| name | string | Shown as the token title |
| description | string | Markdown is supported by some marketplaces |
| image | URL | ipfs://, ar://, https:// or data:image/… |
| image_data | SVG string | Raw SVG instead of an image link; used by on-chain projects |
| external_url | URL | Link to the project’s own page for the token |
| animation_url | URL | Video, audio, 3D model or HTML; shown instead of the image where supported |
| background_color | hex, no # | Six characters, e.g. 16213e |
| attributes | array | Objects with trait_type, value, optional display_type and max_value |
Attribute display types
- No display_type — a text trait such as Background: Blue; marketplaces show rarity percentages.
- number — a numeric trait, optionally with
max_value(“5 of 10”). - boost_number and boost_percentage — shown as +12 or +12% boosts.
- date — a Unix timestamp in seconds, shown as a date. Milliseconds are a common bug and are flagged.
IPFS links and gateways
An ipfs://CID/path URI names content by its hash, so any IPFS gateway can serve it: https://ipfs.io/ipfs/CID/path, https://dweb.link/ipfs/CID/path and so on. Storing ipfs:// in metadata is better than a hard-coded gateway URL, because the token keeps working if one gateway shuts down — but the content stays available only while someone pins it. Use the contract ABI decoder to build the tokenURI(uint256) call, the Base64 encoder to inspect raw strings, and the JSON formatter to fix syntax errors.
NFT Metadata Viewer FAQ
How do I view NFT metadata?
Call tokenURI(tokenId) on the contract through a block explorer’s “Read contract” tab, then paste the result here. If it is a link, open it and paste the JSON it serves; if it starts with data:application/json, paste it as is.
Why does this NFT metadata viewer not load my image automatically?
Loading a remote image sends a request — and your IP address — to that server. The viewer waits for your click so that inspecting metadata stays private. Embedded data: images display immediately.
What does “hard-codes an IPFS gateway” mean?
The image URL points at one company’s gateway (e.g. https://gateway.example/ipfs/…). If that gateway closes, the image breaks. An ipfs:// URI lets any gateway serve the same content.
Is an SVG in the metadata safe to display?
Here, yes: SVGs are shown inside an image element, where browsers do not run scripts. Opening an untrusted SVG directly in a tab is less safe.
What is the {id} in ERC-1155 metadata URLs?
A placeholder that clients replace with the token ID as 64 lowercase hexadecimal characters, so one URI template serves every token. Enter a token ID to see the substituted URL.
Does valid metadata mean the NFT is genuine?
No. Anyone can copy metadata. Authenticity depends on the contract address, which you should verify with the creator’s official channels.