tally.so Paid content

What is Tally?

Tally is a free online form builder that works like a text document: you type questions directly on the page and insert input blocks, similar to writing in Notion, without coding. It is designed for people who need surveys, quizzes, lead-generation forms, contact forms, or checkout forms and want to build them quickly rather than configure a complex tool.

Its core appeal is simplicity plus a generous free tier. The site advertises unlimited forms and submissions for free within fair usage guidelines, no signup required to create a form, and a block-based editor. Beyond basic text and contact fields, it supports file uploads, e-signatures, payments, ratings and rankings, and date/time inputs. Smart features include conditional logic to show, hide, or branch questions, a calculator for scores or prices, and hidden fields for passing URL parameters such as UTM data.

Tally also positions itself as privacy-friendly: GDPR compliance, European hosting, no cookie tracking, and encryption in transit and at rest. That makes it a reasonable fit for teams handling personal data who want a lighter-weight alternative to enterprise form suites.

Who it suits

• Solo founders, marketers, and researchers who want a form live in minutes.
• Teams already comfortable with document-style editing.
• Anyone collecting sensitive data who cares about hosting location and tracking.

Trade-offs to weigh

• The document-style editor is fast for straightforward forms but may feel limited if you need highly custom layouts or deep integrations.
• Free unlimited submissions come with fair usage guidelines, so very high-volume use may require checking the terms.
• Payments and signatures are supported, but complex payment logic or contract workflows may still need a dedicated tool.

A practical next step: open Tally, start typing a real form you need this week, and test one conditional-logic question and one file upload. If those behave as expected, compare it against Typeform or Jotform only if you specifically need their advanced integrations or branding options.

How does Tally's free plan work and what are its fair usage limits?

Tally's free plan is built around a simple promise: unlimited forms and unlimited submissions at no cost, as long as your usage stays within the company's fair usage guidelines. There is no paywall on the core form builder, and you can start typing questions directly on the page without writing code. You can even begin building before creating an account, since the site says no signup is required to start a form.

What you get on the free plan

• Unlimited forms and submissions, subject to fair usage guidelines
• A document-style editor where you type questions and insert blocks
• A wide range of free input blocks: contact details, file uploads, signatures, payments, ratings, rankings, dates and times
• Smart features such as conditional logic, calculated values, hidden fields and URL parameters for pre-filling or personalising forms
• GDPR-compliant hosting in Europe with encryption in transit and at rest, and no cookie-tracking

What "fair usage" means in practice

The site references fair usage guidelines but does not spell out numeric thresholds in the material available. The practical reading is that the free plan is designed for normal business and personal use, not for extreme volumes or abusive automation. If your forms generate unusually heavy traffic, you may be asked to move to a paid arrangement. For exact ceilings, check the pricing page at Tally Pricing, since limits can change.

Who this suits, and the trade-off

The free plan fits freelancers, small teams, community organisers and anyone running surveys, quizzes, lead-generation forms or simple checkout forms who wants to avoid per-response fees. The trade-off is that "unlimited" is qualified by fair usage, so very high-volume or commercial-scale operations should verify their expected load against the current guidelines before committing. Privacy-conscious teams in Europe also get a concrete benefit from the European hosting and lack of cookie-tracking.

Next step

Open Tally and start typing a test form to see how the block editor feels, then read the fair usage guidelines and pricing page before you rely on it for a high-traffic campaign.

Can I use Tally to accept payments and collect e-signatures without writing code?

Yes. Tally's page lists both payments and signatures as built-in input blocks, so you can add them to a form the same way you add a name or email field — no code required.

What that looks like in practice

• Payments: Tally describes "checkout forms without code," meaning you build the order or donation form visually and connect a payment step through the block rather than writing an integration.
• E-signatures: The signature block is positioned for contract signing and similar approval flows, so a client can sign inside the form itself.
• Both in one flow: A freelancer could build a single form that collects contact details, a signed agreement, and a deposit payment — then use conditional logic so the payment step only appears after the signature is complete.

Where the trade-offs sit

The no-code approach covers standard collection and signing. What it doesn't replace is a full contract lifecycle: version control, counter-signatures from your side, audit trails with legal weight, or automatic reminders on unsigned documents. If you need those, expect to pair Tally with a dedicated e-signature service. On payments, the form collects the payment; the money still flows through whatever payment provider you connect, so fees and payout timing come from that provider, not Tally.

Next step

Open Tally and add a signature block and a payment block to a test form, then submit it yourself. That single dry run tells you whether the signing order and payment trigger behave the way your workflow needs before you send it to a real client.

How does Tally's form builder work like a text document compared to traditional drag-and-drop builders?

