# Formatting/Validation option for phone & email fields

**URL:** <https://community.fibery.io/t/formatting-validation-option-for-phone-email-fields/9511>\
**Category:** Ideas & Features\
**Created:** [September 1, 2025, 11:34pm UTC](https://community.fibery.io/t/formatting-validation-option-for-phone-email-fields/9511 "2025-09-01T23:34:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\
**Post date:** [September 1, 2025, 11:34pm UTC](https://community.fibery.io/t/formatting-validation-option-for-phone-email-fields/9511/1 "2025-09-01T23:34:10Z")

</div>

Is it possible to add phone number formatting option so that users phone inputs are consistent and accurate? This is super helpful for CRM applications and would ensure that country codes and phone numbers are correctly entered. There are already a few libraries for this purpose which hopefully can be adopted.

I was also wondering if email and URL fields could have an option of formatting input into lowercase. It would be creator selectable and would help those with OCD maintain consistency 🙂

---

<div class="post-metadata">

**Author:** ![Sev](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@Sev](https://community.fibery.io/u/Sev)\
**Post date:** [September 2, 2025, 1:05am UTC](https://community.fibery.io/t/formatting-validation-option-for-phone-email-fields/9511/2 "2025-09-02T01:05:33Z")

</div>

I agree that a phone or email format should inherrently mean some **validation checks** , particularly in form view where it is exposed to the public; otherwise in the UI, it is just a text field that can link to its value (tel: or mailto:), and optionally has a button display.

> [@cannibalflea](#):
>
> I was also wondering if email and URL fields could have an option of formatting input into lowercase.

As for this, I do not see it as a good idea, since parts of URLs and email addresses, by RFC Standards are allowed to be **case-sensitive** (though most servers implement them fully case-insensitively). In other words, theoretically an email address or URL could break if the case is changed, though in practise this would be highly improbable.

---

<div class="post-metadata">

**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\
**Post date:** [September 2, 2025, 5:29am UTC](https://community.fibery.io/t/formatting-validation-option-for-phone-email-fields/9511/3 "2025-09-02T05:29:00Z")

</div>

The format would need to be thought out. Formats are different in different countries. Do we use full number with country code and + sign, like +15555555555? Or USA format (555) 555-5555? Or where I live the format is 0555 555 555. I agree that formatting is nice, but it would be helpful to clarify what formats we are talking about.

---

<div class="post-metadata">

**Author:** ![Sev](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@Sev](https://community.fibery.io/u/Sev)\
**Post date:** [September 2, 2025, 1:35pm UTC](https://community.fibery.io/t/formatting-validation-option-for-phone-email-fields/9511/4 "2025-09-02T13:35:11Z")

</div>

I agree, though the issue here is not formatting, but validation. To begin with, it could something basic like very **forgiving/permissive** regular expressions, to at least **ensure something close to a valid email or phone number** is input, **without blocking non-standard user inputs**.

As a more developed feature, it would be nice to allow architects to use formulas for validations, where we could set up our own regular expressions, or other logic.