
Send a password reset email after a user requests account recovery. Give them one clear action: open your app’s reset page and choose a new password. Include the link’s expiry, a plain-text fallback, and a short line for anyone who didn’t request the email.
Password reset email copy you can adapt
Use the product name people see on the sign-in screen. The example below uses a fictional app called Northstar. Replace the bracketed fields with your app’s actual expiry period and the HTTPS reset URL generated for that request.
Subject: Reset your Northstar password
Preview text: Use this link to choose a new password for your account.Hi,
We received a request to reset your Northstar password. Use the link below to choose a new one.
Reset my password
If the button doesn’t work, copy this address into your browser:
[Reset URL]This link expires in [expiry period]. If it expires, you can request another one from the Northstar sign-in page.
If you didn’t request a reset, you can ignore this email.
The Northstar team
Keep the expiry in the message consistent with the expiry your app enforces. If the app starts the countdown when it creates the link, a delayed email can arrive with less time remaining. In that case, consider displaying the expiry time with a time zone or saying the link expires a set period after the request.
If you need a design to adapt, browse the Password Reset Email Templates catalog.
A minimal HTML template
Use the same URL for the button, the visible fallback, and the plain-text version. The braces below show illustrative fields. Substitute the syntax your sending system supports, and have your template renderer escape the URL and expiry text for the HTML context.
<p>Hi,</p>
<p>We received a request to reset your Northstar password.
Use the link below to choose a new one.</p>
<p>
<a href="{{reset_url}}"
style="display:inline-block;padding:12px 18px;background:#17336b;
color:#fff;border-radius:6px;text-decoration:none;">
Reset my password
</a>
</p>
<p>If the button doesn’t work, copy this address into your browser:<br>
{{reset_url}}</p>
<p>This link expires in {{expiry_period}}. If it expires, you can
request another one from the Northstar sign-in page.</p>
<p>If you didn’t request a reset, you can ignore this email.</p>
<p>The Northstar team</p>
For the plain-text version, put the complete URL on its own line. Check the delivered message for missing fields or a fallback URL that breaks when copied. To see how an app can hand off transactional messages for delivery, use the Email API guide.
What the app handles when someone opens the link
Generate a reset token with a cryptographically secure random generator, store it securely, and attach it to an HTTPS URL on a trusted domain. The app validates the token, enforces expiry, and invalidates it after use. The email tells the user what to expect. Keep the reset form’s response consistent whether or not the submitted email address belongs to an account, and rate-limit requests to curb abuse. OWASP Forgot Password Cheat Sheet
| Situation | What the user should see |
|---|---|
| The link is valid | A form for setting a new password. |
| The link expired or was already used | A clear message and a way to request a new link from the sign-in page. |
| The user requested another link | Behavior consistent with your app’s policy for earlier links. If the newest request invalidates older links, explain how to request a fresh one on the invalid-link screen. |
| The user didn’t request a reset | The request email says they can ignore it. |
| The password was changed successfully | A separate security notification confirms the change and tells the user how to contact support if it wasn’t theirs. |
Keep the password itself out of both messages.
Pre-send checklist
- Complete a reset from a test inbox. Request a link, open the delivered message on a phone, and set a new password on the expected domain.
- Try the fallback. Copy the visible link from both versions of the email and confirm it reaches the same reset page as the button. Check that the delivered link points directly to the expected domain.
- Check expired, used, and repeated links. Test an expired link, reopen one after completing a reset, and request two links in succession. Verify the result against your app’s policy and check that the next step is clear.
- Check the public request form. Submit a registered address and an unregistered one. Confirm that the response doesn’t reveal which account exists.
- Check the confirmation separately. Verify that requesting a reset sends the request email and that successfully changing the password sends the confirmation.