# ERC-721: Batch minting 1000 NFTs in Remix with automated metadata during minting **URL:** \ **Category:** Smart Contracts\ **Created:** [August 8, 2021, 12:26pm UTC](https://forum.openzeppelin.com/t/erc-721-batch-minting-1000-nfts-in-remix-with-automated-metadata-during-minting/13675 "2021-08-08T12:26:18Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![frangio](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/frangio/32/15251_2.png) [@frangio](https://forum.openzeppelin.com/u/frangio)\ **Post date:** [August 9, 2021, 8:43pm UTC](https://forum.openzeppelin.com/t/erc-721-batch-minting-1000-nfts-in-remix-with-automated-metadata-during-minting/13675/2 "2021-08-09T20:43:27Z")
For your third question see my post here and the subsequent replies: > [@Why doesn't OpenZeppelin ERC721 contain setTokenURI?](https://forum.openzeppelin.com/t/why-doesnt-openzeppelin-erc721-contain-settokenuri/6373/4): > > Yes, we think most people should try to avoid setTokenURI if possible for their use case. If you use IFPS, your baseURI wouldn’t be gateway.pinata.cloud, it would be the URI to an IPFS directory. For example, I just uploaded a directory to Pinata at [https://gateway.pinata.cloud/ipfs/QmcP9hxrnC1T5ATPmq2saFeAM1ypFX9BnAswCdHB9JCjLA/](https://gateway.pinata.cloud/ipfs/QmcP9hxrnC1T5ATPmq2saFeAM1ypFX9BnAswCdHB9JCjLA/). I can now create an ERC721 with that URL as its baseURI (or I could use a native ipfs:// protocol URI), and mint token IDs 1 and 2. The concatenated URI for token … I don't really know what collections are exactly on OpenSea. I suggest browsing OpenSea documentation and potentially asking about that in their Discord server. For batch minting, we don't have a simple solution. But you can write a contract and call `_mint` in a loop in your constructor. This will be more expensive than it technically needs to be, but as I there's no simple cheaper alternative right now. --- _[View the full topic](https://forum.openzeppelin.com/t/erc-721-batch-minting-1000-nfts-in-remix-with-automated-metadata-during-minting/13675)._