Choose a layout that makes the requested action obvious. The email or username field, password field, and sign-in action should be readable and easy to reach on a phone. Keep recovery and registration links distinct from the primary action.

These templates provide a visual interface, not authentication. Connect your own secure sign-in service, use appropriate autocomplete values, and provide accessible validation and error states. Do not collect credentials through an unconnected sample form or imitate another service’s branding.

Preview a design at desktop, tablet, and phone widths on its detail page. You can download the HTML and CSS or customize it in the code editor. Review the code reuse terms before publishing external assets.