<p>Looking at the minting transaction, there seems to be a mismatch between the policy ID in the minting transaction and the metadata policy ID field:</p>
<p><a href="https://cardanoscan.io/transaction/8be04d6a8e22c40f2b3970b0be893b5757d0f237efba997346cb145ccc60b7b3?tab=tokenmint" rel="nofollow noreferrer">https://cardanoscan.io/transaction/8be04d6a8e22c40f2b3970b0be893b5757d0f237efba997346cb145ccc60b7b3?tab=tokenmint</a></p>
<p>Minting policy ID: <code>77a6f71a13e82794409d06c7486a59bb7a6af38e223b646c07e3262e</code>
Metadata policy ID: <code>4a2ba87b606a0aeb40916e906670a346c4b915840a755ddf109af709</code></p>

CC BY-SA 4.0
2021-07-13T20:06:39.233Z
2021-07-13T20:06:39.233Z
Dostrelith
<p>The <a href="https://cardanoscan.io/transaction/8be04d6a8e22c40f2b3970b0be893b5757d0f237efba997346cb145ccc60b7b3?tab=metadata" rel="nofollow noreferrer">metadata in your mint transaction</a> looks good, it follows the standard correctly.</p>
<p>The only thing that kind of violates that standard is the size of your image (see chapter <a href="https://github.com/Berry-Pool/CIPs/blob/master/CIP-NFTMetadataStandard.md#structure" rel="nofollow noreferrer">&quot;Structure&quot;)</a>:</p>
<blockquote>
<p>The <code>image</code> and <code>name</code> property are marked as required. <code>image</code> should be an URI pointing to a resource with mime type <code>image/*</code> used as <strong>thumbnail</strong> or as actual link if the NFT is an image <strong>(ideally &lt;= 1MB)</strong>.</p>
</blockquote>
<p>I assume that the creator of pool.pm has set a limit for the size of the images to prevent long loading times of the website. So your 15MB image is probably just too big. Unfortunately the source code of pool.pm is not available, so I can't check if my guess is correct.</p>
<p>To fix this, you can upload a smaller version as <code>image</code> and the full resolution version of your image as <code>source</code>. Or you can try to optimize the size of the existing image.</p>
<blockquote>
<p>The <code>type</code> and <code>src</code> properties are optional. If <code>type</code> is defined, <code>src</code> will be an URI pointing to a resource of this mime type. If the mime type is <code>image/*</code>, <code>src</code> points to the same image in an higher resolution.</p>
</blockquote>
<hr />
<p>EDIT: Looking at the pool.pm page of your asset, it looks like the JSON metadata is not parsed correctly:</p>
<p><a href="https://i.sstatic.net/0bu4Q.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/0bu4Q.png" alt="enter image description here" /></a></p>
<p>Usually, the properties should be shown like that:</p>
<p><a href="https://i.sstatic.net/115wO.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/115wO.png" alt="enter image description here" /></a></p>
<p>This could be caused by the commas you used in the description property. So it's likely a bug on pool.pm. You could create an issue on their GitHub repo: <a href="https://github.com/SmaugPool/pool.pm/issues" rel="nofollow noreferrer">https://github.com/SmaugPool/pool.pm/issues</a></p>

CC BY-SA 4.0
2021-06-12T08:40:12.090Z
2021-06-12T14:06:30.707Z
2021-06-12T14:06:30.707Z
eddex
<p>I am not seeing the image of the NFT I minted a couple of hours ago on pool.pm.  I used the standard recommended by Alessandro Konrad and Smaug in <a href="https://github.com/Berry-Pool/CIPs/blob/master/CIP-NFTMetadataStandard.md" rel="noreferrer">https://github.com/Berry-Pool/CIPs/blob/master/CIP-NFTMetadataStandard.md</a>.</p>
<p>The gif in question is 15mb and it displays perfectly in IPFS using the Brave browser and in the Blockfrost IPFS web gateway.</p>
<p>Here is the metadata file:</p>
<pre><code>{
  &quot;721&quot;: {
    &quot;4a2ba87b606a0aeb40916e906670a346c4b915840a755ddf109af709&quot;: {
    &quot;cardanollama001&quot;: {
    &quot;name&quot;: &quot;Cardano Llama 001&quot;,
    &quot;image&quot;: &quot;ipfs://QmSahUdK9RTNDBGEq6xHWHZXRFwyQv8wBAtRgpxFCkNvqz&quot;,
    &quot;description&quot;: &quot;1bit aestethic, 256 colors, 90 hand-glitched frame loop&quot;,
    &quot;size&quot;: &quot;1000x666&quot;,
    &quot;rarity&quot;: &quot;225 of 250&quot;
     }
    }
  }
}
</code></pre>
<p>Here is the link to the pool.pm link:</p>
<p><a href="https://pool.pm/77a6f71a13e82794409d06c7486a59bb7a6af38e223b646c07e3262e.cardanollama001" rel="noreferrer">https://pool.pm/77a6f71a13e82794409d06c7486a59bb7a6af38e223b646c07e3262e.cardanollama001</a></p>
<p>I think I followed the standard to a tee, but I am stumped at this issue, and I can't figure out a solution.</p>
<p>Any help is very much appreciated!</p>

CC BY-SA 4.0
2021-10-20T12:47:15.073Z
I'm facing the same problem mate, do you found any solution rather than reducing the image size?
Anis
CC BY-SA 4.0
2022-05-08T05:31:49.613Z
Hey [@Anis](https://cardano.stackexchange.com/users/4486/anis) If you give me the minting transaction hash I can try to help.
keefie
<nft><native-assets><metadata>
NFT Image not Displaying in Pool.pm after using the 721 Metadata Standard
# NFT Image not Displaying in Pool.pm after using the 721 Metadata Standard

(Asked by: username_0 on 2021-06-11)

I am not seeing the image of the NFT I minted a couple of hours ago on pool.pm.  I used the standard recommended by Alessandro Konrad and Smaug in https://github.com/Berry-Pool/CIPs/blob/master/CIP-NFTMetadataStandard.md.
The gif in question is 15mb and it displays perfectly in IPFS using the Brave browser and in the Blockfrost IPFS web gateway.
Here is the metadata file:
{
  "721": {
    "4a2ba87b606a0aeb40916e906670a346c4b915840a755ddf109af709": {
    "cardanollama001": {
    "name": "Cardano Llama 001",
    "image": "ipfs://QmSahUdK9RTNDBGEq6xHWHZXRFwyQv8wBAtRgpxFCkNvqz",
    "description": "1bit aestethic, 256 colors, 90 hand-glitched frame loop",
    "size": "1000x666",
    "rarity": "225 of 250"
     }
    }
  }
}

Here is the link to the pool.pm link:
https://pool.pm/77a6f71a13e82794409d06c7486a59bb7a6af38e223b646c07e3262e.cardanollama001
I think I followed the standard to a tee, but I am stumped at this issue, and I can't figure out a solution.
Any help is very much appreciated!

**Tags:** nft, native-assets, metadata
> **Comments:**
> **username_1**: I'm facing the same problem mate, do you found any solution rather than reducing the image size?  
> **username_2**: Hey [@Anis](https://cardano.stackexchange.com/users/4486/anis) If you give me the minting transaction hash I can try to help.  

---

## 2 answers

### Answer by username_3 on 2021-07-13. Score: 2

Looking at the minting transaction, there seems to be a mismatch between the policy ID in the minting transaction and the metadata policy ID field:

<https://cardanoscan.io/transaction/8be04d6a8e22c40f2b3970b0be893b5757d0f237efba997346cb145ccc60b7b3?tab=tokenmint>

Minting policy ID: `77a6f71a13e82794409d06c7486a59bb7a6af38e223b646c07e3262e`
Metadata policy ID: `4a2ba87b606a0aeb40916e906670a346c4b915840a755ddf109af709`


---

### Answer by username_4 on 2021-06-12. Score: 2

The [metadata in your mint transaction](https://cardanoscan.io/transaction/8be04d6a8e22c40f2b3970b0be893b5757d0f237efba997346cb145ccc60b7b3?tab=metadata) looks good, it follows the standard correctly.

The only thing that kind of violates that standard is the size of your image (see chapter ["Structure")](https://github.com/Berry-Pool/CIPs/blob/master/CIP-NFTMetadataStandard.md#structure):

> The `image` and `name` property are marked as required. `image` should be an URI pointing to a resource with mime type `image/*` used as **thumbnail** or as actual link if the NFT is an image **(ideally <= 1MB)**.

I assume that the creator of pool.pm has set a limit for the size of the images to prevent long loading times of the website. So your 15MB image is probably just too big. Unfortunately the source code of pool.pm is not available, so I can't check if my guess is correct.

To fix this, you can upload a smaller version as `image` and the full resolution version of your image as `source`. Or you can try to optimize the size of the existing image.

> The `type` and `src` properties are optional. If `type` is defined, `src` will be an URI pointing to a resource of this mime type. If the mime type is `image/*`, `src` points to the same image in an higher resolution.

---

EDIT: Looking at the pool.pm page of your asset, it looks like the JSON metadata is not parsed correctly:

[![enter image description here](https://i.sstatic.net/0bu4Q.png)](https://i.sstatic.net/0bu4Q.png)

Usually, the properties should be shown like that:

[![enter image description here](https://i.sstatic.net/115wO.png)](https://i.sstatic.net/115wO.png)

This could be caused by the commas you used in the description property. So it's likely a bug on pool.pm. You could create an issue on their GitHub repo: <https://github.com/SmaugPool/pool.pm/issues>


---

