Password Policy You Define
Decide which rules a password has to meet, and let the person watch them tick off as they type.
NWD Password Input (Strength Meter) was built to replace Bubble’s native password input and offers far more styling flexibility and control. It brings a live strength meter, configurable password policies, and a show/hide toggle together in one polished component. Fully customizable through 60+ properties, giving you complete control over every visual and behavioral detail.
Built for what Bubble does not cover.
Bubble's native password field is not a dedicated input. It is one type of a generic input that also does text, number, phone, email and others. It masks what is typed, supports autofill and can check the app's password policy, but never shows which rules are met or unmet, how strong the password is as a bar, or an integrated way to reveal what was typed.
Decide which rules a password has to meet, and let the person watch them tick off as they type.
A live reading of how strong the password really is, scored on its own and not on the rules you set.
An optional reveal, so people can check what they typed instead of starting over.
The field, the toggle, the rule panel and the strength meter are all yours to style.
Fully operable from the keyboard and announced to screen readers, with motion preferences respected.
Everything the input knows is available to your workflows, and every change is an event you can react to.
In detail
Place the plugin element wherever you need it.
Adjust the settings to match your use case, including the password policy and its labels, where the floating panel appears, and the strength meter.
Use the value changed event to capture the confirmed password, and read the exposed states to use them anywhere in your app.
The password policy and the strength meter are independent measures. A password can satisfy every rule you required and still score low on strength, or score high and fail a rule. Use Pending policies make the input invalid? to decide which of the two gates your form.
Text displayed in the input while it has no value.
Color of the placeholder text.
Tells the browser whether to suggest a new password or fill a saved one.
Controls whether the input icon is displayed.
Icon displayed in the input.
Icon size in pixels. When empty, it is calculated from the input font size.
Color of the input icon.
Shows the eye icon that reveals or hides the password.
Eye icon style. Each style has an open and a crossed-out version.
Eye icon size in pixels. When empty, it is calculated from the font size.
Eye icon color.
Defines when the strength and policy panel is shown.
Preferred or forced opening direction of the floating panel relative to the input.
Opening animation of the floating panel.
Background color of the floating panel.
Sets the border color of the floating panel.
Intensity of the glassmorphism effect on the floating panel.
Shows the strength bar and label in the panel.
Title displayed above the strength bar, next to the strength level.
Font color of the strength title.
Color of the empty bar segments.
Strength label for 0-20%.
Strength color for 0-20%.
Strength label for 21-40%.
Strength color for 21-40%.
Strength label for 41-60%.
Strength color for 41-60%.
Strength label for 61-80%.
Strength color for 61-80%.
Strength label for 81-100%.
Strength color for 81-100%.
Minimum number of characters. Use 0 to disable this policy.
Maximum number of characters. Use 0 to disable this policy.
Requires at least one lowercase letter.
Requires at least one uppercase letter.
Requires at least one number.
Requires at least one special character (any character that is not a letter, number or space).
When enabled, a filled password is only valid when all active policies are met.
Pending policies make the input invalid? decides whether an unmet rule makes the field invalid, or whether the list is only guidance. Turn it off when the policy is advisory and your own workflow decides what to accept.
Title shown above the policy list.
Minimum length policy label. {n} is replaced by the minimum length.
Maximum length policy label. {n} is replaced by the maximum length.
Lowercase policy label.
Uppercase policy label.
Number policy label.
Special character policy label.
Policy title color. When empty, uses the element font color.
Icon pair used for completed and pending policies.
Icon and text color of pending policies.
Icon and text color of completed policies.
Disables the component, preventing any interaction.
Input background color when disabled.
Input border color when disabled.
Input font color when disabled.
This color applies to the password the user typed, not to the placeholder. A disabled field with nothing in it keeps the placeholder color you set in INPUT > # General.
Marks the field as required and enables input validation.
Input background color when invalid.
Input border color when invalid.
Input background color when focused.
Input border color when focused.
Name read by screen readers. When empty, uses the placeholder or the visible label.
Hint read by screen readers after the name. Empty for none.
Values the element exposes for the rest of the page to read.
The policies only decide is valid while Pending policies make the input invalid? is checked. Unchecked, they are a guide, and any password that is not empty is valid.
Current password.
Password strength from 0 to 100.
Label of the current strength range.
Labels of all active password policies.
Labels of the password policies already met.
Labels of the password policies not met yet.
Whether the input accepts interaction.
Whether the input is required.
True when the value is accepted. False when it is required and empty, or a policy is still pending while Pending policies make the input invalid? is checked. It updates on every change, so a workflow can rely on it; the invalid style only shows after the person leaves the field, or when a workflow sets the value.
Whether the input is focused.
Where a workflow can start.
Triggered when the password is confirmed with a different value, when leaving the input, pressing Enter or resetting the element.
What a workflow can tell the element to do.
Clears the password, hides it again and resets the touched state.
Focuses the password input.
Writes a password into the field from a workflow and refreshes the strength meter, the policy list and the exposed states.
Yes applies the value even while the element is disabled. No makes the action do nothing in that state.
The password to write into the field; an empty value clears it. The strength meter, the rule list and the exposed states are all recalculated from it. This exists for the case where your app generates a password that satisfies the policy configured above, which the browser's own generator cannot know. It is not meant for storing a password and writing it back later.
No. Everything happens in the browser: the value, the strength calculation and the policy check never leave the page. The password only goes somewhere when your own workflow sends it.
From the typed password itself, independently of the policy you configured. Length is worth up to 60 points, 3 per character up to twenty characters, except that the counted length is also capped at twice the number of distinct characters, so `aaaaaaaa` does not score like a long password. Variety is worth the other 40, with 10 points for each class present: lowercase, uppercase, number and special character. That is why a password can be strong and still fail a rule you required, or meet every rule and still score low.
Yes. Turn off Pending policies make the input invalid? and the rule list keeps updating as the user types, while the field stays valid. Your workflow then decides what to accept.
Active lists the rules you switched on. Completed lists the ones the current password already satisfies, and pending the ones it does not. The three are text states, so you can show them anywhere on the page.
Because the two do different things with a secret. A default value is an expression that lives in the page definition and is evaluated on every load, which means your app has to be holding the password in plain text to have something to put there. Set value is an explicit, momentary action, and it exists for one case: your app generates a password that satisfies the policy you configured here, which the browser's own generator cannot know about. If what you want is the field to start with the password the person already has, that is the password manager's job: set Browser autocomplete to current-password and the browser fills it, without your app ever seeing it.
Because a password that cannot be seen is a password that gets mistyped, and the error is invisible to the person typing. Letting the user reveal what they wrote is a recommended practice, and the toggle can be switched off when your context forbids it.
Yes. The visual properties support Bubble's predefined styles, so a look can be saved once and applied to every input in the app. A few sizing fields are deliberately not dynamic, and that is what lets them travel inside the style instead of being set one input at a time.
This plugin is maintained by GCS Studios and is part of the NWD UI - Input family, form controls built from scratch for Bubble, inspired by a personal component library originally built for React. Each one is carefully designed and tested in real applications before release, for the level of control, polish and reliability that native Bubble inputs often do not provide. See more plugins on the GCS Studios contributor page.
Each control here is drawn by the plugin instead of being restyled from a native one, so they match each other across the library and keep the same shape in every browser.