The NFT I have imported not showing up it images

[MikeNg]

Before deploying to the production, I deployed a sample NFT contract on the Goerli network, the JSON file and the image file were stored on AWS S3, and everything worked fine, the NFT image and the name show correctly on Metamask after I have imported.

But after I have switched to the production, the NFT contract has been deployed onto Polygon Mainnet, the metadata JSON and the image are generated in real-time from my hosted API, my hosted API is returned in the metadata file in applicatoin/json, and the image is in SVG format - image/svg+xml, I can see the NFT name and image and others on OpenSea correctly. But when I switched to Polygon Mainnet on Metamask and imported the NFT I minted, seems like it cannot resolve the metadata and the image… Any thought to resolving this issue?

I have seen there are related discussions on this forum Post - 18052 (I cannot post link) . Is that mean I have to PUT my metadata.json and the image on IPFS? And I cannot host my personal metadata service?

[KBeeTheCapybara]

hi @MikeNg ,

Did you see this post too?

Nft metadata image and background missing

Hi, our application runs on polygon and while pulling NFTs to metamask from polygon, the metadata like image, token id, background are not displaying correctly, either one is only visible of 3. All this information is correctly visible on Opensea and as I read metamask pulls the metadata configuration from APIs of Opensea. Please help me by providing us a resolution to the issue with documentation that we can follow to fix the issue. Specifically, i need inputs on ‘image’ and ‘image_data’ and…

[KBeeTheCapybara]

In addition to above response, I think this is the original post you noted you saw but just confirming -

NFT Not display on mobile

Is your NFT on a marketplace like OpenSea? MetaMask uses third-party APIs to display NFTs in your wallet. If your NFT is not on one of the marketplaces that MetaMask uses to detect NFTs then they unfortunately cannot be displayed. Here is more information on our Knowledge Base: