AI Form Filler Supported Fields & Data Handling - SmartAutoFill
This reference explains which browser form controls SmartAutoFill can fill, where manual work is still required, and how data moves in hosted and custom-provider modes. It describes the current product behavior as of July 12, 2026.
Supported field matrix
SmartAutoFill works most reliably with visible, ordinary browser controls. A page can still add validation or JavaScript behavior that affects the result, so review every filled value.
| Field or control | Support | Notes |
|---|---|---|
| Native text-like inputs | Reliable for visible fields | Includes text, email, tel, url, number, and date inputs. |
textarea | Reliable for visible fields | SmartAutoFill writes the generated value and dispatches normal input, change, and blur events. |
| Native single select | Supported when an option matches | The generated value must match an option value or visible option text. |
| Native multi-select | Limited | For a native multi-select, SmartAutoFill can apply only one generated value. |
contenteditable and ARIA text fields | Partial | Contenteditable fields and some elements with role="textbox" can be filled. Complex rich-text editors may behave differently. |
| Open shadow DOM | Scanned | Open shadow roots are scanned recursively. Closed shadow roots are not available to the extension. |
| Radio and checkbox controls | Not filled | Radio buttons and checkboxes are detected but their state is not filled. |
| Custom dropdowns | Not reliable | Custom combobox or listbox widgets are not reliably fillable. |
| File input | Paid hosted AI Materials only | SmartAutoFill can place one matched material into a native file input. It does not attach several matched files to one control. |
| Iframes | Not supported | SmartAutoFill does not traverse iframes. Fields inside an iframe are outside the current scan. |
You can use the public AI Form Filler Test to inspect how the extension handles a varied native form before using it on an important workflow.
Automation boundaries
SmartAutoFill is a form-filling assistant, not an autonomous browser agent. It does not navigate sites, submit forms, create repeated sections, or provide site-specific ATS automation. It also does not guarantee support for every JavaScript widget used by Workday, Greenhouse, Lever, Google Forms, CRM products, or internal tools.
Values are filled into the page first; you review them there before submitting the form manually. There is no separate pre-apply approval screen. The final decision, correction, and submission remain with you.
What stays in Chrome local storage
The extension stores basic profile data, context profiles, autofill and interface settings, hosted-mode settings, custom-provider settings and API keys, and the account/extension token in chrome.storage.local. Two additional local records deserve explicit mention:
lastAutofillRunstores the scanned page URL and title, headings, nearby and form text, generated plan values, confidence scores and reasons, and per-field results.lastAutofillRunmay also retainfileBase64, a Base64 copy of a matched hosted AI Materials file prepared for a native file input, until the recent-run storage is replaced or cleared. This browser-local file copy is not part of the hosted request-log summaries described below.resumeDataandresumeTemplatescan contain identity, contact, work, education, and other resume facts from legacy or current resume tools.
The browser does not sync these records through your Chrome account. SmartAutoFill does not claim at-rest encryption for these local records. Anyone who can access your unlocked browser profile or extension storage may be able to inspect them, so use a protected device and remove data or credentials you no longer need.
Chrome documents the difference between storage, host access, and other manifest capabilities in its Chrome extension permission documentation. SmartAutoFill uses browser permissions to run on web forms, read the active page URL and title, and keep extension settings locally.
Hosted mode data path
Hosted mode requires a connected SmartAutoFill account and available credits. When you start a fill, the extension sends the following to the SmartAutoFill backend:
- Your profile and context data selected for the fill.
- The selected field metadata, including field type and available labels, names, placeholders, autocomplete values, and options.
- The page URL and title.
- AI Materials source references when the paid feature is enabled.
The backend uses that request to generate a fill plan. Local last-run data is separate from hosted request logs. Request logs keep the page URL and title, field labels, names, placeholders, and plan metadata. They do not keep profile text or generated field values. The logs use summaries such as field IDs, value lengths, confidence, and truncated reasons to support reliability, credit, and failure investigation.
For the broader service-level disclosure, retention language, and user choices, read the Privacy Policy.
Custom-provider mode data path
Custom-provider mode uses the API key stored locally and sends the request to the provider you selected. The request prompt can include profile/context data, page context, and compatible field metadata. SmartAutoFill's hosted autofill backend and hosted credits are not used for that model request.
Custom-provider mode does not support AI Materials or file filling. Review the selected provider's own privacy, retention, and billing terms before sending form context to it.
AI Materials limits
AI Materials is a paid hosted-mode feature. It can use pasted text, the current page, a website, PDF, Markdown, PNG, JPEG, and WebP sources as fill context.
Current limits are:
- 20 MB per file.
- Up to 5 files per upload batch/request.
- 8 sources per fill.
- 4, 10, or 20 stored sources, depending on the paid plan.
- Uploaded and imported sources remain available for 30 days unless deleted sooner.
The upload-batch limit is separate from the limit of 8 sources per fill.
DOC and DOCX are not exposed as supported uploads. When a native file input is compatible, hosted mode can select one matched stored file; the user must still inspect the selected file and submit manually. See Pricing for the current paid plans and their stored-source allowances.
Sensitive fields and More mode
Sensitive fields remain skipped from actual filling. The detection rules cover common password, verification-code, payment-card, government-identifier, and similar labels.
In hosted mode, More can include additional candidates during planning, but final application still respects the original sensitive or unfillable guard. Custom-provider mode excludes those fields from planning. More does not make password, payment, CAPTCHA, or identity fields supported.
Installation and listing references
Install the current extension from the Chrome Web Store. Google recommends that extension descriptions communicate capabilities accurately and clearly in its Chrome Web Store listing guidance; this page supplies the detailed support and data-handling boundaries behind the shorter store listing.