EMAIL CAPTURE
Email capture on a static page
Collect addresses from a page that has no backend, read them in the dashboard, and export them when you want them somewhere else.
Free plan, free SSL, no credit card.
Plan availability
Which plans include email capture
Email capture starts on Business.
- Free Not included
- Starter Not included
- Pro Not included
- Business Included
- Enterprise Included
Read from the plan records this account is billed against, not from a page someone wrote, so it cannot disagree with what happens when you click the button. See every plan and its limits.
What it does
The one thing a static page cannot do on its own
A static page can show a form. It cannot receive what the form sends, because there is nothing running to receive it.
That gap is the reason most "just a landing page" projects end up dragging in a whole platform. Email capture closes it without changing what your page is: the page stays a file you uploaded, and the submission goes to us instead of to a server you would otherwise have to run. Addresses collect against the site they came from, you read them in the dashboard, and you can take them out again whenever you want them in a mailing tool.
It is worth being precise about the scope, because "forms" means very different things to different people. This is address collection for a waiting list, a launch notification or a simple newsletter signup. It is not a form builder with conditional fields, and it does not send the mail for you: what it gives you is the list, which is the part a static page genuinely cannot produce. If you want a link page rather than a full site to do the collecting, the link in bio builder has a block for it.
How to use it
Three steps
-
Put the form on your page
An ordinary form with an email field. You keep your own markup and styling; nothing is injected into the page.
-
Publish on a plan that includes it
Capture starts on Business. Submissions are held against the site they arrived from.
-
Read or export the list
Check what has come in from the dashboard, and export when you want the addresses in a mailing tool.
Where it earns its keep
When people reach for this
A waiting list before the product exists
One page, one field, no infrastructure. This is the case where standing up a server to receive twenty addresses is obviously the wrong amount of work.
A launch notification on a single page site
A date, a description and a way to be told. Publish the page, connect a domain of your own, and it is finished.
A downloadable document behind a name
Ask for an address on the page that links to the PDF. The document itself stays a normal link, so nothing breaks if someone shares it.
The alternative
Doing this without us
There are two normal answers, and both add a moving part that has to keep working.
| Droply | A third-party form service | |
|---|---|---|
| What you add to the page | A form. The page stays a file you uploaded. | An embedded script or an iframe from another domain. |
| Where submissions live | With the site, in the same dashboard. | In a second account with its own login and its own plan. |
| Getting the addresses out | Export whenever you want them elsewhere. | Varies, and export is sometimes a paid tier. |
| Extra cost | Included from Business upward. | A separate subscription on top of hosting. |
Compared against the general pattern of embedded form services rather than one named product. Checked September 2026.
When this is not the right tool
This collects addresses. Anything past that is a job for a tool built for it.
- It does not send email. There is no campaign editor, no scheduling and no delivery reporting.
- It is not a general form builder. Multi-step forms, file uploads inside a form and conditional fields are out of scope.
- There is no double opt-in flow built in, so if your jurisdiction requires one, you will want a mailing tool that runs it.
- You are the controller of the addresses you collect. Say so on your page, and keep your own privacy notice accurate.