Tally.so + Webflow: forms that convert (complete guide 2026)

Webflow forms do the job for simple cases: an email field, a basic contact form, a newsletter signup. But as soon as requirements get more complex (multi-step, conditional logic, file uploads, payments, integrations), the limits show up fast. It's not a bug: Webflow isn't a form builder, it's a website creation platform.

The typical reflex is to look for a plugin or a workaround. But the cleanest solution is often the simplest: use a dedicated form tool, and embed it in Webflow. Tally.so has become a go-to choice for this, because it combines simplicity, power, and a native embed integration that works well inside Webflow.

This article explains when and why to use Tally with Webflow, how to integrate it concretely, how to track conversions, and which best practices to apply so your forms generate results.

‍

What is Tally (and why it works)

Tally is an online form builder that lets you create advanced forms without writing code. The interface looks like Notion: you type, you structure, you add blocks (text fields, multiple choice, file uploads, payments, conditional logic, calculations). The form is ready in minutes, hosted on Tally, and embeddable anywhere via a link or an embed code.

What sets Tally apart from most alternatives is its pricing model. The free plan is generous: unlimited forms, unlimited responses, conditional logic, file uploads, basic integrations. Premium features (custom domain, branding removal, payments, advanced integrations) are available on the paid plan, but the free tier already covers the majority of needs for an SMB or marketing team.

The other strength of Tally is the quality of the respondent experience. Forms are fast, clean, and well adapted to mobile. No cluttered design, no excessive loading time. It's a tool that does one thing well, and does it simply.

‍

Tally vs Webflow: who does what

Webflow and Tally are not competitors. They complement each other. Webflow is excellent for building a fast, structured, performant site with a flexible CMS and full design control. Tally is excellent for building advanced forms with logic, steps, integrations, and a UX designed for conversion.

The problem many teams encounter with Webflow's native forms is that they're designed as a site component, not as a standalone conversion tool. They work well for simple cases, but they hit their limits as soon as the need goes beyond a standard contact form.

‍In short: for a simple contact form fully integrated into the site design, Webflow forms are enough. For everything else (multi-step, logic, files, payments, integrations, qualification), Tally is a natural complement.

‍

When to use Tally (concrete use cases)

B2B lead generation (audit, quote, brief intake)

This is the most common use case. An SMB or agency offering an audit, a quote, or a discovery call needs a form that qualifies the prospect upfront. With Tally, you can ask the right questions across multiple steps (industry, budget, goal, timeline), display conditional fields based on answers, and send everything directly to Notion, a Google Sheet, or your CRM via Make or Zapier.

The result: the sales team receives pre-qualified leads with context, instead of a bare "name + email + vague message."

Multi-step forms and progressive qualification

Long forms scare visitors away. The solution isn't to remove fields, but to spread them across multiple steps. Tally lets you create native multi-step forms with a progress bar, and show or hide questions based on previous answers.

This is useful for complex quote requests, creative briefs, program signups, or any situation where you need to collect a lot of information without overwhelming the visitor.

File uploads

File uploads on Webflow forms exist, but they're limited by the hosting plan: file size and total storage depend on the plan you're on. For some SMBs, these limits are a real constraint, especially when the form asks for heavy documents (mockups, specifications, CVs with portfolios).

Tally handles uploads natively, with up to 10 MB per file on the free plan and more on the paid plan. Files are stored by Tally, not on your Webflow hosting. It's a clean and reliable workaround.

Payment forms

If you need to collect a payment within a form (deposit for an audit, paid event registration, micro-product purchase), Tally offers a native Stripe integration on the paid plan. The visitor fills out the form and pays in the same flow, without being redirected to an external page.

It's a simple alternative to Webflow Commerce for cases where you don't need a full store, just a one-off payment touchpoint.

Recruitment and job applications

A job application form often needs text fields, dropdowns, file uploads (CV, cover letter, portfolio), and sometimes conditional logic (showing different questions depending on the selected role). Tally covers all of this, and responses can be sent automatically to Notion or a Google Sheet for the HR team to process.

Support, bug reports and feedback

For SaaS companies or agencies managing client projects, a structured bug report or support request form is more effective than a free-form email. With Tally, you can ask for a description, a screenshot (upload), a priority level, and route the response to Slack, Notion, or a project management tool.

Feedback forms (NPS, satisfaction, post-project review) follow the same logic: short questions, conditional logic to dig deeper if the score is low, and direct integration to whatever tracking tool you use.

‍

Integrating Tally into Webflow (step by step)

The integration works via embed. Tally generates a code snippet that you paste into an HTML embed block in Webflow. Here's how to do it.

Create the form in Tally

Build your form in the Tally interface. Configure the fields, conditional logic, integrations (where to send responses), and the confirmation page. Test it in preview to verify the flow.

Get the embed code

In Tally, click "Share" then "Embed." Tally offers several options: a standard embed (iframe), a popup embed, or a slider embed. For integration into a Webflow page, the standard embed is the most common. Copy the code provided.

The code looks like this (the URL and parameters will vary depending on your form):

<iframe data-tally-src="https://tally.so/embed/YOUR_ID?alignLeft=1&hideTitle=1&transparentBackground=1&dynamicHeight=1" loading="lazy" width="100%" height="500" frameborder="0" marginheight="0" marginwidth="0" title="Your form"></iframe><script>var d=document,w="https://tally.so/widgets/embed.js",v=function(){"undefined"!=typeof Tally?Tally.loadEmbeds():d.querySelectorAll("iframe[data-tally-src]:not([src])").forEach((function(e){e.src=e.dataset.tallySrc}))};if("undefined"!=typeof Tally)v();else if(d.querySelector('script[src="'+w+'"]')==null){var s=d.createElement("script");s.src=w,s.onload=v,s.onerror=v,d.body.appendChild(s)}</script>

