Metadata and Hosting Options

As awesome as NFTs are, without metadata they are just numbers! Fortunately, a metadata standard was included in EIP721, along with some additions (background color, stats) to improve the rendering on markets like OpenSea.

Note: This “standard” is more of a suggestion than a fully agreed upon specification. As we'll show below, there are several versions currently adhered too.

The EIP721 standard:

    "title": "Asset Metadata",
    "type": "object",
    "properties": {
        "name": {
            "type": "string",
            "description": "Identifies the asset to which this NFT represents",
        "description": {
            "type": "string",
            "description": "Describes the asset to which this NFT represents",
        "image": {
            "type": "string",
            "description": "A URI pointing to a resource with mime type image/* representing the asset to which this NFT represents. Consider making any images at a width between 320 and 1080 pixels and aspect ratio between 1.91:1 and 4:5 inclusive.",

This content should be hosted at an HTTP or IPFS URL (using an IPFS gateway like (, and should be unique for EACH NFT.

For example, tokenId 1 should be hosted at, and tokenId 2 should be hosted at Sending a request to the URL should return the unique JSON blob, like the above.

Showcase Site Metadata: Showcase and auction sites like OpenSea and Rarebits tend to have their own supported versions of the standard. We'll touch on those two hear, as they are currently the most popular.


The following attributes are available, and will customize how your NFTs are displayed in the OpenSea store:

And an example:

  "name": "Kauri Original Contributor",
  "image": "", 
  "description": "This badge was awarded to one of the first 100 users on Kauri!", 
  "attributes": {
    "level": 1,
  "external_url": "", 
  "background_color": "00000"


And an example:

  "name": "Robot token #14",
  "image_url": "",
  "home_url": "",
  "description": "This is the amazing Robot #14, please buy me!",
  "properties": [
    {"key": "generation", "value": 4, type: "integer"}, 
    {"key": "cooldown", "value": "slow", type: "string"}
  "tags": ["red","rare","fire"]

Hosting the Metadata

An important consideration for your NFT is where the metadata will be hosted, as a dead link effectively kills your token! While the ERC721 standard allows these URIs to be updated, really this behavior should be prevented at the implementation level to avoid an asset having it's information changed after creation (which can be used maliciously). Not too mention that even a bit of downtime on a URI can be problematic, at the very least negatively affecting the user experience.

So to minimize these possibilities, we suggest using a distributed storage solution like IPFS, and eventually Swarm. An easy way to upload content to IPFS is to use an app like

This app allows you to just drag and drop a properly formatted .json file (using the standard), and will return a URL with the IPFS hash, which you can use in your token!

Important note: Your data in IPFS only exists as long as it is pinned (flagged for storage on an IPFS node). While nodes like Infura are reliable, ultimately running your own node(s) is the safest choice, at least until Filecoin or similar products are ready. If you're planning to build a fully-featured application around your NFT, consider using something like, built and maintained by our very own Greg Jeanmart!

Another option for adding and storing metadata is to use Abacus Protocol:, which is a method recommended by OpenSea.

The metadata patterns for NFTs are still evolving (along with the storage options), and we'll continue to update this document as new options and best practices emerge.