Logo for SentXLogo for SentX
Logo for SentX
HBAR

Import artwork and metadata into DreamForge

Prepare a folder of NFT artwork and JSON for DreamForge. Check filename matching, metadata entries and copy counts before pinning or minting.

Content reviewed on

If you have already prepared a collection outside DreamForge, import the artwork and metadata together. Check how the files match before pinning anything or minting the resulting drafts.

A successful upload creates usable entries in the creator workflow. It does not prove that the files have been pinned or that NFTs have been minted.

Organize the folder

Use clear names and keep a backup of the original export. The importer supports matching artwork and JSON pairs, such as 1.png with 1.json, and a single metadata.json array that refers to artwork files.

For the array format, follow the upload screen's requirements for edition and image. Make sure referenced filenames match the files you are importing, including their spelling and case.

collection/
  1.png
  1.json
  2.png
  2.json

This tree illustrates paired files. It is not a complete metadata template.

Read the upload stages

Open Bulk Upload NFT Collection and follow the stages shown for your files. Image-only uploads can show Mint Counts; metadata uploads use a different path because the JSON provides entry information. Review any File Options and submission summary presented.

Read the matching and ordering information before submitting. A draft's edition or import order is not the serial number that Hedera will necessarily assign later.

Check the copy counts

Confirm how many copies each entry should mint. A folder with one hundred artwork files can produce more than one hundred NFTs if the copy counts are greater than one.

If you started from a launch placeholder without a token, create or link the collection token before the workflow that requires it.

Inspect the imported drafts

Open entries from the beginning, middle and end of the import. Compare their artwork, names, traits and counts with the source files. Look for missing images and rows paired with the wrong JSON.

Correct the drafts while they are still preparation. Do not use a mint operation to discover whether the import was matched correctly.

Continue when the entries are right

Pin and mint the prepared entries. Keep the original export so you can trace a problem back to the actual source file.

If an import produces unexpected entries, stop before pinning or minting and ask support with a small non-sensitive example of the file structure.