Collection maker
Build your collection, then launch it in FireSat
Add your pictures, give each NFT its traits, and export one ZIP that FireSat imports. Your pictures stay on your computer: nothing is uploaded.
- 1Add pictures
- 2Give them traits
- 3Export a ZIP
- 4Send it to your phone
Drop a folder of pictures here
PNG, JPEG, WebP or GIF, up to 21,000,000. Numbers come from the file names: 12.png is #12.
Everything stays on your computer. Nothing is uploaded.
What FireSat reads
FireSat’s format
The pictures and collection.csv: a file column with each picture’s name, a number column, then one column per trait. An empty cell means “without one”.
file,number,Sky,Hat,Eyes 1.png,1,Dusk,Cap,Sleepy 2.png,2,Aurora,,Wink
HashLips’ format
A HashLips Art Engine build folder, zipped as it is. Each NFT’s JSON lists its traits under attributes; a trait left out means “without one”.
build/ images/1.png, 2.png … json/1.json, 2.json … json/_metadata.json
FireSat’s limits
- Up to 21,000,000 NFTs, numbered from 1.
- Up to 20 traits, each with up to 100 values.
- A trait's name up to 32 characters; a value up to 64.
- PNG, JPEG, WebP or GIF. FireSat makes still pictures smaller when it needs to.
- A GIF stays as it is, byte for byte: at most 1 MB and 4,096 px a side. Over about 480 KB it can launch, but never be moved or sold later.
FireSat names each NFT “Collection #12” and works out rarity itself, so a name, description, rarity or price column isn’t needed.