‍


Paste into Webflow

In the Webflow Designer, add an "Embed" component (HTML embed) where you want the form to appear on your page. Paste the Tally embed code. Publish the site to see the final result (the embed isn't visible in the Designer's edit mode, only on the published site or in site preview).

UX recommendations

Width. Place the embed inside a container with a width suited to the form. A form that's too narrow (less than 400 px) is hard to use on desktop. A form that's too wide loses readability. A width of 600 to 800 px works well in most cases.

Height. If you use the dynamicHeight=1 parameter in the embed URL, Tally automatically adjusts the iframe height to match the content. This is recommended to avoid internal scrollbars. If you set the height manually, test the entire form to make sure everything is visible without scrolling.

Responsive. The Tally embed is responsive by default. Test on mobile to make sure fields, buttons, and steps are usable without zooming. If the form is embedded in a section with tight margins, adjust the container padding in Webflow.

Appearance. Tally offers customization options (colors, font, transparent background). The transparentBackground=1 parameter lets the form blend visually into your Webflow page without a style break. Match the form colors to your brand guidelines for a seamless look.

Where to send responses

Tally offers direct integrations with Notion, Google Sheets, Airtable, Slack, and HubSpot. For more complex workflows, use Tally's webhooks with Make (formerly Integromat) or Zapier: each submission triggers a scenario that can send an email, create a task, update a CRM, or notify a team.

The choice depends on your existing stack. If your team works in Notion, send responses to a Notion database. If you use a Google Sheet as a mini-CRM, connect it directly. The key is that responses land where someone actually processes them, not in a Tally dashboard no one checks.

‍

Tracking: measuring submissions and performance

Embedding a form without measuring its completion rate is flying blind. Here's how to track submissions from a Tally form integrated into Webflow.

Tally event listeners

Tally provides JavaScript events that fire at key moments in the form journey: open, submission, close (for popups). You can listen for these events and trigger analytics actions.

The main event is Tally.FormSubmitted. Here's a simple listener example to place in your Webflow page's custom code (in the page or project footer code):

<script>window.addEventListener('message', function(e) {  if (e.data && e.data.event === 'Tally.FormSubmitted') {    // send event to Google Analytics 4    if (typeof gtag === 'function') {      gtag('event', 'form_submission', {        'event_category': 'tally',        'event_label': e.data.payload.formId      });    }    // or push to GTM via dataLayer    window.dataLayer = window.dataLayer || [];    window.dataLayer.push({      'event': 'tally_form_submitted',      'tally_form_id': e.data.payload.formId    });  }});</script>

‍This script listens for messages sent by the Tally iframe. When a form is submitted, it triggers an event in Google Analytics 4 or in the Google Tag Manager dataLayer. You can then use this event as a conversion in GA4 or as a trigger in GTM.

Tracking via Tally integrations

If you don't want to touch code, Tally's integrations provide indirect tracking. Each submission sent to a Google Sheet, a Notion database, or a webhook creates a record you can count and analyze. It's not real-time tracking like an analytics event, but it's enough to monitor volume and response quality.

Calculating the completion rate

To estimate your form's completion rate, divide the number of submissions (Tally responses) by the number of visitors to the page containing the form (available in Google Analytics or Webflow stats). If your page gets 1,000 visitors per month and Tally records 40 submissions, your rate is 4%. That's the metric you track to evaluate whether your optimizations are working.

‍

Best practices to increase form conversion

A good form isn't just about having a good tool. It's a combination of structure, clarity, and friction reduction. Here are the rules that have the most impact.

Reduce friction to the minimum

Every field is an obstacle. Every step is a moment where the visitor can decide it's not worth the effort. Ask yourself for each field: do I actually need this right now, or can I collect it later? A first-contact form doesn't need a phone number, company name, job title, budget, and a message. Name, email, and one open question are enough in most cases to start the conversation.

Use steps for long forms

If you need a lot of information, don't ask for it all on a single page. Spread it across 3 to 5 short steps, with a visible progress bar. The visitor moves forward step by step instead of facing a wall of fields. On Tally, multi-step forms are native and simple to set up.

Leverage conditional logic

Only show relevant fields. If the visitor selects "e-commerce" as their project type, display the e-commerce-related questions. If they select "brochure site," skip straight to the next section. This reduces the number of visible fields, personalizes the journey, and increases the completion rate.

Polish the micro-copy

The text around and inside the form matters as much as the fields themselves. Labels should be clear and short. Placeholders should give a concrete example, not rephrase the label. The submit button should indicate what happens next ("get my audit" rather than "submit"). And the confirmation page should reassure: "we'll get back to you within 24 hours" is more useful than a generic "thank you."

Think mobile first

More than half of visitors will fill out your form on mobile. Systematically test on a real phone: are the fields large enough to tap with a thumb? Do the dropdowns work? Is the submit button visible without scrolling? Tally is well adapted to mobile by default, but the layout of the Webflow page containing the embed can create issues if margins and the container aren't designed for small screens.

‍

Conclusion

Webflow builds great websites. Tally builds great forms. Used together, they cover a wide range of needs without adding complexity to the tech stack: the site stays fast, managed, and autonomous for the marketing team, and the forms gain power, flexibility, and integrations.

If your current forms are a friction point (low completion rate, lack of qualification, upload or integration limitations), testing Tally on a concrete use case takes less than an hour. And if you want to go further on optimizing your conversion journeys on Webflow, we can talk about it.