HTML · ATTRIBUTE
Last reviewed
autofocus is a boolean global attribute that asks the browser to focus an element when the page loads, or when a dialog containing it opens with showModal(). Use it on only one element per page. Content added later does not normally receive autofocus unless it is in a dialog being opened. iOS Safari and some Android browsers usually will not open the on-screen keyboard without a user tap. The attribute is never submitted with form data.
What gets submitted
Fill in the form above and press its button. The demo stops the request and lists every name=value pair the browser would send, plus the controls it leaves out.
With a free access key in the form, these fields land in your splitforms dashboard; access_key and botcheck are read by splitforms, not stored as lead data.
Minimal snippet
<input type="search" name="q" autofocus>Copy-paste code
Replace YOUR_ACCESS_KEY with a key from your free splitforms dashboard. The form posts to one endpoint — submissions land in your inbox and dashboard with spam filtering built in.
<form action="https://splitforms.com/api/submit" method="POST">
<input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
<label for="name">Name</label>
<input type="text" id="name" name="name" autofocus required>
<label for="message">Message</label>
<textarea id="message" name="message" rows="4" required></textarea>
<!-- Honeypot: hidden from people, bots fill it in -->
<input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
<button type="submit">Send</button>
</form>Attributes · autofocus
Focus requires an eligible, visible element; these attributes affect focus behavior.
| Attribute | What it does | Docs |
|---|---|---|
autofocus | A boolean global attribute that requests focus when the page loads or its containing dialog opens. | MDN |
disabled | A disabled form control cannot receive focus. Enable it before requesting focus. | MDN |
tabindex | Controls whether an element can receive focus and how it participates in keyboard navigation. | MDN |
Common mistakes
Choose focus deliberately and account for browser and accessibility behavior.
A search page, login, single-purpose form, or the first field in a dialog can benefit from immediate focus. Use only one autofocus element per page; if several compete, the browser focuses the first eligible candidate.
Automatic focus can scroll past introductory content. Screen-reader users may land in a field without hearing the content before it, and a mobile keyboard can obscure the page. Keep a visible label and let visitors choose where to start when context matters.
Multiple autofocus elements compete; an element added after page load by JavaScript or a framework does not normally autofocus unless it is in a dialog being opened. A field hidden with display:none or disabled cannot be focused. Focus inside an iframe may also depend on browser and embedding restrictions. When appropriate, make the field visible and enabled, then call el.focus({ preventScroll: true }); after it is inserted. This does not bypass browser restrictions.
iOS Safari and some Android browsers usually require a user tap before opening the on-screen keyboard. Focusing a field programmatically does not guarantee the keyboard will appear; allow the visitor to tap the field.
React uses the camelCase autoFocus prop and applies focus itself when the element mounts: <input name="q" autoFocus />. Browser focus and mobile keyboard restrictions still apply.
Sources: WHATWG HTML Standard: autofocus · MDN: autofocus
The HTML autofocus Attribute example below is a complete, working form — paste it into any HTML page and it submits, no edits to the markup required.
Your html autofocus attribute form posts to one endpoint. No server, PHP, or API route — accepted submissions are saved to your dashboard before owner notification email is attempted; delivery time and inbox placement depend on provider and recipient settings.
Unlike a static reference snippet, this autofocus form actually sends data to a free splitforms backend, with spam filtering built in.
How it works
Copy the html autofocus attribute example, drop in your free access key, and paste it into any page — submissions start landing in your dashboard.
Copy the HTML autofocus Attribute example below.
Replace YOUR_ACCESS_KEY with a free splitforms key from the dashboard.
Drop the form into any HTML page. Submissions arrive in your dashboard.
How SplitForms works
splitforms receives the submission, filters spam, saves it to your dashboard and emails you — then, on paid plans, sends it on to your webhooks and integrations. No backend infrastructure to build.
Point your form to your unique SplitForms endpoint. That's it.
We instantly capture and organize every submission in your inbox.
Send data to email, spreadsheets, CRMs, webhooks, and 7,000+ apps.
No credit card required. Set up in under 60 seconds.
Connect & automate
On paid plans, submissions can also go to Slack, Discord, Google Sheets, Notion, Airtable, Zapier or any signed webhook — and splitforms works on the platforms you build on, from WordPress and Shopify to Next.js. With Stripe connected, your forms can take payments too.
NewTake payments on your formsDeposits, bookings, order forms — submitters check out through Stripe and the money goes straight to your Stripe account. Included on every paid plan.See payment forms →Need time slots? Online booking →Questions
Add the boolean autofocus attribute to the input, such as <input type="search" name="q" autofocus>. Use it on only one element per page and provide a label.
Yes. An autofocus element inside a dialog can receive focus when the dialog opens with showModal(). Choose the most appropriate initial focus for the dialog, which is not always its first input.
Mobile browsers can require a user gesture before showing the keyboard. A visitor can tap the field to open it, even if the browser has already focused it.
Use the camelCase autoFocus prop, for example <input autoFocus />. React applies focus when the element mounts, subject to browser restrictions.
No. autofocus controls focus behavior; it is not submitted as form data.
Simple pricing
Free gives you 500 submissions for $0 — no card, no time limit. Pro is $5/month for 5,000 submissions a month, and Annual is $49/year for 15,000 a month with every Pro feature.
For side projects and indie devs.
Every paid feature, for agencies and growing products.
Every Pro feature with triple the volume — $0.27 per 1,000 at full use.
No credit card required on Free • Cancel anytime • Full pricing and FAQ
