How to Send Emails in Remix (2026)
Loaders and actions are the send points. Remix is comfortable with both Node and edge deploys.
Remix on Cloudflare Workers needs an edge-friendly SDK. Remix on Node accepts any SDK.
Send patterns
- Action handlers for form-triggered sends.
- React Email co-located with route modules.
- Idempotency derived from form submission ID.
Common mistakes
- Edge-runtime incompatible SDKs cause cold deploy failures.
- Resource routes leaking inside loaders without authentication.
provider picks for Remix
- 01
Resend
TransactionalReact Email plays well with Remix loaders.
3,000/mo permanent, capped at 100/day, one domain · $20/mo for 50,000 emails - 02
Postmark
TransactionalStable across Remix runtimes.
100/mo developer plan · $15/mo for 10,000 emails - 03
Loops
Marketing TransactionalSingle SDK for transactional and lifecycle.
1,000 contacts and 4,000 sends/mo on the Free plan · $49/mo for 5,000 contacts
reading this as early-stage startups
At an early stage the deciding factors are what the free tier actually covers, what the first paid invoice looks like, and how much of a founding engineer's week the setup costs. Feature depth that only matters at a million sends a month is noise until it is not.
Applied to how to send emails in remix (2026), that means weighing free tier, best published rate per 1,000, entry price, and developer experience ahead of the rest, against a waitlist, a launch announcement, onboarding email, and the first transactional sends.