Add a form to your website without building a backend

A contact form or a subscribe box, designed on the canvas along with the rest of the page, and the answers arrive in your inbox. There is no server to run and nothing to wire up.

Start for free -> See the plans

The short answer.

You draw the form where you draw the page, and what people send you turns up as email. Every plan carries a forms allowance and the number is the only thing that moves between them. The one thing that decides whether a form does anything at all is publishing, and on the free plan the answer to that is short. No — the free plan builds and previews privately; publishing needs a paid plan, so a form designed there has no public page for anyone to submit it from.

Right tool for this

Enquiries, project briefs, sign-ups, anything that ends with a person reading a message and replying to it. Siter.io describes forms as collecting information from visitors, including subscription and contact details, and that is exactly the shape of job they suit.
Wrong tool for this

Anything where a server has to decide something in response. Signing a person in, taking a payment, looking their order up in a system only you hold. A form collects a message and passes it on. Whether it can do anything more elaborate than that — branching questions, attachments, checks before sending — is not documented, so design for the plain version.

How to build one.

Five steps. The two everybody skips are the last two.
1. Decide what the reply must contain.
2. Cut every field you can.
3. Design the form on the canvas.
4. Publish and send yourself a test.
5. Check the inbox and spam folder.
Where the answers go, and what is not documented

The documented promise is short. Forms collect information from visitors, including subscription and contact details, and the answers reach your inbox. For a marketing site that is usually the whole requirement, and it is worth knowing that it really is the whole requirement before you plan anything more elaborate on top of it.

What is not published anywhere is the detail underneath. Which field types you can place. Whether anything checks what was typed before it is sent, or whether one question can depend on the answer to another. Whether submissions are filtered for spam, whether a visitor can attach a file, whether the destination address can be changed or pointed at more than one person, whether you can download a record of past submissions, and how long they are kept. We are not going to guess at any of it.

So place a form in the app and read what it actually offers before you build a process on top of it. The app is the authoritative source and this page is not. If what you need depends on one of those details — a hiring form that wants a CV attached, a support form that has to land in a shared queue — check it there first and design around what you actually find.

Then submit a real test from the published page, from a device that is not the one you built it on, and look in the spam folder as well as the inbox. A form that silently drops enquiries looks exactly like a form nobody is filling in.

How many you get.

One row, because forms are on every plan and only the count changes. The pricing table counts them across your web pages rather than per page, so a contact form on one page and a subscribe box on another use two of the allowance between them. Start shows a number here too, and it is a design allowance rather than a working form, because that plan does not publish.

Feature	Start (free)	Solo $7	Plus $12	Pro $24
Forms per Website	3	3	5	Unlimited

Read off the “Compare plans” table on siter.io/pricing on 2026-10-08.

Four things worth knowing.

Designing the form is the easy half. What decides whether it was worth having is what happens in the ten minutes after somebody presses send.

Every field costs you replies
A field is a decision, and each one is another moment a visitor can decide this is not worth it. The test for keeping a field is simple. If knowing the answer would not change what you do next, it does not belong on the form.
Contact and subscribe are different jobs
One asks for a message and expects a reply. The other asks for permission to send something later, and should say what and how often. They belong in different places on the site, and a subscribe box is not a mailing list on its own. The addresses land in a mailbox and you still need something to send them.
Keep an address next to the form
Some people will not use a form at all, and some want a copy of what they sent in their own outbox. Show a plain email address people can copy alongside it. That is one line of markup and it catches the enquiries a form would have quietly lost.
Know which mailbox gets them
Answers arrive as email, so the enquiries live in whichever mailbox receives them. Check in the app which address that is, and whether it can be a shared one, before the first good lead sits unread in somebody's holiday inbox.

Frequently asked.

How do I add a contact form to my website?

You design it on the canvas the way you design the rest of the page, publish the page, then submit a test entry yourself and confirm it arrives. Because the form is part of the layout rather than an embedded widget, it takes your type and spacing instead of arriving with a third party’s styling attached to it.

Where do form submissions go?

To an inbox. Siter.io describes forms as collecting information from visitors, including subscription and contact details, and says the answers arrive in your inbox. Which address that is, and whether it can be changed or sent to more than one person, is not documented publicly, so check it in the app before you build a routine around it. Every submission is also kept on the form’s Entries page in the app, private to your site’s team, where each one’s answers show at a glance and you can select several and remove them together.

How many fields should a contact form have?

As few as let you reply properly. Usually that is a way to reach the person and the message itself, plus a name if you want to open the reply with one. Ask for a phone number, a company size or a budget only when the answer changes what you would do next. Otherwise you are trading replies for data you will never look at.

Do I need a backend or a server for a website form?

Not to collect messages. The page can be entirely static and the submission still reaches you as email, which covers enquiries, briefs and sign-ups. You need an actual application the moment the server has to decide something in response, such as signing a person in, charging them, or looking up an order. That is a different kind of product, not a form on a marketing page.

How many forms can I have on Siter.io?

3 on Solo, 5 on Plus, and unlimited on Pro. The free Start plan lists 3 as well, but it publishes nothing publicly, so those are a design allowance rather than working forms. The count runs across your web pages rather than per page, so two pages carrying one form each have used two of the allowance, not one.

Can I use forms on the free plan?

You can design them, and the plan lists an allowance of 3. Whether you can collect anything with them is a different question. No — the free plan builds and previews privately; publishing needs a paid plan, so there is no public page for a visitor to submit from. Publishing starts from $7/mo billed yearly, and the forms allowance on that plan is the same 3 as the free one.

How do I stop spam from a website contact form?

Not documented, and we are not going to claim it either way. There is no published statement about spam filtering, attachments or validation on Siter.io forms. Treat the first week of a new public form as a trial. If junk starts arriving, that is the moment to ask support what the options are, rather than to assume there are none.

Can I export the answers or send them to another tool?

Not documented. Whether past submissions can be downloaded, how long they are kept, and whether answers can be pushed into a spreadsheet, a CRM or a mailing tool is not stated anywhere public. If your process depends on any of that, ask before you build it, and until you have an answer treat your inbox and the Entries page as the record you can count on.

Where should a subscribe form go?

Wherever somebody has just finished reading something of yours, which is the only moment they have evidence you are worth hearing from again. That means the end of a piece of writing or a project page, not the contact page. Keep the contact form on the contact page, doing the other job, and word the two differently.

More of what the editor does

Also useful: Siter.io pricing in full and every feature, plan by plan.

Design the form where you design the page.

A form built into the layout inherits your type and spacing instead of arriving with somebody else's styling attached. The free plan builds and previews as much as you like; publishing the page so people can actually submit it needs a paid plan.
Get the plugin ->
Start for free with Siter.io
Start for free ->