Open the Subnames tab on your name, click + New Subname, give it a label, and approve in your wallet. That gives you something like pay.yourname.eth — free except for gas. Deleting a subname is the same flow in reverse.

Good to know

The Manager is the wallet that controls a name's records — it can change the ETH Address, set text records, and so on. For wrapped names, the Manager role is merged into the Owner role. Only the Manager can create or delete subnames.
Needs ETH on Ethereum Mainnet for gas — no other cost.
There's no cap on how many subnames you can create.
Subnames can create their own subnames (sub.sub.name.eth).
Subnames have only a Manager — ownership stays with the parent name.
The ENS App only handles .eth names and onchain subnames. For project subnames like base.eth or uni.eth, use the project's own site. See What are project subnames?

Create a subname

Open the Subnames tab. Go to app.ens.domains and connect your Manager wallet. Search for your name, then open the Subnames tab.
Click + New Subname and enter the label you want. That's the part before your name — pay makes pay.yourname.eth.
Add profile records (optional). Click + Add More to Profile to preload addresses or text records on the new subname. That adds a second transaction after the subname is created. Click Next to continue, or Skip to do it later.
Approve in your wallet. Most confirm in 1–2 blocks (12–24 seconds); busy networks can take longer. If you added profile records, approve the second transaction too.

Your subname appears in the Subnames tab once it's onchain.

Delete a subname

Open the subname in the ENS App (search for sub.yourname.eth).
Click Delete subname on its profile.
Approve in your wallet. When the transaction lands, the subname is gone.

If the Manager of the subname is someone other than you, the parent owner can reassign the Manager role to themselves first, then delete.

How subnames fit together

When you register a .eth name like ens.eth, you're registering a second-level name under .eth. Once you own it, you can create subnames under it (sub.ens.eth), and those subnames can create their own subnames (sub2.sub.ens.eth), and so on. There's no depth limit and no fee per level — just gas on each transaction.

Each subname links back to the parent. Records on the subname live on the parent's Resolver. The parent name keeps ultimate ownership; each subname has only a Manager role.

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 and then delete.

Why don't I have a Manager?

Wrapped names don't have a separate Manager field — the Manager role is merged 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 can I do with the Name Wrapper?

The Name Wrapper is an advanced tool. It lets you burn fuses on a name to lock certain permissions — like preventing the parent from controlling a subname. Think carefully before burning any fuses, and consider waiting for ENSv2 deployments. For more, see articles in our Advanced: Name Wrapper section.

Can I wrap a subname if the parent isn't wrapped?

Yes, but there's no point. Name Wrapper fuses on a subname only work if the parent name is wrapped first.

Can I unwrap a subname?

Yes, as long as the CANNOT_UNWRAP fuse hasn't been burned on that subname.

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

Wrapped parents create wrapped subnames; unwrapped parents create unwrapped subnames. Changing the parent's wrap status later doesn't change existing subnames — they keep whatever state they were created in.

What happens to subnames if I transfer the parent name?

Subnames stay linked to their parent. Transferring the parent gives the new owner control over its subnames, including the option to reassign the Manager, update records, or delete subnames.

The exception is wrapped names where certain fuses have been burned (like PARENT_CANNOT_CONTROL) — in those cases the parent loses some permissions over the subname. Either way, subnames don't automatically update when the parent is transferred.