A blank password field does not prove that a saved login has disappeared. The browser may not recognise the site’s current form, or you may be using a different profile. Establish whether the record exists before deleting anything or resetting the account password.

Locate the intended record

Check the Chrome profile and signed-in Google account. Open Google Password Manager through Chrome’s menu and search for the service name or site address. Google notes that imported entries can sometimes appear under an unexpected app or site name, so inspect likely matches carefully.

Compare the website address and username with the account you intend to use. A company may have several similar portals, and one person may have multiple usernames on the same service. Do not select the first familiar-looking entry without checking both fields.

If the entry is present, return to the genuine website and select the password field. Chrome may then offer matching suggestions. If suggestions still do not appear, Google says the browser may be unable to detect the correct fields on the page.

Separate lookup from credential changes

Use the password manager’s supported reveal or copy controls only in a private setting, following device authentication prompts. Enter the intended credential through the genuine service and check whether sign-in succeeds. Keep passwords out of screenshots, support tickets and shared clipboard workflows.

If manual entry works while autofill fails, record that comparison for the website’s support team. Include the browser version and the particular step where suggestions disappear, such as a second-stage password screen. This is more precise than reporting “passwords are gone.”

If the credential itself is rejected, use the service’s official recovery process as a separate account task. Editing a local saved record does not change the server password. Preserve any working recovery route before removing entries. The acceptance check is the correct account signing in through the intended route, with a clear distinction between stored data and the form’s autofill behaviour.

Sources: Chrome documentation.