To claim an NFT directly on your contract, follow these steps:
Claimbutton on the NFT view
Paste in the address to claim the NFTs and the number of NFTs.
Single uploading NFTs is a preferred method for uploading one-off NFTs or smaller amounts of NFTs.
Follow these steps to lazy-mint a single NFT to your contract.
To upload single NFTs, navigate to the NFTs view and click the
Fill in the corresponding NFT metadata fields including Name, Media, and Description on the modal.
(Optional) Add Properties or traits for the NFT.
(Optional) Configure advanced metadata options such as Background Color and External URL.
Lazy Mintbutton when you are ready to mint. This action will prompt a transaction in your wallet.
Batch Uploadbutton in the NFTs view on the dashboard.
Download the sample CSV file (recommended) or JSON, which holds an example of the expected structure.
- After downloading, open the sheet in a preferred CSV editor. You can use Microsoft Excel, Google Sheets, or any other software or text editor that supports editing CSV files.
Google Sheets is a great beginner option if you are unfamiliar with using spreadsheet software. It is free to use with a Google account, and you can use it on any browser - no need to download software.
- On Google Sheets, you can click file > import to upload the sample CSV file for editing. When you open the sample file, you will find a couple of column headers with the first property row filled out.
Overview of different properties:
- name: The name of the NFT
- description: Description of the NFT
- external_url: This URL appears below the image on marketplaces like OpenSea and allows users to view the NFT from your site.
- background_color: An optional property available on OpenSea. Must use six-digit hex (#) format.
- youtube_url: Similar to the external URL, this will allow users to see the YouTube channel or video behind the NFT.
This option also allows you to upload a variety of different file types. The CSV file is used to add the NFT file next to the properties, which will parse.
- image: A link to the image or file to be uploaded. The link can be a local image or a URL of an uploaded NFT on a service, such as IPFS. Supported file types: png, jpg, jpeg, and gif
- animation_url: link to the animation that is to be uploaded. Supported file types: any file that is not an image such as mp4, audio files, pdf, CSV, 3d models, etc.
In addition to these specific properties, you can also add properties that may be unique to your collection. In the following example, we have a Shapes Collection NFT project with properties of shape, color, and sides.
Once you're done editing, export your file as a
.csvand add it to a folder with all your assets.
Upload your assets to the dashboard, verify your collection is properly mapped, and click
Nextwhich will prompt you to configure more options.
Using JSON format is recommended when using an NFT generator that will generate NFTs and their corresponding metadata and output a JSON file.
After batch uploading your NFTs, you may choose to instantly reveal them or choose delayed reveal if your contract implements the delayed reveal extension.
Reveal Upon Mint
Reveal Upon Mint instantly reveals your NFTs as normal. This option does not require any additional configuration.
You may optionally choose to shuffle your NFTs before uploading by enabling the checkbox.
Delayed Reveal allows you to put placeholder metadata until you want to reveal the actual NFT. This option is currently only available for contracts which implement the delayed reveal extension.
To configure delayed reveal:
Set a password. You will use this password later to reveal the NFTs.danger
The delayed reveal password is non-recoverable so please store it somewhere safe.
Add in your placeholder metadata: image, name, and description.
(Optional) Check the box at the bottom, if you want to shuffle the order of NFTs before uploading.
Upload NFTsbutton at the bottom. This will prompt a transaction you need to confirm in your wallet.
If you experience any issues uploading your files, please check out our Batch Upload Troubleshooting article.