It doesn't offer to save a new login item on most web sites


It doesn't offer to save a new login item when I submit a form first time on most websites I visit. How to deal with them?

It is very time-consuming to note them down and report you one by one.


1Password Version: 7.2.1
Extension Version: Not Provided
OS Version: Not Provided
Sync Type:


  • Hi @koraykupe,

    When you say most, does this mean that it is working on some? The reason for asking is one entire area of troubleshooting would be to see if the extension is connected to 1Password but if however filling is working and you're being prompted in some places anything related to a connection issue is eliminated. What would also be useful is to learn what version of the 1Password extension you have installed in your browser.

    If this is the case let's start with one example, assuming you're happy to post a link to the site in our public support forum what is a recent site where you've experienced trouble with the autosave prompt and was it with the sign-in form or the registration form?

  • koraykupekoraykupe
    edited October 2018

    Yes, it works for a lot of websites perfectly, and there is no any network issue, don't worry. :) All apps & extensions are up-to-date. It occurs especially on Ajax forms. I can give a few examples:

    I can find much more.

    Another problem is on websites that have 2-steps login. First, you type your email and submit, then you type your password. 1Password offers to save it but doesn’t catch the email. It only saves your password.
    Some examples:

  • littlebobbytableslittlebobbytables

    Team Member
    edited February 11

    Hello @koraykupe,

    So the multi-stage ones won't play nicely with 1Password's autosave prompt. For those it will require manually creating a Login item and we detail the process on our support page Sign in to websites with username and password split across multiple pages which covers both saving and filling.

    For the others I'll have to investigate each in turn. I got the expected prompts on gearbest so as best I can tell we work there for both the sign-in and registration forms. For D & R the problem is 1Password is weak with non-English sites and it doesn't understand that GİRİŞ YAP is Turkish for sign in and we should react to that. I will file an issue and check each of the sites to see what combination of words seem to be used.

    ref: xplatform/filling-issues#301

  • Okay, thanks! I think It's better to check class names, ids and input names instead of labels. Otherwise, you have to check all possible translations in hundreds of languages.

  • Hi @koraykupe,

    Each has its issues. Lots of sites either ignore or use meaningless ID and names and there isn't anything stopping a site from using a different language here as well. While not perfect for the reason you mention, at least we know the displayed title should be meaningful to the user given it is what they see. There is of course always room for improvement here.

  • Ok, your answer is satisfying. Thanks. The Twitter support team just suggested me to save these logins manually. :)

  • Hi @koraykupe,

    Saving a Login item manually is certainly one way and how I viewed 1Password changed when I first learnt about this method. Of course we still want to improve the detection and your report will help. There is also slightly different behaviour that may offer an immediate improvement. Sign-in forms tend to allow both clicking a sign-in button and the user pressing the enter key on the password field. Some sites only allow clicking a button but in my own experience I tend to find them rare. Pressing enter on a password field is handled slightly differently and can trigger the correct response in places where clicking a button won't.

    I am still very grateful for the report regarding these sites though as what we have to aim for is consistency no matter how and where you use 1Password.

  • I think it is not only about one local language. is a Dutch website, and save login prompt doesn't work.


  • jxpx777jxpx777 Code Wrangler

    Team Member

    littlebobbytables was using a bit of shorthand… Depending on the site and how it's coded, 1Password has to check a few different things for determining whether to offer saving. For very well coded sites, 1Password is less dependent on trying to look at the user-facing strings on things like buttons. For sites that use less semantic approaches such as a <div> tag instead of a <input type="submit"> for the form submission element, 1Password has to try to determine if the thing the user clicked on is likely a submission widget even though it's not obviously so from the code of the page. I hope that makes some sense.

    In any case, I tried on by going to the main page and then clicking Inloggen at the top, which took me to I got a save prompt when I entered credentials and pressed the Inloggen button and when I pressed return in the password field. Did you get a different result?

    Jamie Phelps
    Code Wrangler @ 1Password
    Fort Worth, Texas

  • I have a lot of different type of example websites. I've compared my current websites with the other password manager app that I was using before and there is a HUGE difference. After I update a password on a local website, although I go to another page, It offers me to update the password perfectly. But 1Password just saved my generated password and that's it. I have to copy that password, remove the password item and update the login item manually. Can you see the difference? It may miss a few websites, but I faced this type of issues on a lot of websites. The last one was one of the most popular websites in Turkey, password update page.
    I am so sorry but I am about to give up. I think I won't extend my subscription and go with the current app.

    Best Regards.

  • In time I'm sure we will improve support for Turkish across sign-in and change password forms but your final determination about any software should be on what it does at this moment in time and not what future improvements may bring. Like any category of software, each password manager will have its strength and weaknesses and its about finding the one that best fits you. Should you decide to give 1Password a shot again at some point in the future maybe you will find it works better with Turkish sites compared to this first experience.

  • I logged in to with a different login, after pressing enter (to submit the login form) it didn't offer to save it.

    The same thing just happened on (generated a password and filled in the registration form) It just saved the password. I had to manually convert it to a login item.

    This is extremely annoying for me!

  • Hi @koraykupe,

    Can you supply the exact URL you use for Netflix please. I tested and everything worked okay for me and I just want to make sure whatever is happening isn't specific to a certain version of that page.

  • @littlebobbytables I checked the case one more time, and realised that it doesn't offer to add it because the password is same. The email address is different, so it should offer to save it. The current behaviour doesn't check the username which does not make sense at all.

    The URL:

  • Greetings @koraykupe,

    That would explain what you're seeing. 1Password's determination of whether to prompt or not is based exclusively on the password. Part of the reason is a page can have masses of text fields and so they're considerably less reliable for using as cues. It would be great if 1Password could prompt for both but the false positive rate would have to be extremely low otherwise it would drive people insane with the false prompting. Of course part of the goal in using 1Password is to eventually have unique passwords for each account, even if you have multiple accounts with a single service.

  • koraykupekoraykupe
    edited February 6

    Part of the reason is a page can have masses of text fields and so they're considerably less reliable for using as cues.

    Dear @littlebobbytables
    Isn't it the same thing with the regular new login item prompt? I don't understand the reason of false positives. As long as it is the same login page, there wouldn't be many fields and it'd be the same behaviour with the first new login item prompt. This case doesn't occur on a random page. It's already the login page of the same web site.

  • Hi @koraykupe,

    All of the prompts displayed by 1Password, whether it is for a sign-in form or a change password form, they're based on the password fields on the page. We attempt to extract a username field if we detect something worth saving and a number of the things we do are based on using the password field as a starting point. This is why multi-stage sign-in forms require the first stage with only the username to basically use the How to save a Login manually in your browser steps.

    The prompt isn't limited to simply the password being present for some site, the Login item must also match the registered domain so this only impacts when multiple accounts for the same site are reusing the same password. The hope is even for people slowly moving over to 1Password that these cases aren't that common.

    If sign-in pages were for the vast majority of instances nice, simple and clean dedicated pages we could be a lot more liberal but this isn't the case. We need to design 1Password for the sites where the sign-in form is part of a larger page for searching a timetable, I've seen sign-in pages with over 500 input fields and I've seen pages (plural) where the username field was labelled as a new password field using the autocomplete attribute. A lot of what goes into 1Password is often just about trying to minimise the wackiness we find out there. Should 1Password interact with fields set as read-only? you'd think that would be simple but when we added it what did we learn but there are sign-in forms where our users need 1Password to fill into a read-only field to avoid forcing the user to muck around with a virtual keyboard. Believe me, I wish detecting could be much easier than it currently is.

  • I also think that each login item should have different passwords, but this type of problems happen to me. Not just for netflix, I gave many other example web sites that the extension could not catch the correct fields or missed it completely.

    Is tracking subsequently visited pages is over-complex to detect multi-stage sign-in forms. If so, I will congratulate the password manager that can do that already. Actually having this type of js based trackers bring extra load to the browser and you don't want to do that, but I wondered if it is really complex or not.

    I've been saving new items, updating passwords or converting passwords to a login item manually often. Identity filling doesn't work properly for many many pages.

    (a recent example; the name field's name is fname, and the last name's name is lname and the extension fills my first name + last name to the last name field as merged.)

    I agree that you can not trust every website and false positives may always occur. Developing a generic app for forms is a very trick job indeed. Thanks for the detailed answers.

  • Today I created a new account on and it did not offer to save it. :'(

  • @koraykupe: Identities are one of the toughest things to fill properly. There are infinitely more ways for web developers to label fields on these forms compared to login forms, which can lead to 1Password not being confident enough to fill.

    Today I created a new account on and it did not offer to save it.

    No matter how many times I tried to create an account there, I got the prompt to save the login, so I'm not sure what went wrong there. Which browser are you using? Did you press Enter/Return key, or click the Create account button?

  • Does it make difference to click enter key or click the button for 1Password normally?
    It was Chrome. I can check again tomorrow.

  • @ag_sebastian I think it was my second account. Passwords were different. Can you first save a login for the website and try to login with another credentials again?

  • Greetings @koraykupe,

    For the most recent report, would I be correct in believing you used the Password Generator? It looks like we have a bug where if 1Password fills using a generated password it is incorrectly inferring that it already knows the password. In a way 1Password isn't wrong, it will have created a Password item but we want that viewed on as a second class citizen and 1Password should prompt even if the Password Generator is used. I wonder if that is the case here because if Sebastian is anything like me my tests often have me use a goto dummy username and password, my own being peekaboo. You should see how much 1Password dislikes my test vault :lol: This bug is something I'm hoping we can correct soon. This would be separate from some of the earlier sites where it looks like the lack of knowledge on Turkish is the cause.

  • Hello @littlebobbytables I think that was the case. I hope it will be fixed soon. Do you think it is an old bug?

  • Hello @koraykupe,

    I believe the bug I've eventually noticed wasn't present in 7.1.2 so it's not a long, long standing bug but if it was present in 7.2 that's four minor updates that it escaped me. Part of the reason is by pure chance things worked okay on one of my goto test sites - I haven't delved into why it worked there given the way the bug should affect all usage of the Password Generator. Fingers crossed we can get that one corrected soon and then we can turn our attention back to where we know 1Password is weak in terms of languages.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file