Skip to main content

Create & Delete ENS Subnames

Create unlimited subnames like pay.yourname.eth for free—only gas fees apply. Perfect for organizing family, projects, or teams.

Updated over 2 weeks ago

Good to Know

  • Creating and deleting subnames are gas-only transactions requiring ETH on Ethereum Mainnet.

  • The Manager can create and delete subnames. For wrapped names, the Owner and Manager roles are merged.

  • There's no limit to how many subnames can be created for free.

  • Subnames can create their own subnames.

  • Subnames have only a Manager role—ownership stays with the parent name.


Note: Only .eth names and onchain subnames are supported in the ENS App. For project subnames (base.eth, uni.eth, etc), use their platform.


Understanding Subnames

When you register a .eth name, like ens.eth, you're registering a second-level domain (2LD) under the top-level domain (TLD) .eth.

Once you own a .eth name, you can create subnames under it. For example, the owner of name.eth can create subnames like sub.name.eth. Those subnames can also create their own subnames, like sub2.sub.name.eth, and so on.


How to create a subname

  1. Go to app.ens.domains

  2. Connect your Manager wallet

  3. Search for your name and open the Subnames tab.

  4. Click + New Subname.

  5. Enter the label for your new subname.

  6. Add profile records (optional)
    Click +Add More to Profile to preload address and profile records, and prompt a second transaction after the subname is created. Click Next when ready, or Click Skip if you'd like to do this later.

  7. Confirm the Transaction to create subname

  8. Confirm the Transaction to Add Profile records (If Applicable)

  9. Your subname is now created.


How to delete a subname

  1. Go to app.ens.domains

  2. Connect your Manager wallet

  3. Search for your subname

  4. Click Delete subname.

  5. Confirm the transaction.

  6. Your subname is now deleted.


Common Questions

Who can delete a subname?

The Manager can delete a subname. If the Manager differs from the parent owner, the parent can reassign the Manager role to themselves, then delete the subname.

Why don't I have a Manager?

Wrapped names don't have a separate Manager field—the Manager role merges into the Owner role on the ERC-1155 token contract. Unwrapped names have both an Owner and a Manager. All subnames (wrapped or unwrapped) have only a Manager, never an Owner.

What subnames can I create with the Name Wrapper contract?

The Name Wrapper is an advanced tool. It's recomended to think carefully before burning any fuses, and wait for ENSv2 deployments. For more information see articles in our Advanced: Name Wrapper section.

Can I wrap a subname if the parent is not wrapped?

Yes. However there would be no purpose. To use the Name Wrapper Fuses on a subname, you must wrap the parent name first.

Can I unwrap a subname?

Yes, you can unwrap a subname, provided the CANNOT_UNWRAP fuse has not been burned on that subname.

If I create subnames on a wrapped parent name, are they wrapped or unwrapped?

Wrapped parents create wrapped subnames; unwrapped parents create unwrapped subnames. Changing the parent's status doesn't affect existing subnames—they keep their original state.

What happens to subnames if I transfer the parent name?

Subnames stay linked to their parent name. Transferring the parent gives the new owner control over its subnames. Subnames keep their existing profile records and Manager from the time of transfer. The new parent owner can reassign the Manager to themselves, update records, or delete the subname if needed.

The exception is for wrapped names where certain Fuses (such as PARENT_CANNOT_CONTROL) have been burned - in these cases, the parent may not have permission to modify or delete the subname. In all cases, subnames do not automatically update when the parent name is transferred.

Did this answer your question?