Before contacting us
Reload the extension from chrome://extensions, refresh the page you are testing and try the action again.
Questions, bug reports and feature suggestions are welcome. We usually respond by email.
Email support@fill.50.ciReload the extension from chrome://extensions, refresh the page you are testing and try the action again.
Include your Chrome version, the Quick Fill version, the field type involved and clear steps to reproduce the issue.
Chrome blocks extensions on internal pages, the Chrome Web Store and some restricted frames. This is expected browser behavior.
No. Form detection and fictional data generation happen locally. Quick Fill has no developer-controlled server, tracking or analytics.
The field may be hidden, disabled, read-only, protected, inside a closed Shadow DOM, or matched by your blacklist. You can also add a custom rule in Options.
Yes. Open Quick Fill Options to select the language, country, phone format, password length and other generation preferences.
No. They are fictional test values. Card numbers satisfy the Luhn checksum for validation testing but must never be used for real payments.