1x Studio Metadata Guide Open Studio

Metadata Guide

Prepare asset links and token metadata for 1/1/X Mint Factory.

The Studio does not ask artists to upload heavy asset files directly. You upload assets to IPFS as the source folder, paste the folder CID, then upload a CSV. The Studio checks the CSV, creates one metadata JSON file per token, and uploads the final launch files to permanent storage before the mint page goes live.

1. Upload assets to Pinata

  1. Open Pinata and go to Files.
  2. Click Add or + Add Files in the top-right corner.
  3. Choose Folder, then select the folder with your images, GIFs, videos, audio files, or HTML files.
  4. Upload to Public IPFS so collectors and mint pages can load the assets.
  5. When the upload finishes, open the uploaded folder details and copy only the folder CID.

Paste the CID into Asset folder CID in the Studio. A CID looks like bafy... or Qm.... If you accidentally paste a full ipfs:// link or gateway URL, the Studio will extract the CID.

Important: keep source IPFS active

The Studio reads files from the CID you enter while preparing permanent storage. Keep the source folder pinned and public until launch storage is complete. After storage completes, save the final metadata URI and storage receipt shown by the Studio.

2. Permanent storage before launch

Permanent storage is part of every 1/1/x launch. The Studio uses your IPFS folder as the source, then stores the final artwork links and generated metadata on permanent storage after the wrapper is created and before the mint page goes live.

What happens

The storage service receives the verified CID and generated metadata JSON from the Studio. It fetches the matched asset files, stores the assets and metadata permanently, then returns the final metadata base URI used by the wrapper contract.

  1. Read the source files from your IPFS folder CID.
  2. Create final token JSON files from your CSV.
  3. Store assets and metadata on permanent storage.
  4. Attach the final metadata URI to the wrapper before launch.

Why there is a cost

Permanent storage networks charge to store data long-term. The price depends on total asset size, metadata size, provider fees, and current network pricing. This is separate from Ethereum gas and separate from the 1/1/x per-mint fee collectors pay during minting.

  1. Small image collections usually cost less than video-heavy collections.
  2. The quote is calculated before the mint page goes live.
  3. The creator reviews and pays the storage cost during launch.
  4. The final metadata URI is saved with the creation record.

What artists need to do

Use Pinata or another IPFS provider to prepare the source folder. Keep it public until permanent storage completes. After wrapper creation, review the storage quote during launch, pay it, then wait for the Studio to attach the final metadata URI before registering the extension and opening the mint page.

Further reading: IPFS pinning guide, Arweave permanent storage, and ArDrive upload guide.

3. Choose a CSV format

You can use the 1xStudio template, or you can upload a marketplace-style metadata CSV like the one with image, animation_url, and attribute:: columns.

1xStudio template

Use this if you are starting fresh. The media_filename value must match a file in your IPFS folder.

token_number,name,description,media_filename,media_type,trait_background,trait_mood 1,"Token 1","Short description","1.png","image","Pink","Calm" 2,"Token 2","Short description","2.mp4","video","Green","Wild"

Marketplace CSV

Use this if your metadata already came from another tool. The old URLs are used only to read filenames. Final metadata links are rebuilt from the CID you enter in the Studio.

name,description,image,animation_url,attribute::tokenId,attribute::Lineage1 "Portal Warden","Culture Monke #1","https://gateway.example/ipfs/oldCid/1-Portal%20Warden.gif","https://gateway.example/ipfs/oldCid/1-Portal%20Warden.gif",1,"Constructed Distortion"

4. What the Studio creates

Before launch storage, a folder CID of bafyExampleCid lets the Studio prepare a draft token metadata file named 1.json. The old gateway URL and old CID from the CSV are not kept. During permanent storage, the storage service should rewrite the asset links to permanent asset URLs before returning the final metadata base URI.

{ "name": "Portal Warden", "description": "Culture Monke #1", "image": "ipfs://bafyExampleCid/1-Portal Warden.gif", "animation_url": "ipfs://bafyExampleCid/1-Portal Warden.gif", "attributes": [ { "trait_type": "Lineage1", "value": "Constructed Distortion" } ] }

5. Checks before continuing

  • CID check: The Studio accepts a real folder CID such as bafy... or Qm....
  • Filename check: Every CSV asset filename must exist in the IPFS folder. Capitalization and file extensions must match.
  • Count check: The IPFS folder file count must match the unique asset filenames found in the CSV.
  • Token check: Token numbers must be unique and greater than zero.
  • Trait check: Empty trait cells are skipped. Columns like attribute::Lineage1 become metadata attributes.

Common fixes

  • If the Studio says a file is missing, compare the CSV filename with the uploaded IPFS folder row by row.
  • If the folder has extra files, remove unused files from the folder or add matching CSV rows before uploading again.
  • If Pinata just finished uploading, wait a minute and try again. Public gateways can take a short time to see a new folder.