A waitlist page has one job and everybody adds three. The job is to collect an address from someone who cannot use the product yet, which means the page has to make them want something they cannot have and then get out of the way.
24 components on 21st carry the waitlist tag. Here is the short version of what works.
The page
Waitlist Hero by Le Thanh is the most-taken one: the email capture built into the hero rather than bolted underneath it, which is the whole difference. Waitlist Landing Page with Countdown Timer by M.bin Salman adds a deadline, Waitlist Form by preetsuthar17 and Waitlist by Ayushmaan Singh are the standalone forms, and Coming Soon Waitlist Page by 7Ovr is the full page.
One field
Email. Not name, not company, not role, not "how did you hear about us". Every additional field costs sign-ups, and everything you wanted to ask can be asked in the first email, where the person has already committed and is far more likely to answer.
The exception is a genuine qualifier that changes who you let in first. If it does not change the order of the list, it is not a qualifier, it is curiosity.
What the page has to say
Three things, and most waitlist pages ship one.
What it is. "Join the waitlist" above a logo tells the reader nothing. One sentence about what the product does, and one about who it is for.
Why now. A waitlist is a request to remember you. A reason - limited early access, a launch date, a founding price - is what converts an interested reader into an address.
What happens next. When they will hear, and roughly how many people are ahead of them if you are willing to say. Silence after signing up is what makes a waitlist feel like a void.
The confirmation
The most under-built screen in this pattern. The form submits, the button spins, and then... the same page with a small green tick.
What should happen: replace the form with a real confirmation that states what they signed up for and when to expect something. Send the email immediately, because an inbox confirmation is what makes it feel real. And give them something to do - a referral link, a Discord, a related post to read - because the moment straight after signing up is the highest-intent moment you will get from that person for weeks.
Referral positions ("move up the list by inviting people") work well enough that they are worth building if the list is your main channel, and they are pure overhead if it is not.
The mechanics
Store it somewhere you can email from. A form that writes to a spreadsheet nobody has connected to an email tool is a list you cannot use.
Double opt-in if you plan to send marketing. It costs some sign-ups and it protects your sending reputation, which matters more the moment you have thousands of addresses.
Handle duplicates gracefully. Someone signing up twice should be told they are already on the list, not shown an error.
Rate-limit and validate server-side. An open form with no protection collects bot addresses that will wreck your deliverability on the first send.
The countdown, honestly. A timer that resets when it hits zero is the fastest way to lose everyone you collected. Only ship one if the date is real.
Where else to look
The honest list, because the answer is not always us:
| Source | Best for | Trade-off |
|---|---|---|
| A waitlist service | Referrals, positions and the emails, hosted | A subscription and their branding on the flow |
| An email platform's embedded form | The list living where you will send from | Their markup and styling constraints |
| shadcn/ui | Input, Button and Form underneath your own page | You build the flow |
| 21st | Waitlist heroes, countdown pages and standalone forms | Quality varies by author, so preview before you take it |
Taking one
Every component page has a live preview and the code. Installing goes through the shadcn CLI against our registry:
That key comes from your 21st account, and installs require a membership. Set API_KEY_21ST once in your shell and the command works for anything in the catalogue. The 21st MCP covers the same ground without leaving the editor: ask Claude, Cursor or Codex for a waitlist page, get the previews inline, and let the agent write the file.
Frequently asked
- How many fields should a waitlist form have?
- One: email. Every additional field costs sign-ups, and anything else you want to know can be asked in the first email, where the person has already committed. The only exception is a genuine qualifier that changes who gets in first; if it does not change the order, it is curiosity.
- What should a waitlist page say?
- What the product is and who it is for, why to join now rather than later, and what happens next. Join the waitlist above a logo tells a reader nothing, and silence after signing up is what makes a list feel like a void.
- What should happen after someone signs up?
- Replace the form with a real confirmation stating what they joined and when to expect something, send the email immediately, and give them one thing to do next, such as a referral link or something to read. The moment after signing up is the highest-intent moment you will get from that person for weeks.
- Is a countdown timer a good idea on a waitlist page?
- Only if the date is real. A timer that resets when it reaches zero is the fastest way to lose the trust of everyone already on the list, and it is visible to anyone who returns.