Frequently asked questions

WorkMail is the control center for your application's email, built on your own Resend account. Compose from your verified domain, start from a template, test how something renders, or use the API Playground to get the equivalent code for your own app — all through your own Resend API key. WorkMail isn't an email provider itself.

Yes. WorkMail sends every email through Resend, using your own API key. If you don't have a Resend account yet, you'll need to create one and verify a sending domain before you can send from WorkMail.

Your key is stored only in your browser's local storage. When you send an email or sync your domains, WorkMail's server relays that one request to Resend using your key and does not log, cache, or store it anywhere. See the Privacy Policy for details.

Any prefix on a domain you've verified in Resend — noreply@, support@, info@, or a custom prefix you type yourself. WorkMail suggests common ones as you type, but doesn't restrict you to that list.

Domain verification happens in Resend, not in WorkMail — add and verify your domain from your Resend dashboard, then use Sync domains from Resend in WorkMail's Settings tab to pull it in.

Starting points for the emails most apps send — welcome, OTP, invoice, password reset, payment confirmation, contact form, and developer notification. Pick one in the Templates tab, fill in a few fields, and it drops straight into Compose as regular HTML you can keep editing.

Yes — templates are just a starting point. Once inserted into Compose, the content is regular editable text in the rich text editor, the same as anything you'd write from scratch.

A place to build a send request — from, to, subject, HTML — and get matching code in cURL, JavaScript, Python, PHP, Node.js, and React. There's also a "Send this request" button if you want to fire the exact request you're looking at, using your saved key.

Yes — add your address once in Settings under "Testing," then use Send test to myself in Compose any time. It sends the current draft to that address with "[Test]" prepended to the subject.

It renders your actual HTML in your browser, inside a frame styled to resemble each client's layout — it isn't running each client's real rendering engine, so treat it as a strong visual guide, not a pixel-perfect guarantee. Outlook desktop in particular renders HTML differently from a browser (it uses Word's engine), which is why the preview also flags patterns — flexbox, grid, background images, embedded SVG — known to behave differently there.

WorkMail's compose form flags things it can actually check — domain verification, a plain-text version, subject lines that look clean — but no tool can guarantee inbox placement. That also depends on your domain's sending reputation and each recipient's own filters.

WorkMail itself doesn't charge for sending. You're using your own Resend account, so any costs are whatever Resend's pricing applies to your usage — check Resend's pricing directly.

In your browser's local storage, nothing else. You can delete individual entries from the History tab, or clear everything at once from Settings.

Your saved API key, domain, and sent history all disappear — they're not backed up anywhere else. You'll need to paste your key in again next time.

No. WorkMail is an independent tool built on top of Resend's API.

Email info@workmail.space and we'll get back to you.