Do you need Typeform on a small website?

You published a site on Webflow, Lovable, or a static host. The next suggestion is often “paste a Typeform.”

Open the live page and write down the questions you need answered. That list decides whether you need a form builder.

Start with the questions on the page

A small site usually needs one form.

Name, email, and a message. Or a waiting list email. Or a quote with a project type and a file.

If those fields fit on one or two screens, a form builder is extra machinery. You still need a backend that stores the answer. An embed that only emails you is not enough if you cannot find the file later.

If the form only shows “Thanks” in the browser and stores nothing, connect storage first. Follow the static contact form guide if that is the gap.

A form builder earns its keep on long paths

Typeform and Tally shine when the path is long. One question per screen. Logic that hides a field. A quiz. A payment on the last step.

If you sell a diagnostic, keep Typeform. If the second question depends on the first, keep it too.

If you ask for a name, a project type, and a PDF, you do not need that runtime. A two-step form on your page does the job.

An embed is also a third-party page inside yours. Visitors leave your layout. The thank-you screen is theirs. You add another vendor to the privacy policy.

<iframe
  src="https://form.typeform.com/to/a8K2mQ1p"
  title="Request a quote"
  style="width:100%;height:720px;border:0"
></iframe>

That iframe is fine when you chose the builder on purpose. It is a lot of UI for three fields.

A contact form covers the usual inbound

Name, email, and a message belong on a contact form. Store the row. Reply from one inbox. Export CSV if you want a copy.

Sitebase’s contact form does that. Custom forms cover the next step: your own fields, more than one step, and a file upload. A site can have several custom forms. Quote request and workshop signup stay separate.

You pick the fields. Visitors see “Step 2 of 2” and move with Next and Back. Required fields are checked before they go forward. You can ask for text, email, a dropdown, a date, a URL, a number, or a file.

There is no field-level skip logic. If the second question has to disappear based on the first answer, stay on Typeform.

Sitebase is in private beta. Public signup isn’t open.

The snippet looks like this. Replace YOUR_FORM_KEY with the form key from your dashboard:

<section aria-labelledby="quote-heading">
  <h2 id="quote-heading">Request a quote</h2>
  <script
    async
    crossorigin="anonymous"
    src="https://sitebase.dev/embed.js"
    data-sitebase-widget="YOUR_FORM_KEY"
  ></script>
</section>

If the editor only accepts a URL, use the hosted embed. That is the path on Notion, Wix, or Squarespace.

Turn on Cloudflare Turnstile in the site Config before you share the page. Sitebase also uses a honeypot and a per-visitor rate limit. Follow the CAPTCHA guide if you still need to decide about the puzzle.

Responses land in Data. New rows are bold. Expanding one marks it read. File fields show a download link. Export CSV if you want a copy outside the dashboard. If you already send submissions to Slack, that path is the webhooks guide.

Submit it on the published URL

Open the live page in a fresh window, not the preview.

Send a request with an address you control. Confirm that it arrives in storage. Confirm that an empty required field blocks the next step.

If the form is still an iframe on someone else’s domain, decide whether you want that vendor in the stack. If three fields are enough, put the form on your page.

Then walk the other checks in the launch checklist.