Tally treats the form canvas like a blank document: you click on the page and start typing, and each question becomes a block you can move, duplicate or delete. Instead of dragging field types from a sidebar onto a grid, you type the question directly and insert blocks (multiple choice, file upload, payment, signature, rating) where the cursor sits — similar to writing in Notion. Formatting, reordering and branching happen inline rather than through a separate layout panel.

How that differs in practice

The trade-off is flexibility. Document-style builders are fast for linear forms and keep you focused on wording, but they give you less control over multi-column layouts or precise visual placement. Drag-and-drop builders suit marketing pages where the form must match a designed layout, at the cost of more setup time.

Tally's page evidence also notes conditional logic, a calculator with variables, and hidden fields for passing URL or UTM data — so the simple typing surface doesn't mean the logic has to stay simple. It states unlimited forms and submissions under fair usage guidelines, and says the tool is GDPR compliant and hosted in Europe.

Next step: if you're deciding between the two approaches, sketch your form as plain text first. If it reads naturally as a linear list of questions, a document-style builder will get you there faster; if it needs side-by-side fields or a branded layout, a drag-and-drop canvas is the better fit. For a second opinion on the document-style category, see Notion.

How does Tally handle data privacy and GDPR compliance for form submissions?

Tally states that it is GDPR compliant, hosts its service in Europe, avoids cookie-tracking, and encrypts form data both in transit and at rest. Those are the core privacy commitments it makes on its own site, and they matter most to teams collecting personal data from EU respondents.

Tally

H3 What this means in practice

• Europe-based hosting reduces the number of legal jurisdictions your submission data crosses, which simplifies GDPR transfer questions.
• Encryption in transit and at rest protects responses while they move between respondent and server, and while stored.
• No cookie-tracking on forms means you are less likely to need a cookie banner or consent flow just for the form itself.
• GDPR compliance claim is the vendor's own statement; for regulated industries you should still confirm the specifics your legal team needs, such as a data processing agreement, subprocessor list, retention controls, and where backups live.

H3 Who should care most

If you run surveys, lead forms, or checkout forms that collect names, emails, addresses, signatures, or payment details from EU residents, these defaults reduce setup work. A small marketing team can publish a form without bolting on a separate consent tool, while a healthcare or finance team will still want to verify retention and deletion options before going live.

H3 A useful next step

Before launching, collect one real submission and check three things: whether the form shows any tracking notice, where the response appears in your workspace, and whether you can delete it on request. If your compliance officer needs paperwork, request the data processing agreement and subprocessor list directly from Tally.

For a broader comparison of privacy positioning, you can also review how other form tools describe their data handling, such as Typeform or Jotform.

What advanced features like conditional logic and calculators does Tally offer for creating dynamic forms?

Tally's dynamic-form features revolve around three ideas: changing what a respondent sees based on their answers, calculating values from those answers, and personalizing the form with data passed in from outside. All three are described as part of Tally's standard form builder rather than separate add-ons.

Conditional logic

Build branching into a form so later questions depend on earlier answers. You can show or hide blocks, route respondents down different paths, and calculate values that feed into the form's behaviour. In practice, this is what separates a flat questionnaire from something closer to an interview: a respondent who says "no" to a qualifying question skips the follow-up section entirely, while someone who says "yes" gets it.

Calculator and variables

Variables let you compute values from responses — scores, totals, prices, and similar derived numbers. A quiz can tally a score and show it at the end; a quote form can multiply quantity by a rate; a lead form can prioritize or segment respondents based on a computed result. The same variable mechanism supports dynamic content, so text elsewhere in the form can change depending on what has been entered.

Hidden fields and URL parameters

Hidden fields accept data passed through the form's URL, including UTM parameters or known personal details. This is the feature to reach for when the form is embedded in a campaign, sent to an existing contact list, or linked from a specific landing page: you can pre-fill or silently attach context so the respondent isn't asked for something you already know, and so submissions arrive already tagged by source.

How the pieces fit together

A concrete scenario

A small agency wants a project-brief form. Conditional logic asks about budget range only when the respondent selects a paid engagement, skipping it for pro-bono enquiries. A calculator turns selected service options into an indicative price band shown on the final screen. Hidden fields carry the campaign source from the link the client clicked, so the agency can see which outreach produced the brief. One form, three behaviours, no code.

What to weigh

These features reward a little planning. Branching gets hard to audit once a form has many paths, and a calculator is only as trustworthy as the logic behind it — test edge cases such as blank answers and unusual quantities before sending the form to real respondents. If your needs are simple (a contact form, a single survey), you may never touch any of this, and that's fine; the value appears when a single generic form would otherwise force every respondent through questions that don't apply to them.

Start by sketching the paths on paper, then build the branching first and layer the calculator and hidden fields on top. If you want to compare the approach with other builders, Typeform and Jotform are the common alternatives to check against your specific logic requirements.