Good to Know
Creating and deleting subnames requires only gas fees (ETH on Ethereum Mainnet).
The Manager can create and delete subnames. For wrapped names, the Owner role has Manager permissions.
Creating a subname costs only gas—no registration fees.
There's no limit to how many subnames can be created.
Subnames can create their own subnames too.
Subnames have only a Manager role—ownership stays with the parent name.
The ENS App currently supports management of .eth names and their onchain (Ethereum) subnames only. Offchain subnames and subnames from specific projects on L2s (for example, base.eth subnames such as <sub>.base.eth) use their own custom contracts and frontends, and should be managed through those platforms.
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
Step 1: Select New subname
Navigate to the ENS App.
Connect your wallet.
Search for your name and open the Subnames tab.
Click + New Subname.
Step 2: Label the New Subname
Enter the label for your new subname. No registration fees, no limits—just gas costs.
Step 3: Prepare the Profile (Optional)
Add addresses and profile records now, or skip this and add them later. See How to Edit Profile. Click Next once you're ready.
In this example, an ETH Address has been added
Step 4: Confirm the Transaction to Create the Subname
Click Open Wallet and confirm the transaction.
Your subname is now created.
Step 5: Confirm the Transaction to Update Profile (If Applicable)
If you added profile records, a second transaction prompt will appear.
Click Open Wallet and confirm the transaction.
Your subname profile is now updated.
In this example, the ETH Address is added to the name
How to delete a subname
Step 1: Select Delete Subname
Navigate to the ENS App.
Connect the Manager wallet.
Search for the subname and open the Profile tab.
Click Delete subname.
Step 2: Confirm the Transaction
Click Open Wallet and confirm the transaction.
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. See Name Wrapper Overview.
What subnames can I create with the Name Wrapper contract?
You can create subnames on both unwrapped and wrapped names. The Name Wrapper contract turns these subnames into ERC-1155 NFTs. Read more in the Name Wrapper Overview, and review other articles in the Name Wrapper Collection. For specific subname use cases utilising Name Wrapper permanent Fuses, see Sell or Rent Subnames, Give subnames out to NFT holders and Issue subnames as tickets
Can I wrap a subname if the parent is not wrapped?
Yes. But to use Name Wrapper Fuses on the 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.