Why is my info not being autofilled in a field?

Vauz only offers to fill fields it is confident are a username, an e-mail or a password on a sign-in form. That is deliberate: a Vauz logo on a search box or a one-time-code field is worse than no logo at all. Below are the reasons a field you expected to work does not show one.

The field has autocomplete="off"

Some sites add this attribute to ask password managers to stay out of a field. Vauz takes it seriously but no longer treats it as the last word, because it is set routinely on password boxes people plainly do want filled — including on government and banking sign-ins, where being locked out of your own password manager helps nobody.

So it counts against a field rather than disqualifying it. A password box, or a field the form itself names as the username, is still offered. A field whose only hint was a vague placeholder is not: with autocomplete="off" set, that hint is no longer enough on its own.

The field is inside an embedded frame

Some pages show a form that is served by a different site and embedded into the page — code playgrounds like CodePen, JSFiddle and w3docs, documentation pages with live examples, and some embedded checkout or booking widgets all work this way.

Vauz does not fill logins inside embedded frames. Any site can embed any other site, so a Vauz prompt appearing inside an embedded frame would be one the surrounding page decided to put in front of you, not one the site you trust asked for. Vauz fills logins on the page you actually navigated to.

This also covers some sign-in boxes that do not look embedded at all. A shop or an app can put a sign-in provider's own page inside its checkout — Apple's Store and iCloud sign-in work this way, and so do a number of company sign-ins. The box looks like part of the page, but it is served by another address, so Vauz stays out of it. Signing in at the provider's own site first, or in its own tab, works normally.

If you are testing a form on a code playground, open it in its own tab — most of them have a "full page" or "open in new window" option — and Vauz will work normally.

It is a search box, a filter or a suggestion list

Vauz skips search fields, filter boxes and type-ahead suggestion lists, even when their wording mentions e-mail or users — "Search for email, meetings and files" and "Find a user" are both search boxes. It also skips one-time codes, verification codes and confirmation fields.

It is a code you were sent, not a password

Vauz does not offer to fill one-time codes, device codes or confirmation codes, including the rows of single-character boxes some sites use for them — signing in to a device from a phone or a TV usually looks like this. Those codes are not saved logins, and a Vauz mark on one would be an offer Vauz cannot keep.

Some of these boxes are labelled in a way that reads like a username field. Vauz treats a box that only holds a character or two as a code box whatever it is called, so the character you type stays visible.

The field is too small to mark

The Vauz mark sits at the end of the field, and Vauz will not draw one on a field too narrow to hold it — covering up what you are typing is worse than showing no mark.

If your Autofill Mode is set to Autofill on field focus, that field is still filled; it is only the mark that is missing. If it is set to Show Vauz logo in fields, the logo is how you ask for a login, so there is nothing to click on a field this small. If you meet a real sign-in field this happens on, please tell us and include the page — a login field that narrow is unusual, and worth looking at.

The address looks like another site's

If Vauz thinks the web address is built to be mistaken for a well-known one, it says so in an orange box below the login field. Where the resemblance is unmistakable — letters borrowed from another alphabet, or digits standing in for letters — Vauz refuses to fill anything on the page. Where it is weaker, it warns you and still offers your logins.

Each message, what it means and what to do about it, is in Vauz says this address looks like another site.

It is a sign-up form

Vauz does not fill account-creation forms. A saved password belongs to an account you already have, offering one as the password for a new account is the wrong suggestion. Sign-in forms on the same site are unaffected.

The field genuinely is not recognised

If none of the above apply and Vauz is struggling to autofill information into that field, but autofills other fields on the same page, please contact us. Share the link to the page, along with the specific field that is not accepting Vauz autofill, and, preferably, include a screenshot, so we can visually confirm the issue and fix it.

None of the fields on any page are filled

If no field anywhere is being autofilled by the Vauz extension, please check that:

• Vauz extension is correctly registered with main Vauz app. Please see the troubleshooting steps here.
• Confirm that main Vauz application has the credentials for the specified domain in the vault.
• Please triple-check that domain, you are trying to autofill, is legitimate, as scammers often create fake websites that look like real ones to steal your information.