Webflow’s built-in Memberships and Logic features currently use email addresses as the unique identifier for users during login—username-based login is not supported natively. Here's a breakdown of what's possible and not possible.
1. Email is the Only Supported User Identifier
- Webflow Memberships only supports email as the unique login credential.
- You cannot change the login form to accept a username instead of an email.
- Any form that connects to the native Webflow user system must use the email input field with the input name and ID set to "email".
2. There Is No Supported “Username ID”
- Webflow does not provide a “Username ID” for login.
- Even if you collect a username as part of a signup form (e.g., a text field labeled “Username”), it cannot be used for login authentication.
- The backend authentication requires the email + password combination only.
3. Workarounds Are Very Limited
- You could store a custom “username” field in the User data for display, but not for login.
- Advanced solutions that use third-party auth systems (e.g., Firebase, Auth0) with custom front-end development outside of Webflow’s native login could allow for username login, but these require exporting Webflow code and are not supported directly inside Webflow.
Summary
Webflow’s native login system requires email for user authentication—you cannot use a username ID in place of email for login. If you need username login, you'll have to use a custom authentication flow hosted outside of Webflow's built-in features.