# Metadata Standards ## Please Use My Template Music NFTs don't have an established standard for metadata, so that means we're all basically guessing. Having standardized metadata will make front ends easier to build. What standards do any NFT's really have for metadata besides the gold standard [Opensea](https://docs.opensea.io/docs/metadata-standards) page? The pieces of metadata needed for a web3 music dapp weren't in the metadata standards that I looked at. What I'm talking about are simple things like duration of the song, resized images, contract metadata, and more. This is why I had to come up with my own templates. ## Thicc = Good The more thicc the metadata, the better! You can download a blank file of the metadata standards [here](https://github.com/jasondesante/721J-Token/tree/master/Metadata%20Templates) {% embed url="" %} ## How To Improve Metadata Standards We must improve metadata standards. It's important. One important first step is to make sure that you don't write things in different styles inside the same metadata file. Like using snake\_case and camelCase in the same file, which some platforms do. Standardizing music NFT metadata deserves serious attention. When everyone agrees on data organization, it becomes more efficient and enables builders to work from the same playbook. Having shared standards, with clear guidelines on where to find what, makes the entire ecosystem stronger, especially as those standards evolve over time. My goal is to see regular thicc metadata become ultra thicc one day. ### snake\_case vs camelCase My suggested metadata standard files are all using snake case. There's something called camelCase. And something else called snake\_case. camelCaseLooksLikeThis. Camel case is seen a lot in Javascript. snake\_case\_is\_all\_underscores. Is snake case named that way because the long snake of words, I don't know? I guess camel case is named that because the capitals are like humps on a camel? Anyways, the Opensea metadata standard which to me is the base of all other metadata standards, it uses snake case exclusively. There are other metadata standards I've seen suggested by other people and they will literally use snake case and camel case in the same file which is insane to me, so for my version it's all snake case. My take is that using snake\_case and camelCase in the same piece of metadata invalidates someone's opinion. Read even more about metadata standards [here on Opensea's site.](https://docs.opensea.io/docs/metadata-standards) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://contract-wizard.gitbook.io/contract-wizard/create/the-metadata-maker/metadata-standards.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.