# Autocomplete="off" for some fields

**URL:** <https://community.noloco.io/t/autocomplete-off-for-some-fields/1569>\
**Category:** Feature Requests\
**Created:** [December 30, 2024, 4:32pm UTC](https://community.noloco.io/t/autocomplete-off-for-some-fields/1569 "2024-12-30T16:32:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thomas](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/thomas/32/1287_2.png) [@Thomas](https://community.noloco.io/u/Thomas)\
**Post date:** [December 30, 2024, 4:32pm UTC](https://community.noloco.io/t/autocomplete-off-for-some-fields/1569/1 "2024-12-30T16:32:42Z")

</div>

Hi everyone,

While building my app, I’ve encountered an issue where browsers automatically autofill fields (e.g., fields where sensitive information is entered). This behavior can be problematic, as it pre-populates fields with previously entered data, which might confuse users or cause incorrect information to be submitted.

To address this, I’d like to suggest a feature that allows us to disable browser autofill for specific fields (with autocomplete=“off” per exemple).

Is this something that could be considered in a future update? Thanks for your attention to this!

---

<div class="post-metadata">

**Author:** ![Xaver](https://avatars.discourse-cdn.com/v4/letter/x/b4bc9f/32.png) [@Xaver](https://community.noloco.io/u/Xaver)\
**Post date:** [January 7, 2025, 8:18pm UTC](https://community.noloco.io/t/autocomplete-off-for-some-fields/1569/2 "2025-01-07T20:18:09Z")

</div>

Big +1 from me, I ran into the same issue when trying to passcode lock record visibility. I ended up using 4 single select fields with numbers, but that’s only a solution for that specific case.