In Settings I have checked Enable Auto-fill on Page Load, with the Default autofill setting for login items set to Auto-fill on page load.
My issue is that all login items have their Auto-fill on page load? set to – Select –, so nothing is auto-filling.
How can I set all login items Auto-fill on page load? to Default (Yes), without changing every login individually?
Primary browser is Firefox.
@Schrodingers_cat Welcome to the forum!
When you enable “Autofill on page load” and do set the default to “Autofill on page load”…
…then - select - defaults to “Yes”:
I just tested this also and it does work for me.
Here more info to autofill on page load – and just a reminder: it’s not the recommended method: Autofill From Browser Extensions | Bitwarden
As I stated in my post, that is not my experience.
Could the problem be that most logins were imported from an xml file (IIRC) created by LastPass?
And again,
Could you please post a screenshot of your “Autofill on page load” section in the settings of the browser extension?
Does autofill work in general with the login items you speak of? (I ask because if autofill wouldn’t work at all, then it would be expected to also not work with “autofill on page load” – and that could e.g. be a problem of wrong URIs/URLs, due to the import)
And to also answer to this directly:
Unfortunately, this could only be done individually for every login item. (maybe there would be a workaround like exporting your items, changing that value, and re-importing your vault…) [PS/Edit: @grb checked this now – see this following post – and it turns out, those values are not included in both CSV and JSON exports, so that path is not an option right now.]
If everything is set up as it should be, it is not necessary to change -- select -- to Default (Yes). Both -- select -- and Default (Yes) are “Yes”… when everything is set up correctly. (and you would only have to set No for those login items that you don’t want to autofill on page load)
If you really have the Default already set to “Autofill on page load”, then it’s indeed probably a problem of the URIs…
@Schrodingers_cat What version of the browser extension do you have installed?
Could you please screenshot this? There is no “Select” option for the Autofill on page load? selector in the browser extension. These are the options available for the individual login items:
The state of the first (“Default”) option depends on how you have configured the “Default autofill setting for login items” setting under Settings > Autofill.
Please make a screenshot of one of your existing login items, showing the “Select” value under the Autofill on page load? option. Next, create a new Login item, and take a screenshot showing its default value for the the Autofill on page load? option.
Existing login items – when created or imported before “Autofill on page load” was enabled – can have that - Select - state/“value”:
(screenshot from one of my existing forum login items)
As @Schrodingers_cat seems to have imported items before enabling “Autofill on page load” their existing login items are probably in that state. (at least that was my understanding)
Interesting. And it seems that if saving a Login item that was created after “Autofill on page load” was enabled, then re-opening the item also shows the “–Select–” value (if it the item was saved without changing the “Default” value in the Autofill on page load? selector).
To me, this actually seems like a bug (inconsistent UI). The selector value should always show “Default” instead of “–Select–” (unless a non-default value has been specified), whether it is a newly created item or an existing item.
As an aside (unrelated to the topic at hand), investigating this made me aware that the custom setting for the Autofill on page load? option is not captured in vault exports (either CSV or JSON).
Ah, that is also interesting. And indeed either a bug – or at least redundant and questionable UI/UX, as - Select - acts as if it was Default. – I agree then, it just should default to Default…
Thanks for checking this! I’ll add that to my previous post (where I speculated if those values might be included in exports…)!
I can confirm this as I use a non-normal setting (Host) and I need to update it on each device. This is a setting I would like synced (as opposed to Vault Timeout, which I do not want synced).
Update: I am an idiot.
Seems like you may be you referring to the “Default URI Match Detection” setting (not “Default autofill setting for login items” or “Autofill on page load?”). Incidentally, unlike the customized settings for “Autofill on page load?” (which are not synchronized or captured in exports), the customized settings for “Match detection” (for individual URIs) are in fact included in JSON formatted exports (and are synchronized, as well).
I also use a non-standard URI match detection method (Exact), and I am in the habit of customizing each individual URI to have the desired match detection setting (instead of relying on the Default setting), to ensure that the preference is synchronized.
Version: 2025.11.2
SDK: ‘main (8ef7951)’
Server version: 2025.12.0
@Nail1684, I can confirm that I only discovered auto-fill was possible, long after I started to using Bitwarden.
@grb, I can confirm that my newly saved community.bitwarden.com login has – Select –, not Default (yes), even when Auto-fill is the default value.
So, I can’t export my data, and import it, to have all my logins use the default auto-fill setting. 
@Nail1684 and @grb, do you need me to provide any more information, or have you confirmed that this behaviour is present, but unintended?
Please share what version of the browser extension you have installed?
Next, for testing purposes, please create a new login item by clicking the 
New button in the browser extension, and entering arbitrary dummy values for the item name, username, and password. In the Autofill Options section, please clear any contents in the “Website (URI)” field, and then copy and paste the following string:
https://fill.dev/form/login-simple
Next, please confirm that the “Auto-fill on page load?” option is set to “Default (Yes)”, and then click Save.
After you have saved the new Login, click Edit to re-enter the “Edit Login” view, and check what value is shown for the “Auto-fill on page load?” option. Click Cancel when you have checked the setting.
Finally, open the link https://fill.dev/form/login-simple in your browser. Are the username and password fields automatically autofilled when the page loads?
As above, 2025.11.2
Done. Check showed -- Select --, but auto-fill worked.
OK, thanks. Could you please confirm that your other (existing) logins show “–Select–” but do not autofill on page load? And that this failure to autofill is also observed in browsers other than Firefox?
If so, would you mind sharing the login form URLs for a few of the logins where you’ve confirmed you are having an autofill issue? For example, does autofill occur on page load for your community.bitwarden.com login?
Furthermore, it would be helpful to know what setting you have configured for the option “Default URI match detection” (under Settings > Autofill, in the “Additional Options” section).
Yes and yes.
Fastmail and Hubbl, which both ask for a user name before showing the password box. Could that be the problem. Selecting Fill fills the fields.
Yes.
Base domain (recommended)
Why does --Select -- even exist? Surely the option Default should be active, in the absence of a user selection.
It is. “–Select–” and “Default” are the same thing (which is why @Nail1684 and I were discussing UI inconsistencies above). There is something odd going on in your setup that is preventing the autofill on page load feature from working for you.
Did some quick tests with Fastmail, and yes, their login form design prevents the “Autofill on Page Load” function from working for the password field; the email field can be autofilled if you define a linked custom field using the label v23-input (linked to the username).
The login form (email and password) for the Hubbl site can be autofilled on page load if you define a linked custom field using the label username (linked to the username).
OK, so the autofill problem that you’re experiencing evidently only occurs on specific websites — the problem is not that “nothing is auto-filling” (which was your original assessment).
And it has nothing to do with the fact that “Default” selection for the Auto-fill on page load option is sometimes displayed as “–Select–”.
