Tool AT-W40REV. 2026-A
Check NFT metadata: does the marketplace show your NFT correctly?
Marketplaces and wallets read the name, image and traits of an NFT from a JSON file that the contract points to with tokenURI. A # before the colour, a number in quotation marks or a gateway address instead of ipfs:// is enough for fields to go missing or the image to vanish at some point. The checker reads your JSON or data: URI, checks it against ERC-721, ERC-1155, ERC-7572 and the marketplace rules, and shows a preview.
- free
- no wallet needed
- checks in the browser, fetches nothing
01 / CHECKER
Paste metadata, read the findings and view the preview
Checker · NFT metadata under ERC-721, ERC-1155 and ERC-7572
The tool checks what you paste in against ERC-721, ERC-1155, ERC-7572 and the marketplaces' documented rules. It fetches nothing: it does not check whether the images and files behind the addresses can actually be reached.
Result
Preview, roughly as on a marketplace
Findings
Addresses and storage locations
| Field | Rating | Address |
|---|
Nothing is fetched. If you want to look at the file yourself, open the gateway address shown in your browser.
Corrected version
View JSON
Rules under ERC-721, ERC-1155, ERC-7572, the OpenSea documentation and the ERC-8495 draft, as of 14 November 2026. The source is given with every finding. We will build a collection with you that appears correctly everywhere; write to us using the contact form.
Checks in your browser. Nothing is sent, stored or fetched.
02 / PROCESS
How a marketplace gets to a name and an image
The contract almost never holds the image itself. For each token, an ERC-721 contract returns an address through the function tokenURI, an ERC-1155 contract through uri. Behind that address is a small JSON document with a name, a description and the address of the image. So the marketplace fetches two files one after the other, and either can be missing, misspelt or moved.
ERC-721 defines only three fields for this: name, description and image. Everything else that marketplaces show, from videos to traits, follows a convention that OpenSea documented in 2018. Because OpenSea was the marketplace with the most users and the highest turnover White et al. 2022, the others follow it. Since November 2026 this convention has existed as the ERC-8495 draft; the checker uses both as its yardstick and names the source with every finding.
Faulty metadata is not a cosmetic matter. If the link between token and file is stored wrongly, the NFT is cut off from what it stands for and, in the worst case, becomes worthless Mell and Yaga 2024.
The fields of the token metadata
| Field | Origin | What belongs in it |
|---|---|---|
| name | ERC-721, ERC-1155 | Name of the token, plain text. If it is missing, marketplaces usually show only “#123”. |
| description | ERC-721, ERC-1155 | Description. OpenSea reads Markdown; raw HTML is not rendered. |
| image | ERC-721, ERC-1155 | Image for lists and preview. ERC-721 recommends a width of 320 to 1080 px, OpenSea at least 3000 × 3000 px. |
| animation_url | OpenSea, ERC-8495 draft | Video, audio, 3D model or HTML page, shown instead of the image. The image remains mandatory as a fallback. |
| external_url | OpenSea, ERC-8495 draft | Link from the marketplace to your own page, preferably https. |
| background_color | OpenSea, ERC-8495 draft | Background colour behind the image: six hex digits without #, such as E0F2FE. |
| attributes | OpenSea, ERC-8495 draft | Traits as a list of trait_type, value and optionally display_type and max_value. The collection's filters are built from them. |
| decimals | ERC-1155 | Decimal places for displaying the quantity, a whole number from 0. |
| properties | ERC-1155 | Any additional information as an object. Marketplaces show only traits from attributes as filters. |
| localization | ERC-1155 | Translations: uri with {locale}, default and locales are required. |
| image_data | Legacy field (OpenSea 2018) | Raw SVG instead of image. Only read if image is missing; do not use any more. |
| youtube_url | Legacy field (OpenSea 2018) | YouTube video instead of animation_url. Do not use any more. |
No field is required, not even in ERC-721. If name or image is missing, the marketplace still shows only a number and a placeholder. Rules as of 14 November 2026.
The image deserves particular care. Collections look uniform, and alongside past sales history, image features predict the price best Nadini et al. 2021. ERC-721 recommends a width of 320 to 1080 pixels at an aspect ratio between 4:5 and 1.91:1, OpenSea at least 3000 × 3000 pixels. If the image is in the text as a data: URI, the checker reads format and size straight from the bytes.
03 / TRAITS
attributes: writing traits so that filters are correct
Filters of a collection and, on many sites, the rarity of an NFT are built from attributes. That has consequences: across 410 collections with 3.7 million transactions, the rarity calculated from the traits was clearly linked to price and trading Mekacher et al. 2022. One space too many in “Colour ” turns one trait type into two, and the count is already wrong.
| Entry in attributes | Display | Type |
|---|---|---|
| {"trait_type":"Colour","value":"Gold"} | Colour: Gold | Text |
| {"trait_type":"Level","value":3,"max_value":5} | Level: 3 of 5 | Number |
| {"display_type":"number","trait_type":"Points","value":12} | Points: 12 | Number |
| {"display_type":"boost_number","trait_type":"Stamina","value":40} | Stamina: +40 | Bonus |
| {"display_type":"boost_percentage","trait_type":"Discount","value":10} | Discount: +10 % | Bonus in % |
| {"display_type":"date","trait_type":"Valid until","value":1798761600} | Valid until: 01.01.2027 | Date |
display_type: number, boost_number, boost_percentage, date, string, text. Other values are treated as if the field were missing.
- Number without quotation marks. "value": "5" is text, "value": 5 is a number. For number, boost_number, boost_percentage and date it must be a number; OpenSea explicitly reads a number in quotation marks as text.
- Date in seconds. Unix time like block.timestamp, so 1798761600 for 1 January 2027. Values from 1,000,000,000,000 upwards are almost always milliseconds: 1798761600000 read as seconds would be the year 58970.
- max_value only for numbers. Without max_value, OpenSea takes the highest value it has seen in the collection. If max_value is smaller than value, the entry is invalid.
- Several values, one name. A hat and a scarf: two entries of trait_type “Accessory”, each with one value. A value given as a list is ignored.
- Spelling exactly the same. “Colour” and “colour” are two filters for the marketplace. The checker reports such pairs.
04 / STORAGE LOCATIONS
data:, ipfs://, ar:// or https: where image and JSON should live
An NFT is only as lasting as the file it points to. In a study of eight large marketplaces, 80.69 per cent of metadata addresses were not on IPFS; for 2.89 per cent of tokens the address changed within three months, and content outside IPFS disappeared more often Das et al. 2022. For high-priced art it looked hardly better: 19 of 51 contracts had changed the metadata address at least once Balduf et al. 2022.
| Spelling | Rating | Why |
|---|---|---|
data:application/json;base64,… | good | Lives in the contract itself and changes only with it. Recommended for small metadata and SVG images. |
ipfs://<CID>/… | good | Content address: the CID is a hash of the content. Reachable as long as at least one node holds the data (pinning). |
ar://<Transaktions-ID> | good | Arweave, storage paid for in perpetuity. The ID is 43 characters of Base64URL. |
ar://<Name> | use with care | ArNS name: a pointer that can be repointed, and so mutable. |
https://… | use with care | Your own server or the cloud. Content can change or disappear as soon as nobody pays any more. |
https://<Gateway>/ipfs/<CID> | use with care | Ties IPFS content to a single operator. Better to enter ipfs://<CID>. |
ipns://… | use with care | Mutable name in IPFS. Only for content that is meant to change. |
web3://…, onchain:… | use with care | Fetched through a contract call (ERC-4804, ERC-8493 draft). OpenSea reads it, far from every wallet does. |
http://… | wrong | Unencrypted; browsers block such images on https pages. |
ipfs://ipfs/<CID> | wrong | Doubled ipfs; some clients correct it, but you should not rely on that. |
relativ, z. B. 1.png | wrong | Without a scheme, no client knows where the file is. |
https: the normal case, which does not last
A web address is convenient, but it lives only as long as the server and the contract with the host. This is not an NFT problem: of well over a million web references in scholarly articles, in one article in five at least one led nowhere or to changed content Klein et al. 2014. For things that are meant to change, such as an access token with a validity period, https is still right; such dynamic NFTs are now a research field of their own Guidi and Michienzi 2023. In that case the contract sends the MetadataUpdate event under ERC-4906 with every change, otherwise the marketplace goes on showing the old state for a long time.
ipfs://: content address, but only with pinning
With IPFS the address is a hash of the content, the CID Trautwein et al. 2022. If one pixel changes, the CID changes; so nobody can quietly swap the content behind an ipfs:// address. A CIDv0 begins with Qm and has 46 characters, a CIDv1 usually with bafy. The checker decodes both and checks version, codec and hash length, because a truncated CID looks normal at first glance.
Only: IPFS stores nothing by itself. A file stays reachable as long as at least one node holds it Daniel and Tschorsch 2022. In a measurement of over four million IPFS files, about half of them belonging to NFTs, many could be fetched only after several attempts, and 50 providers delivered 95 per cent of the files Shi et al. 2024. Overall, too, the network is more centralised and cloud-heavy than its reputation suggests Balduf et al. 2023. And that a marketplace shows the image proves little: often it shows its own copy Guidi et al. 2025.
| CIDv0 | QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR |
|---|---|
| CIDv1 | bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi |
Three rules follow. Pin with at least two independent providers or on a node of your own. If the file is in a folder (ipfs://…/1.png), pin the whole folder, because without the folder block nobody finds the file. And enter ipfs://, never a gateway address.
Gateway addresses: the most common avoidable mistake
Many contracts contain https://gateway.pinata.cloud/ipfs/… or https://ipfs.io/ipfs/… instead of ipfs://. That makes the display depend on exactly one operator, and availability and integrity drop to the level of an ordinary web server Balduf et al. 2022. A gateway's responses can even be swapped on the way without anyone noticing, as long as nobody recomputes the CID Stöger et al. 2023. The ERC-8495 draft cites a sample of its own: 113 of 204 token addresses using a gateway did not load. And gateways really do disappear; Cloudflare shut down cloudflare-ipfs.com and cf-ipfs.com on 14.08.2024. The checker recognises path and subdomain gateways and suggests the ipfs:// form.
ar://: paid for a long time
Arweave takes a different approach. Uploading costs a fee once, and the network is meant to hold the data permanently Daniel and Tschorsch 2022. The address is ar:// with a transaction ID of 43 characters of Base64URL, where upper and lower case matter. A shorter name after ar:// is an ArNS name: practical, but repointable and therefore mutable.
05 / ONCHAIN
Metadata in the contract: data: URIs without pitfalls
The most lasting metadata is what the contract returns itself. Researchers who studied particularly expensive art NFTs recommend exactly that for anything small enough Balduf et al. 2022. tokenURI then returns not an address but a data: URI with the JSON inside, and the image often comes along as SVG. What that costs in gas is worked out by the gas calculator.
- Base64 instead of unencoded.
data:application/json;base64,…is the recommended form. Unencoded, the browser breaks off at the first #, and a name such as “Pass #42” or a colour such as #fff in the SVG tears the document apart. - ;utf8 is not a parameter.
data:application/json;utf8,…is widespread and is read, but RFC 2397 knows only attribute=value, so ;charset=utf-8. With Base64 the question does not arise. - SVG without scripts. SVG can contain executable code Heiderich et al. 2011. Marketplaces therefore show it only as an image: scripts do not run, external fonts and images are not loaded, and OpenSea caches SVG as PNG. Anything that depends on those is missing from the display.
- Matching media type. image/svg+xml, image/png and so on belong in image. The checker compares the stated type with the actual bytes.
For any valid JSON the checker produces the Base64 version to copy, after the safe corrections such as the # before the colour, numbers in quotation marks or gateway addresses.
06 / ERC-1155
ERC-1155: {id}, file names and translations
An ERC-1155 contract often returns the same uri for all tokens, such as ipfs://bafy…/{id}.json. The client replaces the placeholder {id} with the token ID, in hexadecimal, in lower case, without 0x and padded to 64 characters. That also applies to {id} in values within the JSON, such as in image.
The most common mistake lies in the file name: the files are called 1.json, 2.json, and the marketplace looks for 000…001.json. Enter the token ID in the checker and you will see the full address. Incidentally, with ERC-721 {id} is not replaced.
ERC-1155 also brings three fields of its own: decimals for divisible tokens, properties for any additional information and localization for translations. In localization, uri, default and locales are required, and the uri contains {locale}, which the client replaces with the language code.
| Token ID | Replacement, 64 characters |
|---|---|
| 1 | 0000000000000000000000000000000000000000000000000000000000000001 |
| 42 | 000000000000000000000000000000000000000000000000000000000000002a |
| 255 | 00000000000000000000000000000000000000000000000000000000000000ff |
| 314592 | 000000000000000000000000000000000000000000000000000000000004cce0 |
07 / COLLECTION
contractURI: the metadata of the whole collection
The name, banner and description of the collection page come from a file of their own, which the function contractURI points to. ERC-7572 describes it; the standard is still a draft, but OpenSea reads it anyway. Only name is required. When the file changes, the contract sends ContractURIUpdated().
| Field | What belongs in it |
|---|---|
| name | Name of the collection. The only required field. |
| symbol | Abbreviation of the collection. |
| description | Description of the collection. |
| image | Profile picture of the collection. |
| banner_image | Banner image at the top of the collection page. |
| featured_image | Image for featured areas. |
| external_link | Your website. Note: here the field is called external_link, in the token external_url. |
| collaborators | Ethereum addresses that may edit the collection page on marketplaces. |
The checker checks the addresses in collaborators for format and checksum under EIP-55. Wrong upper and lower case almost always points to a typing error. Compare individual addresses character by character with the Ethereum address checker.
08 / RESEARCH
What research says about NFT metadata
The ratings in the checker rest on measurements of the NFT ecosystem and the IPFS network. Five findings underpin the most important decisions; the full list with review dates is further below.
- Metadata addresses change, and web content disappears. 2.89 per cent of addresses changed within three months, and content outside IPFS was lost more often Das et al. 2022. That is why the checker rates https as mutable.
- Gateway addresses turn IPFS into a web server. Hard-coded gateways lower availability to cloud level Balduf et al. 2022, and their responses can be altered on the way Stöger et al. 2023. The checker reports every gateway address with a replacement.
- IPFS does not hold data by itself. Many NFT files needed several fetch attempts Shi et al. 2024, and marketplaces often show a copy of their own Guidi et al. 2025. That is why every ipfs:// address carries the pinning note.
- Traits move prices. Rarity derived from attributes is linked to price and returns Mekacher et al. 2022. That is why the checker reports even a stray space at the edge.
- Faulty metadata separates token and content. That is how the NIST report on NFT vulnerabilities describes it Mell and Yaga 2024; an invalid image is therefore an error, not a trifle.
09 / PROCEDURE
How to launch a collection cleanly
- Decide the storage location. Store small metadata and SVG as a data: URI in the contract, and store larger images and videos on IPFS or Arweave. Use https only for content that is meant to change.
- Check one file per token. Paste name, image and traits here until no errors and warnings are left. For ERC-1155, enter the token ID and compare the file names.
- Set up pinning twice over. Pin the whole folder with two independent providers or on a node of your own.
- Write the collection file. Create a contractURI with name, image, banner and external_link, and check it here.
- Look at it on the testnet. Mint a token and look at it on a marketplace's testnet and in two wallets before the mainnet comes into play.
- Announce changes. Send MetadataUpdate (ERC-4906), URI (ERC-1155) or ContractURIUpdated() when something changes.
Where the checker stops
- It fetches nothing. It cannot see whether an image at ipfs:// is still pinned or whether a server responds. For fetching, it names the gateway address as text.
- Marketplaces differ. Checks follow the standards, the OpenSea documentation and the ERC-8495 draft. Some wallets read less, some marketplaces read additional fields of their own.
- No verdict on value or authenticity. Name and image can be copied at will; forgeries often even used the same image addresses as the original Das et al. 2022. You recognise an NFT by contract address and token ID.
More tools for blockchain projects are in the overview Web3 tools. How we build collections, access tokens and the applications around them is described on the Web3 development page.
10 / FOR AI ASSISTANTS
Using this tool from an AI assistant
Assistants such as Claude or ChatGPT that speak the Model Context Protocol (MCP) can call this page’s calculation directly instead of rebuilding it. The server is public, needs no sign-in and stores nothing. The answer always includes the link to this page, the date of the data and the limits of the result.
- Endpoint
https://aureum-tech.com/mcp- Tool
werkzeug_nft_metadaten_pruefer- Transport
- Streamable HTTP, read-only
| Name | Required | Meaning |
|---|---|---|
metadaten | yes | What is to be checked: the metadata JSON as text, the return value of tokenURI, uri or contractURI as a data: URI (media type application/json, Base64 or unencoded) or just an address (ipfs://, ar://, https://), which is then checked but not fetched. |
standard | no | Which standard to check against: erc721 = token metadata (tokenURI), erc1155 = token metadata with {id} (uri), erc7572 = collection metadata (contractURI), auto = detect from the fields (default). |
token_id | no | ERC-1155 only: token ID in decimal (314592) or hexadecimal with 0x (0x4cce0), so that {id} is replaced and the expected file names are shown. |
Questions where an assistant should call it
- “Is this NFT metadata correct, and does OpenSea show the traits correctly?”
- “My tokenURI returns a data: URI with Base64 JSON. Is that valid?”
- “What must the file be called for ERC-1155 token 314592 if the URI contains {id}.json?”
- “Is ipfs://Qm… or Pinata's gateway address the better choice for the image?”
How the connection works and what MCP can do in your own business is explained on the page about MCP integrations.
11 / COMMON QUESTIONS
Common questions about NFT metadata
Why does OpenSea not show the image of my NFT?
Usually the address in image is the cause. Common reasons: the field is missing or is called image_url; the address is relative (just “1.png”) or unencrypted (http); it points to a gateway that has been shut down, such as cloudflare-ipfs.com (since 14.08.2024); or an unencoded data: URI contains a #, after which the browser cuts it off. If only the image has changed, the MetadataUpdate event under ERC-4906 is often missing; the marketplace then still shows the old version from its cache.
ipfs:// or a gateway address: which belongs in the metadata?
Enter ipfs://<CID>, for example ipfs://bafy…/1.png. A gateway address such as https://gateway.pinata.cloud/ipfs/… ties the file to a single operator; if that operator goes down, the image no longer loads even though the data is still in the IPFS network. In the ERC-8495 draft, 113 of 204 token addresses examined that used a gateway did not load. Gateway links are generated by the viewer itself; for every gateway address the checker suggests the ipfs:// form.
How do I write numbers and dates in attributes correctly?
Numbers without quotation marks: "value": 5, not "value": "5". In quotation marks the number counts as text, and filters then do not sort by it. For display_type number, boost_number, boost_percentage and date, value must be a number. A date is written as Unix time in seconds; a value from 1,000,000,000,000 upwards looks like milliseconds. max_value is optional and must be at least as large as value.
What does {id} do in ERC-1155?
If {id} appears in the uri or in a value in the metadata, the client replaces it with the token ID: hexadecimal, in lower case, without 0x and padded with zeros to 64 characters. Token 314592 becomes 000000000000000000000000000000000000000000000000000000000004cce0. The file must therefore be called 000000000000000000000000000000000000000000000000000000000004cce0.json; a client that follows the standard will not find “314592.json”.
What belongs in the contractURI of a collection?
Under ERC-7572, it is a JSON object with name as the only required field, plus symbol, description, image, banner_image, featured_image, external_link and collaborators. Note the website field: in the collection it is called external_link, in the individual token external_url. collaborators are Ethereum addresses that may edit the collection page on marketplaces. ERC-7572 is still a draft, but OpenSea reads it.
Base64 or ;utf8: which form of data: URI is correct?
Both are read, but Base64 is recommended. In an unencoded data: URI, browsers cut off everything from a # onwards, and a name such as “Pass #42” breaks the JSON. Moreover, ;utf8 is not a valid parameter under RFC 2397; the correct form would be ;charset=utf-8. From any valid JSON the checker produces the Base64 version to copy.
Must background_color be written with a #?
No. It must be written without it. Exactly six hex digits are required, such as "E0F2FE". With a #, some clients strip the character themselves, others ignore the colour altogether. Short forms such as "fff", colour names or rgb() are not read.
Where does the NFT metadata checker stop?
It checks the text you paste in against ERC-721, ERC-1155, ERC-7572 and the marketplaces' documented rules. It fetches no address and so does not know whether an image at ipfs:// is still pinned or whether a server responds. It says nothing about the value, authenticity or rights to the content. How contract, metadata and storage fit together and who pins permanently, we are happy to work out with you.
12 / STUDIES AND SOURCES
What the tool is based on
The guide values and notes above are based on these 15 scientific papers. Each one has been checked via its DOI or the publisher’s page (most recently on 14 November 2026): it exists, it has not been retracted, and its findings still hold for this question today.
Das, D.; Bose, P.; Ruaro, N. et al. (2022): Understanding Security Issues in the NFT Ecosystem. Proceedings of the 2022 ACM SIGSAC Conference on Computer and Communications Security (CCS ’22), pp. 667–681
Finding Study of eight large NFT marketplaces and millions of traded tokens: 80.69 per cent of metadata addresses were not on IPFS, for 2.89 per cent the address changed within three months, and content outside IPFS disappeared more often. Forgeries often used the same image addresses as the original.
In the tool The tool rates https addresses as mutable and reminds you that an NFT is recognised by contract and token ID, not by name and image.
doi.org/10.1145/3548606.3559342 · Conference paper
Balduf, L.; Florian, M.; Scheuermann, B. (2022): Dude, where's my NFT: distributed infrastructures for digital art. Proceedings of the 3rd International Workshop on Distributed Infrastructure for the Common Good (DICG ’22), pp. 1–6
Finding Of 51 contracts of high-priced art NFTs, 19 changed the metadata address at least once. Many entered a fixed gateway address instead of ipfs://, and half of the IPFS content had fewer than ten providers within a week. The authors recommend storage in the contract (data:) or content-addressed with a hash.
In the tool The tool reports gateway addresses as a warning together with an ipfs:// replacement; data: URIs count as the best choice; for folder CIDs it points out that folder and file must both remain reachable.
doi.org/10.1145/3565383.3566106 · Conference paper
Stöger, F.; Zhou, A.; Duan, H.; Perrig, A. (2023): Demystifying Web3 Centralization: The Case of Off-Chain NFT Hijacking. Financial Cryptography and Data Security (FC 2023), Lecture Notes in Computer Science, pp. 182–199
Finding Almost every point at which NFTs run through central services can be subverted. In the experiment, responses from IPFS gateways and blockchain access points could be swapped on the way.
In the tool Explains why the tool asks for ipfs:// instead of a gateway address: only the CID can be checked against the content, whichever way it arrives.
doi.org/10.1007/978-3-031-47751-5_11 · Conference paper
Guidi, B.; Michienzi, A.; Pasquale, L. (2025): On the impact of marketplaces on the availability of NFT assets on the IPFS network. 2025 IEEE Symposium on Computers and Communications (ISCC), pp. 1–6
Finding Two weeks' observation of NFT files from ten collections in the IPFS network: IPFS does not guarantee high availability, and marketplaces often show copies of their own instead of the file from the contract.
In the tool Hence the note in the result: that a marketplace shows the image does not prove that the file is still reachable in the network.
doi.org/10.1109/iscc65549.2025.11326542 · Conference paper
Shi, R.; Cheng, R.; Han, B. et al. (2024): A Closer Look into IPFS: Accessibility, Content, and Performance. Proceedings of the ACM on Measurement and Analysis of Computing Systems 8 (2), pp. 1–31
Finding Measurement of over four million files in IPFS: about half belong to NFTs, and many of them can be fetched only after several attempts. The 50 largest providers, mostly cloud nodes, deliver 95 per cent of the files.
In the tool Carries the pinning note: ipfs:// is only as available as the nodes that hold the data.
doi.org/10.1145/3656015 · Journal article
Balduf, L.; Korczyński, M.; Ascigil, O. et al. (2023): The Cloud Strikes Back: Investigating the Decentralization of IPFS. Proceedings of the 2023 ACM Internet Measurement Conference (IMC ’23), pp. 391–405
Finding Large-scale measurement of topology, traffic and providers in the IPFS network: marked centralisation and a high share of nodes in the cloud.
In the tool That is why the tool advises pinning NFT data with at least two mutually independent providers instead of a single one.
doi.org/10.1145/3618257.3624797 · Conference paper
Trautwein, D.; Raman, A.; Tyson, G. et al. (2022): Design and evaluation of IPFS: a storage layer for the decentralized web. Proceedings of the ACM SIGCOMM 2022 Conference, pp. 739–752
Finding Describes the design and measurement of IPFS: content-addressed storage over a peer-to-peer network with nodes in over 2700 networks and 152 countries; publishing and retrieval are fast enough for many applications.
In the tool Basis of the CID explanation: the address is a hash of the content, so the tool checks its structure closely.
doi.org/10.1145/3544216.3544232 · Conference paper
Daniel, E.; Tschorsch, F. (2022): IPFS and Friends: A Qualitative Comparison of Next Generation Peer-to-Peer Data Networks. IEEE Communications Surveys & Tutorials 24 (1), pp. 31–52
Finding Compares IPFS, Swarm, Hypercore, SAFE, Storj and Arweave. IPFS holds data only as long as nodes keep it voluntarily or for payment (for example via Filecoin); Arweave aims to store data permanently and has uploading paid for through fees.
In the tool Explains the difference between ipfs:// and ar:// in the notes on storage locations.
doi.org/10.1109/COMST.2022.3143147 · Review
Mell, P.; Yaga, D. (2024): Non-fungible token security. National Institute of Standards and Technology, NIST IR 8472
Finding Explains NFT technology and names 27 possible vulnerabilities. Metadata stored incorrectly can cut an NFT off from its subject and make it worthless; whoever controls an external mapping table can reassign tokens.
In the tool Explains why the tool reports missing or invalid image and metadata addresses as errors and flags mutable storage locations.
doi.org/10.6028/NIST.IR.8472 · Research report
Mekacher, A.; Bracci, A.; Nadini, M. et al. (2022): Heterogeneous rarity patterns drive price dynamics in NFT collections. Scientific Reports 12, Art. 13890
Finding 3.7 million transactions in 410 collections: rarity, calculated from an NFT's readable traits, is clearly linked to price, trading frequency and returns.
In the tool Traits are not a side issue. The tool therefore reports numbers in quotation marks, spaces at the edge and differing spellings of the same trait type, because they distort filters and rarity.
doi.org/10.1038/s41598-022-17922-5 · Journal article
Nadini, M.; Alessandretti, L.; Di Giacinto, F. et al. (2021): Mapping the NFT revolution: market trends, trade networks, and visual features. Scientific Reports 11, Art. 20902
Finding Analysis of 6.1 million sales of 4.7 million NFTs (2017 to 2021): collections look uniform, and alongside sales history, image features predict the price best.
In the tool The image is what buyers see. A missing or unloadable image is therefore reported by the tool as a warning, not as a trifle.
doi.org/10.1038/s41598-021-00053-8 · Journal article
White, B.; Mahanti, A.; Passi, K. (2022): Characterizing the OpenSea NFT Marketplace. Companion Proceedings of the Web Conference 2022 (WWW ’22), pp. 488–496
Finding 5.25 million sales on OpenSea from 2019 to 2021, the marketplace with the most users and the highest turnover; a few very active users drive growth.
In the tool That is why the tool checks, alongside the ERC standards, the fields documented by OpenSea: they are the rules the other marketplaces follow.
doi.org/10.1145/3487553.3524629 · Conference paper
Klein, M.; Van de Sompel, H.; Sanderson, R. et al. (2014): Scholarly Context Not Found: One in Five Articles Suffers from Reference Rot. PLoS ONE 9 (12), e115253
Finding Over a million web references from 3.5 million scholarly articles: one article in five is affected by link rot or changed content, and among articles with web references, seven in ten.
In the tool Supports the note on https addresses: web addresses disappear or change their content over time, even without bad intent.
doi.org/10.1371/journal.pone.0115253 · Journal article
Heiderich, M.; Frosch, T.; Jensen, M.; Holz, T. (2011): Crouching tiger - hidden payload: security risks of scalable vectors graphics. Proceedings of the 18th ACM Conference on Computer and Communications Security (CCS ’11), pp. 239–250
Finding SVG files are not mere images but can contain HTML, JavaScript and other executable parts; browsers often handled crafted SVGs wrongly.
In the tool That is why marketplaces show SVG only as an image without scripts, and the tool warns when an SVG contains scripts, event attributes or external references that have no effect there.
doi.org/10.1145/2046707.2046735 · Conference paper
Guidi, B.; Michienzi, A. (2023): From NFT 1.0 to NFT 2.0: A Review of the Evolution of Non-Fungible Tokens. Future Internet 15 (6), Art. 189
Finding Overview of the step from static NFTs, whose metadata is fixed after minting, to dynamic NFTs that change; the technical difficulties lie mainly in metadata and how it changes.
In the tool For mutable metadata, the tool names the event from ERC-4906 or URI from ERC-1155 so that marketplaces pick up the change.
doi.org/10.3390/fi15060189 · Review
Standards, authorities and manufacturer data
- ERC-721: Non-Fungible Token Standard (Final) · Final, checked 14.11.2026
- ERC-1155: Multi Token Standard, Metadata section (Final) · Final, checked 14.11.2026
- ERC-7572: Contract-level metadata via contractURI() (Draft) · Draft, checked 14.11.2026
- ERC-4906: EIP-721 Metadata Update Extension (Final) · Final, checked 14.11.2026
- ERC-8495: Token Metadata JSON Schema (Draft, Pull Request 2163) · Draft, opened 10.11.2026, version of 12.11.2026, not yet adopted; rules from it only as a warning
- OpenSea Developer Docs: Media and traits, Metadata storage, Contract-level metadata · As of 12.11.2026
- RFC 2397: The "data" URL scheme · 1998
- RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format · 2017
- multiformats/cid: Content Identifier, with multibase and multicodec table · checked 14.11.2026
- IPFS Docs: Best Practices for Storing NFT Data using IPFS · checked 14.11.2026
- Arweave HTTP API: field id (Base64URL, SHA-256 of the signature) · checked 14.11.2026
- Cloudflare-Blog: Cloudflare's public IPFS gateways and supporting Interplanetary Shipyard · 14.05.2024
- EIP-55: Mixed-case checksum address encoding · Final
13 / MORE TOOLS
Still have a question?
- AT-W32 · Businesses
Blockchain suitability check
Does your project really need a blockchain, or will a database do? - AT-W33 · Businesses
MiCA check
Does your token fall under MiCA, and what obligations follow from that? - AT-W34 · Home & business
Gas calculator
What does a transaction cost on Ethereum, Arbitrum, Optimism, Base or Polygon? - AT-W35 · Home & business
Ethereum address checker
Is this Ethereum address valid and correctly written? EIP-55 checksum and comparison of two addresses. - AT-W36 · Businesses
Selector and topic calculator
Which function selector or event topic belongs to this Solidity signature, and the other way round? - AT-W37 · Businesses
Calldata decoder
What does this transaction do? Make calldata readable before you sign.
Are you launching a collection or access tokens? Send us the copied result. We bring contract, metadata and storage location together so that marketplaces and wallets show everything correctly, and we set up the pinning, from Rodewisch.
+49 3744 4399760[email protected]Mon–Fri 8:00–17:00 · Straße der Jugend 5, 08228 Rodewisch