---
url: https://docs.floored.app/features/metadata-collections.md
description: >-
  Add standalone, new-collection, or existing-collection metadata to content
  before inscription.
---

# Metadata and collections

Metadata gives an inscription a collection name, item name, traits, supply, links, and other display information. It is included with the content when you inscribe and counts toward the final size.

## Before you start

* Prepare the text, image, or file in **Create** before opening metadata.
* A new collection needs a name, symbol, and positive whole-number maximum supply.
* Adding to an existing collection requires its collection transaction hash.
* Merkle root and proof fields are advanced. Enter them only when the collection setup requires them and the collection owner has provided the correct values.
* Metadata is part of the on-chain inscription. Check it carefully because the creator studio cannot edit the published result.

## Find metadata options

1. Open **Create**.
2. Prepare the content you want to inscribe.
3. Open **Inscribe options**.
4. Choose **Create New Collection** or **Add to Existing Collection**.

Use no metadata for a standalone Ethscription. If metadata is already attached and you want a standalone result, open **Inscribe options** and choose **Remove metadata**.

## Create a collection and its first item

The guided flow has **Collection**, **Item**, and **Review** steps.

### 1. Enter collection details

1. Enter the **Collection Name**.
2. Enter a short **Symbol**.
3. Enter **Max Supply** as a positive whole number.
4. Open **Appearance and links** to add an optional description, logo, banner, background color, website, X link, or Discord link.
5. Open **Advanced settings** only if you need an initial owner or Merkle root.
6. Leave **Initial Owner** blank to use the connected wallet.
7. Select **Next**.

The Item step becomes available when the required collection fields are valid.

### 2. Describe the first item

1. Enter the optional item name and description.
2. Open **Item display** to confirm the item index and optional background color. The first item starts at `0`.
3. Open **Attributes** and select **Add Attribute** for each stable trait.
4. Enter both **Trait Type** and **Value** for every attribute row.
5. Add a Merkle proof only when the collection rules require one.
6. Select **Next**.

The Review step becomes available when the item fields and all attribute pairs are valid.

### 3. Review and finish

1. Compare the collection name, symbol, supply, first item, index, and attribute count with your intended setup.
2. Select **Edit** beside Collection or Item to correct a value.
3. Select **Done**.

Done returns you to Create with the metadata attached. It does not publish anything yet. Confirm the final encoded size, then select **Inscribe** and approve the Ethereum transaction.

## Add an item to an existing collection

1. In **Inscribe options**, choose **Add to Existing Collection**.
2. Paste the complete collection transaction hash into **Collection ID**.
3. Enter the item name, description, and non-negative whole-number item index.
4. Add optional attributes. Every row needs both a trait type and a value.
5. Open **Merkle Proof** only if the collection owner supplied a required proof.
6. Enter one 32-byte `0x` proof hash per line.
7. Select **Done**.
8. Back in Create, review the final content size and select **Inscribe** when ready.

The collection ID and item values shown in Create confirm that the metadata is attached. The item does not join the collection until the Ethereum inscription and separate collection confirmation complete.

## Remove or replace metadata

1. Open **Inscribe options**.
2. Choose **Remove metadata**.
3. Confirm the warning.

Removing metadata discards the unsaved metadata changes from the current draft. It does not affect a previously published Ethscription.

To use another metadata mode, remove the current metadata first, then reopen Inscribe options and choose the new mode.

## How to know it worked

After you inscribe:

* **Ethscription created** means the Ethereum transaction confirmed.
* **Created on Ethereum. Collection confirmation is still pending** means the Ethscription exists, but floored is still processing the collection update.
* A collection page, collection name, item name, and attributes appearing on the detail page confirm that the collection data is available in floored.

Collection confirmation can finish after Ethereum creation. Do not repeat the inscription just because collection data is still pending.

## Fix validation problems

floored blocks **Next** or **Done** until the current fields are valid.

* **Collection name or symbol is missing:** Enter both required values.
* **Max Supply is invalid:** Use a positive whole number.
* **Collection ID is invalid:** Paste the complete collection creation transaction hash.
* **Initial Owner is invalid:** Use a complete Ethereum address or resolvable ENS name, or leave it blank.
* **Item Index is invalid:** Use zero or a positive whole number.
* **Attribute is incomplete:** Fill both Trait Type and Value, or delete the row.
* **Merkle root or proof is invalid:** Use complete 32-byte `0x` hashes supplied for that collection, or leave optional fields blank.
* **Final content is too large:** Remove unnecessary metadata, reduce images, or compress the main content until the total is 150 KB or smaller.

See [Creator studio](/features/create) for inscription recovery and [Troubleshooting](/troubleshooting) if a confirmed collection update remains missing.

## Metadata fields at a glance

| Group | Fields |
|---|---|
| Required collection fields | Collection name, symbol, maximum supply |
| Optional collection display | Description, logo, banner, background color, website, X, Discord |
| Advanced collection fields | Initial owner, Merkle root |
| Item fields | Item name, description, item index, background color, attributes |
| Existing collection fields | Collection ID and any required Merkle proof |