--- title: "Custom Temp Email: Choose Your Inbox Name" description: "Create a custom temporary email address with a name you choose. When a custom prefix beats the auto-generated address, and how to set one in seconds." url: https://tempinbox.dev/blog/custom-temp-email-address locale: en published: 2026-05-29 updated: 2026-09-07 source: TempInbox --- # Custom Temp Email: Choose Your Inbox Name By default TempInbox generates a random address like swift-cloud-7x4@tempinbox.dev. You can set a custom prefix instead — the part before the @ — which helps when you run several inboxes and want to tell them apart by purpose. The domain stays the service domain; custom domains are not supported. By default, TempInbox generates an address automatically — something like `swift-cloud-7x4@tempinbox.dev`. That works perfectly for most use cases. But if you want an address with a specific name you will recognise, or one that reflects its purpose, you can set a custom prefix instead. ## How do you create a custom temp email address? 1. Open [tempinbox.dev](https://tempinbox.dev/). 2. In the address field at the top of the inbox, click the edit icon or the address name itself. 3. Type the prefix you want — for example, `qa-signup-test` or `trial-review-may`. 4. Confirm. Your address becomes `yourprefix@tempinbox.dev`. The inbox works identically to an auto-generated one. All incoming mail to that address appears in real time. The same persistence rules apply — the inbox is stored in your browser via localStorage and stays available until you delete it or clear browser data. ## When does a custom address name help? ### QA and developer testing When running multiple test scenarios, a descriptive address name makes debugging easier. `signup-happy-path@tempinbox.dev` and `signup-dupe-email@tempinbox.dev` are self-documenting. If a test fails, the address name in the logs tells you which test case was running without needing to cross-reference a UUID. ### Sharing an inbox across a small team If two people on the same team need to access the same temporary inbox — for example, both want to see whether a welcome email arrived correctly — a custom predictable name lets both parties access the same inbox from their respective browsers. Note that this makes the inbox semi-public: anyone who knows the name can access it, since TempInbox inboxes are browser-scoped by default. For a genuinely shared team inbox with controlled access, consider using a password-protected inbox instead. ### Remembering the address without looking it up Auto-generated addresses are random — `swift-cloud-7x4` is not something you will remember. If you need to reference the same address in multiple contexts without always having TempInbox open, a custom name you can type from memory is practical. ## When is an auto-generated address better? ### Privacy A predictable custom name — your real name, your username, anything guessable — reduces the privacy benefit of a disposable address. If someone can guess your address name, they can read your inbox. Auto-generated names like `swift-cloud-7x4` are effectively unguessable and provide proper session-scoped privacy. If you want a custom name for organisational purposes but still want privacy, use a random-looking custom name rather than something personally identifiable. ### Speed If you just need an inbox quickly and do not care about the name, letting TempInbox generate one automatically is faster. One less decision. ## Is a custom address the same as a custom domain? These are two different things that often get confused: - **Custom address name:** you choose the local part before the `@`, but the domain is still `@tempinbox.dev`. This is what this post covers — available to any individual user for free. - **Custom domain temp email:** a team or organisation uses their own domain for disposable addresses, so addresses look like `test@yourcompany.com`. This is a different feature aimed at teams who need controlled routing under their own domain. See the [custom domain temp email guide](https://tempinbox.dev/blog/custom-domain-temp-email) for that use case. ## Related guides [Create a temp email](https://tempinbox.dev/blog/create-temp-email) · [Custom domain temp email](https://tempinbox.dev/blog/custom-domain-temp-email) · [Password-protected inboxes](https://tempinbox.dev/blog/temp-email-password-protection) · [What is temp mail?](https://tempinbox.dev/blog/what-is-temp-mail) ## Start using TempInbox Create a temporary inbox in seconds. No signup, no timer, up to 3 browser-saved inboxes. Open your TempInbox → ## FAQ ### Can I choose a custom name for my temp email address? Yes. On TempInbox, you can set a custom prefix for your address instead of using the auto-generated one. The address will be yourname@tempinbox.dev. Use the address name field in the inbox creation screen. ### Is a custom temp email address less private than an auto-generated one? Potentially, if you choose a predictable name. A custom name like 'john.smith' is guessable; an auto-generated name like 'swift-cloud-7x4' is not. For privacy, either use a random custom name or let TempInbox generate one automatically. ### What is the difference between a custom temp email and a custom domain temp email? A custom temp email address lets you choose the local part (before the @) — e.g. myname@tempinbox.dev. A custom domain temp email lets a team use their own domain for disposable addresses — e.g. test@yourcompany.com. The first is for individuals; the second is for teams with their own domain. ### Why would I want a custom temp email address? Custom addresses are useful when you need to remember the address without looking it up, when you want the address to reflect its purpose (e.g. 'qa-test-run-3@tempinbox.dev'), or when you need a consistent address across multiple test runs. ## Related guides - [Masked Email vs a Disposable Inbox](https://tempinbox.dev/blog/masked-email-vs-disposable-inbox.md) - [Verification Codes Without Your Real Email](https://tempinbox.dev/blog/receive-verification-code-without-real-email.md) - [Reusable Email: Keep and Reuse One Temp Inbox](https://tempinbox.dev/blog/reusable-temporary-email.md)