A Simple Way to Generate Unlimited Test Emails
For Gmail and Google Workspace business emails
When you’re testing online forms, user signups, or checkout flows, you often need multiple email addresses to make sure everything works correctly. Instead of creating separate accounts, both Gmail and Google Workspace (Google for Business) support a built-in shortcut: the plus-sign alias trick.
What It Is
Gmail and Google Workspace ignore anything you add after a + in the first part of an email address.
For example, whether you’re using a personal Gmail inbox or a business email like you@yourdomain.com, all of these will work:
- example@gmail.com
- example+test@gmail.com
- example+userA@gmail.com
And for business accounts:
- info@yourdomain.com
- info+form1@yourdomain.com
- info+checkout@yourdomain.com
All of these deliver to the same inbox.
This allows you to generate unlimited “unique” email addresses for testing—without creating new accounts.
Why It’s Useful for Testing
Using plus aliases makes it easy to check:
- Form submissions
- Automated confirmation emails
- Email marketing signups
- Multi-step registration flows
- CRM or database behavior
- Systems that require distinct email addresses per user
Each alias appears unique to the system you’re testing, even though all emails land in one place.
How to Use It
- Start with your regular Gmail or Google Workspace email, e.g., user@yourdomain.com.
- Add a tag with a + before the @, such as:
- user+test1@yourdomain.com
- user+newsletter@yourdomain.com
- user+checkout01@yourdomain.com
- Use each variation to submit your form or test your workflow.
- All confirmation or notification emails will arrive in your main inbox.
Bonus: Stay Organized With Filters
Gmail and Google Workspace allow you to filter by alias. For example:
- to:user+checkout01@yourdomain.com
This helps you track which submission generated which message.
A Note on Compatibility
Most modern systems accept plus aliases.
If a form or checkout rejects an address with a +, it usually means the email validation is too strict—a helpful issue to flag during testing.
