input validation/REGEX

That would be useful for several use cases: zip code formats, customer numbers, etc.

Thanks so much for the detailed write-up. What you're describing overlaps closely with one of our most-requested features already on the board: custom input validation / regex (forcing text fields to follow a specific format like phone numbers, IBANs, IDs, and so on). I'm merging your request into that one so your vote and notes count together — it's one of our top-voted requests, which really helps us prioritize it. I've made sure your extra details are captured too, especially the dynamic/conditional mask idea (a single field adopting different formats based on earlier selections), since that adds something new to the conversation. Thanks again for taking the time to lay it out so clearly!

Still not in 2026? its been ages since 2023. as basic native implementation as regex pattern attribute matching client side for a progress.

Where are we on this?

This is so critical for our workflow as well. I think a form builder as capable as Tally should have this kind of power-user feature!

THIS IS HIGHLY NEEDED. MY VALIDATION IS A MESS! HELP ANYONE?

Update on this? Isn't this so hard, or not seeing this as a quality of life update 🫤🫤🫤

Hello, when is this being added to the Roadmap ? With Tally AI coming, it would make even more sense since the AI could create REGEX for us !

Hi Quentin, thanks for sharing your feedback with us. Could you please share more details so that our team can review your feedback? Thanks :)

Chiming in to request this as well. This would really help in improving data quality when dealing with formatted data. (IBAN, Social Security number, etc...)

Hi, the significant community interest in input validation with regex (as evidenced by the votes and merged requests) makes its apparent neglect in recent roadmap planning concerning. Features like this are standard in Google Forms, partially offered by MS Forms, and available in numerous other free form alternatives. Could you please provide an update on whether its prioritization is being reconsidered for future development and potential inclusion in the roadmap? Any clarity on the plans to address this important feature gap would be greatly appreciated by the community.

I see this isn't currently on the roadmap but really would like to see it ASAP...I'm really worried about messy data. Will try Tally for now but if my data ends up being messy because user's aren't being guided well enough I'll have to switch to another form builder even though I love everything else about Tally

Hi Tedi Yettison, thanks for this clearly formulated request! I see how you envision this feature and its intended purpose. The workaround you're using with condition logic is smart, but has some limitations as you've experienced yourself. I've merged your request with a similar one that would also solve this problem for you. While I can't make any promises about if or when it might be implemented, rest assured that you'll see updates here if anything changes. Thanks again for your contribution!

Filip Minev Shouldn't be merged with this one ? https://tally.so/feedback/p/key-regex

From a Pro user: We've just added "email address validation" to our form using debounce.io. We were using it at our back-end anyway and they have a JS library that pushes it into your form - just had to paste some JS from their site to your code injection area on the custom domain. Took about 30 seconds in total. I only mention it in case it's something you wanted to add to your docs or somewhere as a potential feature.

Yes I need input validation For us input validation is quite important, we would like to validate: - Zipcodes - Addresses (with an API) - IBANs - Chamber of commerce codes (numbers with a specific length) A regex validation on text inputs would already bring us quite far.

Or check that a date entered is past today /set in the future

or even have email validation for email inputs

We hope to have some progress on this validation. Kindly do asap.

This is very necessary to validate CNPJ and CPF, which in Brazil are standard identifiers.

For a client project I need a way to validate an IBAN input, so the user directly can be made aware if they made an error. This would not be possible just with regex, it would need the possibility for a math formula.

This would be great. REGEX please.

Very important! We cannot use the phone format because our public does not understand the international prefix +55 (for Brazil). a regex validatior would fix this

Hello Ian, Thanks for your request. As a workaround, you can acheive this achieveby adding a logical condition saying that in case the email contain "hotmail / gmail / etc..." , hide the "Next page" button and show an error message. I've made an example for you 👇,

It would be nice to use regex to validate input format.

Second that - input masks have been available in Jotform for ages.